Minor cleanup.

Documentation/filesystems/ntfs.txt

@@ -43,11 +43,17 @@ errors=opt		What to do when critical file system errors are found.
 			Following values can be used for "opt":
 			  continue: DEFAULT, try to clean-up as much as
 				    possible, e.g. marking a corrupt inode as
-				    bad so it is no longer accessed.
+				    bad so it is no longer accessed, and then
+				    continue.
 			  recover:  At present only supported is recovery of
 				    the boot sector from the backup copy. If a
 				    read-only mount, the recovery is done in
 				    memory only and not written to disk.
+			Note that the options are additive, i.e. specifying:
+			   errors=continue,errors=recover
+			This means the driver will attempt to recover and if
+			that fails it will clean-up as much as possible and
+			continue.
 
 show_inodes=opt		Allows choice of which types of inode names readdir()
 			returns, i.e. this affects what "ls" shows. Following

fs/Config.help

@@ -584,9 +584,10 @@ CONFIG_NTFS_FS
   This file system is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called ntfs.o. If you want to compile it as a
-  module, say M here and read <file:Documentation/modules.txt>. If you
-  are not using Windows NT/2000/XP in addition to Linux on your computer
-  it is safe to say N.
+  module, say M here and read <file:Documentation/modules.txt>.
+
+  If you are not using Windows NT/2000/XP in addition to Linux on your
+  computer it is safe to say N.
 
 CONFIG_NTFS_DEBUG
   If you are experiencing any problems with the NTFS file system, say
@@ -600,7 +601,7 @@ CONFIG_NTFS_DEBUG
     echo 1 > /proc/sys/fs/ntfs-debug
   Replacing the "1" with "0" would disable debug messages.
 
-  If you leave debugging messages disable, this results in little
+  If you leave debugging messages disabled, this results in little
   overhead, but enabling debug messages results in very significant
   slowdown of the system.