Fixed typos, minor spelling mistakes

(This used to be commit 726785c7fa548c6f0b1f0d4818032c2621c2225e)

1 files changed, 17 insertions, 15 deletions

diff --git a/docs/manpages/mount.cifs.8.xml b/docs/manpages/mount.cifs.8.xml
index bcf3954da2..bdccc1399e 100644
--- a/docs/manpages/mount.cifs.8.xml
+++ b/docs/manpages/mount.cifs.8.xml
@@ -49,7 +49,7 @@ have write permission.
 	<para>
 		Options to <emphasis>mount.cifs</emphasis> are specified as a comma-separated
 list of key=value pairs. It is possible to send options other
-than those listed here, assuming that cifs filesystem supports them.   
+than those listed here, assuming that the cifs filesystem kernel module (cifs.ko) supports them.   
 Unrecognized cifs mount options passed to the cifs vfs kernel code will be logged to the
 kernel log.
 
@@ -95,7 +95,7 @@ for a password, unless the guest option is specified.
 character (i.e. a comma ',') will fail to be parsed correctly
 on the command line.  However, the same password defined
 in the PASSWD environment variable or via a credentials file (see
-below) will be read correctly.
+below) or entered at the password prompt will be read correctly.
 </para>
 	</listitem></varlistentry>
 
@@ -230,7 +230,7 @@ port 445 is tried and if no response then port 139 is tried.
                 on newly created files, directories, and devices (create,
                 mkdir, mknod) which will result in the server setting the
                 uid and gid to the default (usually the server uid of the
-                usern who mounted the share).  Letting the server (rather than
+                user who mounted the share).  Letting the server (rather than
                 the client) set the uid and gid is the default. This
                 parameter has no effect if the CIFS Unix Extensions are not
                 negotiated.</para></listitem>
@@ -266,7 +266,7 @@ port 445 is tried and if no response then port 139 is tried.
                 client (e.g. when the application is doing large sequential
                 reads bigger than page size without rereading the same data)
                 this can provide better performance than the default
-                behavior which caches reads (reaadahead) and writes
+                behavior which caches reads (readahead) and writes
                 (writebehind) through the local Linux client pagecache
                 if oplock (caching token) is granted and held. Note that
                 direct allows write operations larger than page size
@@ -315,7 +315,7 @@ port 445 is tried and if no response then port 139 is tried.
 
         <varlistentry>
                 <term>--verbose</term>
-                <listitem><para>print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:</para><para>mount -t cifs //server/share /mnt --verbose -o user=username</para></listitem>
+                <listitem><para>Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:</para><para>mount -t cifs //server/share /mnt --verbose -o user=username</para></listitem>
         </varlistentry>
 
 	<varlistentry>
@@ -331,20 +331,22 @@ port 445 is tried and if no response then port 139 is tried.
 
         <varlistentry>
                 <term>serverino</term>
-                <listitem><para>Use servers inode numbers instead of generating automatically
-                incrementing inode numbers on the client.  Although this will
+                <listitem><para>Use inode numbers (unique persistent file identifiers)
+		returned by the server instead of automatically generating
+                temporary inode numbers on the client.  Although server inode numbers
                 make it easier to spot hardlinked files (as they will have
-                the same inode numbers) and inode numbers may be persistent,
-                note that the server does not guarantee that the inode numbers
+                the same inode numbers) and inode numbers may be persistent (which is
+		userful for some sofware),
+                the server does not guarantee that the inode numbers
                 are unique if multiple server side mounts are exported under a
                 single share (since inode numbers on the servers might not
                 be unique if multiple filesystems are mounted under the same
-                shared higher level directory).  Note that this requires that
-                the server support the CIFS Unix Extensions as other servers
-                do not return a unique IndexNumber on SMB FindFirst (most
-                servers return zero as the IndexNumber).  Parameter has no
-                effect to Windows servers and others which do not support the
-                CIFS Unix Extensions.
+                shared higher level directory).  Note that not all 
+                servers support returning server inode numbers, although
+		those that support the CIFS Unix Extensions, and Windows 2000 and
+		later servers typically do support this (although not necessarily
+		on every local server filesystem). Parameter has no effect if
+                the server lacks support for returning inode numbers or equivalent.
 		</para></listitem>
         </varlistentry>