(Selecting a Fileset): Fix typo; small rewording.

diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index 81f09ee463718412468af645a26315ddbe1c2180..32228e4260426a7443bcfa96c4ad1e28d9281fb8 100644 (file)
--- a/doc/emacs/ChangeLog
+++ b/doc/emacs/ChangeLog
@@ -2,6 +2,7 @@
 
        * files.texi (Why Version Control?): Fix typo.
        (VCS Concepts): Fix typos; small tense fix.
+       (Selecting a Fileset): Fix typo; small rewording.
 
 2007-11-23  Mark A. Hershberger  <mah@everybody.org>
 

diff --git a/doc/emacs/files.texi b/doc/emacs/files.texi
index e384e8b0838a913eb751873e55650b95fcb71a19..04eaeac4aebe8bc355d4297a96176de972608ee4 100644 (file)
--- a/doc/emacs/files.texi
+++ b/doc/emacs/files.texi
@@ -1622,7 +1622,7 @@ your fileset is the marked files only.
 If they are not, VC mode will fail when you attempt to execute 
 a command on the fileset.
 
-   In VC, filesets, are, essentially, a way to pass multiple file
+   VC filesets are, essentially, a way to pass multiple file
 arguments as a group to underlying version-control commands.  For
 example, on Subversion a checkin with more than one file in its
 fileset will become a joint commit, as though you had typed
@@ -1640,7 +1640,7 @@ version-control systems.
 
    Emacs uses the concept of named filesets elsewhere
 (@pxref{Filesets}) to allow you to view and visit files in functional
-groups. Unlike those, VC filesets are not named and don't persist
+groups.  Unlike those, VC filesets are not named and don't persist
 across sessions.
 
 @node Doing The Right Thing