Patch from larry to fix some grammar errors.

git-svn-id: svn://busybox.net/trunk/busybox@2715 69ca8d6d-28ef-0310-b511-8ec308f3f277

2 files changed, 6 insertions, 6 deletions

diff --git a/docs/busybox.sgml b/docs/busybox.sgml
index f794f896c..2d372506b 100644
--- a/docs/busybox.sgml
+++ b/docs/busybox.sgml
@@ -805,7 +805,7 @@
 
                 <para>
                 Summarize the disk space used for each FILE or current
-                directory.  Disk space printed in units of 1k (i.e.
+                directory.  Disk space printed in units of 1k (i.e.,
                 1024 bytes).
                 </para>
 
@@ -2285,7 +2285,7 @@
 
                 <para>
                 Creates a temporary file with its name based on
-                TEMPLATE.  TEMPLATE is any name with six `Xs' (i.e.
+                TEMPLATE.  TEMPLATE is any name with six `Xs' (i.e.,
                 /tmp/temp.XXXXXX).
                 </para>
 
@@ -3407,7 +3407,7 @@
                 <screen>
                         -a      Unmount all file systems
                         -r      Try to remount devices as read-only if mount is busy
-                        -f      Force filesystem umount (i.e. unreachable NFS server)
+                        -f      Force filesystem umount (i.e., unreachable NFS server)
                         -l      Do not free loop device (if a loop device has been used)
                 </screen>
                 </para>
diff --git a/docs/contributing.txt b/docs/contributing.txt
index abfd51684..2e0049289 100644
--- a/docs/contributing.txt
+++ b/docs/contributing.txt
@@ -45,7 +45,7 @@ Archives can be found here:
 
         http://opensource.lineo.com/lists/busybox/
 
-If you have a serious interest in Busybox, i.e. you are using it day-to-day or
+If you have a serious interest in Busybox, i.e., you are using it day-to-day or
 as part of an embedded project, it would be a good idea to join the mailing
 list.
 
@@ -294,7 +294,7 @@ are some guidelines on how to test your changes.
    behavior / output is identical between the two.
 
  - Try several different permutations and combinations of the features you're
-   adding (i.e. different combinations of command-line switches) and make sure
+   adding (i.e., different combinations of command-line switches) and make sure
    they all work; make sure one feature does not interfere with another.
 
  - Make sure you test compiling against the source both with the feature
@@ -456,7 +456,7 @@ mailing list if:
 
  - Your changes are broad and touch many different files
  - You are adding a feature
- - Your changes are speculative or experimental (i.e. trying a new algorithm)
+ - Your changes are speculative or experimental (i.e., trying a new algorithm)
  - You are not the maintainer and your changes make the maintainer cringe
 
 The more of the above are true, the better it is to post a patch to the