minor typos in emacs.texi and files.texi

["Robert J. Chassell" <bob@rattlesnake.com>]

Minor typos:

in   emacs/doc/emacs/emacs.texi

in  @detailmenu

    * Old Revisions::        Examining and comparing old versions.

should be

    * Old Revisions::       Examining and comparing old versions.

that is to say, remove one space before the word  Examining

\f
in   emacs/doc/emacs/files.texi

in @subsection Introduction to Version Control

    systems with widely differing capabilities,  it does provide

should be

    systems with widely differing capabilities, it does provide

that is to say, remove one space before the word  it

\f
in   emacs/doc/emacs/files.texi

in @subsubsection Concepts of Version Control

    work file at any time.  When you check in a a file, the system will

should be

    work file at any time.  When you check in a file, the system will

that is to say, remove the extranous  a

\f
in   emacs/doc/emacs/files.texi

in @subsubsection Concepts of Version Control

please improve phrasing:

change

    Most later version-control systems, such as GNU Arch, git, and
    Mercurial, have been fundamentally merging-based rather than
    locking-based.  

to

    Most later version-control systems, such as GNU Arch, git, and
    Mercurial, are based on merging rather than locking.

\f
in   emacs/doc/emacs/files.texi

in @subsubsection Concepts of Version Control

    @dfn{master file} with its own comment- and revision history separate

should be

    @dfn{master file} with its own comment- and revision history separate

that is to say, remove the extranous hyphen; I know why it is there,
but `comment history' succeeds.

\f
in   emacs/doc/emacs/files.texi

in @subsubsection Concepts of Version Control

write tenses correctly

    from that of all other files in the system.  Later systems, beginning
    with Subversion, are @dfn{changeset-based}; a checkin may include
    changes to several files and that change set is treated as a unit by the
    system.  Any comment associated with the change doesn't belong to any
    one file, but is attached to the changeset itself.

should be

    from that of all other files in the system.  Later systems,
    beginning with Subversion, were @dfn{changeset-based}; a checkin
    included changes to several files and that change set was (and
    still is) treated as a unit by the system.

(I have refilled the latter.)

You might also change from

    system.  Any comment associated with the change doesn't belong to any
    one file, but is attached to the changeset itself.

to

    system.  No comment associated with a change belongs to any one
    file, but is attached to the changeset itself.


\f
in   emacs/doc/emacs/files.texi

in @subsubsection Concepts of Version Control

    there are lots of legacy repositories still to be dealt with at time of
    writing in 2007.

shold be

    there are lots of legacy repositories still to be dealt with at
    the time of
    writing in 2007.

that is to say, add `the' to `time of writing'; please don't ask me
why `time' is considered as concrete as `maple tree'. 


\f
The `makeinfo' program converts three dashes or hyphens to two and two
dashes or hyphens to one.  TeX converts three hyphens to a long dash.

The convention in the Emacs manual is to use three dashes, not two
dashes, in the Oxford style (I prefer the Cambridge style with three
dashes, but that is irrelevant).

However,   emacs/doc/emacs/files.texi  has both three and two dashes.

For example, 

    convention it uses to separate lines---newline (used on GNU/Linux and

in  emacs/doc/emacs/files.texi


in @subsubsection Concepts of Version Control

    changeset-based ones--the Subversion support, for example, used to break

    single point of failure--if the repository server is down all work

and other double dashes, should be

    changeset-based ones---the Subversion support, for example, used to break

    single point of failure---if the repository server is down all work

\f
I stopped there.  The next segment in emacs/doc/emacs/files.texi is

    subsubsection Types of Log File

-- 

    Robert J. Chassell                          GnuPG Key ID: 004B4AC8
    bob@rattlesnake.com                         bob@gnu.org
    http://www.rattlesnake.com                  http://www.teak.cc