In doc, use standard American English style for e.g., etc., i.e.

31 files changed, 70 insertions, 71 deletions

diff --git a/doc/emacs/ack.texi b/doc/emacs/ack.texi
index a0ab8223ae0..99e0c690a09 100644
--- a/doc/emacs/ack.texi
+++ b/doc/emacs/ack.texi
@@ -726,7 +726,7 @@ the display of the Emacs tool bar.  With Riccardo Murri he wrote
 Eric Ludlam wrote the Speedbar package; @file{checkdoc.el}, for checking
 doc strings in Emacs Lisp programs; @file{dframe.el}, providing
 dedicated frame support modes; @file{ezimage.el}, a generalized way to
-place images over text; @file{chart.el} for drawing bar charts etc; and
+place images over text; @file{chart.el} for drawing bar charts etc.; and
 the EIEIO (Enhanced Implementation of Emacs Interpreted Objects)
 package.  He was also the main author of the CEDET (Collection of Emacs
 Development Environment Tools) package.  Portions were also written by
diff --git a/doc/emacs/mark.texi b/doc/emacs/mark.texi
index 6ed3b2e6d37..05b2a5be3a4 100644
--- a/doc/emacs/mark.texi
+++ b/doc/emacs/mark.texi
@@ -131,7 +131,7 @@ detailed description of these mouse commands.
 @cindex shift-selection
   Finally, you can set the mark by holding down the shift key while
 typing certain cursor motion commands (such as @kbd{S-@key{right}},
-@kbd{S-C-f}, @kbd{S-C-n}, etc.)  This is called @dfn{shift-selection}.
+@kbd{S-C-f}, @kbd{S-C-n}, etc.).  This is called @dfn{shift-selection}.
 It sets the mark at point before moving point, but only if there is no
 active mark set via shift-selection.  The mark set by mouse commands
 and by shift-selection behaves slightly differently from the usual
diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi
index 50710e23234..1181244a974 100644
--- a/doc/lispref/processes.texi
+++ b/doc/lispref/processes.texi
@@ -88,7 +88,7 @@ initializes @code{exec-path} when it starts up, based on the value of
 the environment variable @env{PATH}.  The standard file name
 constructs, @samp{~}, @samp{.}, and @samp{..}, are interpreted as
 usual in @code{exec-path}, but environment variable substitutions
-(@samp{$HOME}, etc.) are not recognized; use
+(@samp{$HOME}, etc.)@: are not recognized; use
 @code{substitute-in-file-name} to perform them (@pxref{File Name
 Expansion}).  @code{nil} in this list refers to
 @code{default-directory}.
@@ -557,7 +557,7 @@ from the process only while waiting for input or for a time delay.
 when creating the process, based on the value of the variable
 @code{process-connection-type} (see below).  Ptys are usually
 preferable for processes visible to the user, as in Shell mode,
-because they allow for job control (@kbd{C-c}, @kbd{C-z}, etc.)
+because they allow for job control (@kbd{C-c}, @kbd{C-z}, etc.)@:
 between the process and its children, whereas pipes do not.  For
 subprocesses used for internal purposes by programs, it is often
 better to use a pipe, because they are more efficient, and because
@@ -571,7 +571,7 @@ program @var{program} running in it.  It returns a process object that
 stands for the new subprocess in Lisp.  The argument @var{name}
 specifies the name for the process object; if a process with this name
 already exists, then @var{name} is modified (by appending @samp{<1>},
-etc.) to be unique.  The buffer @var{buffer-or-name} is the buffer to
+etc.)@: to be unique.  The buffer @var{buffer-or-name} is the buffer to
 associate with the process.
 
 If @var{program} is @code{nil}, Emacs opens a new pseudoterminal (pty)
diff --git a/doc/man/etags.1 b/doc/man/etags.1
index 20c392776ee..20be5c82684 100644
--- a/doc/man/etags.1
+++ b/doc/man/etags.1
@@ -146,7 +146,7 @@ of \- means standard output; overrides default \fBTAGS\fP or \fBtags\fP.
 Make tags based on regexp matching for the files following this option,
 in addition to the tags made with the standard parsing based on
 language. May be freely intermixed with filenames and the \fB\-R\fP
-option.  The regexps are cumulative, i.e. each such option will add to
+option.  The regexps are cumulative, i.e., each such option will add to
 the previous ones.  The regexps are of one of the forms:
 .br
 	[\fB{\fP\fIlanguage\fP\fB}\fP]\fB/\fP\fItagregexp/\fP[\fInameregexp\fP\fB/\fP]\fImodifiers\fP
@@ -282,4 +282,3 @@ Permission is granted to copy and distribute translations of this
 document into another language, under the above conditions for
 modified versions, except that this permission notice may be stated
 in a translation approved by the Free Software Foundation.
-
diff --git a/doc/misc/ada-mode.texi b/doc/misc/ada-mode.texi
index c687ce16877..223911ebb7a 100644
--- a/doc/misc/ada-mode.texi
+++ b/doc/misc/ada-mode.texi
@@ -72,7 +72,7 @@ existing code and facilitates writing new code.
 
 When the Gnu Ada compiler GNAT is used, the cross-reference
 information output by the compiler is used to provide powerful code
-navigation (jump to definition, find all uses, etc).
+navigation (jump to definition, find all uses, etc.).
 
 When you open a file with a file extension of @file{.ads} or
 @file{.adb}, Emacs will automatically load and activate Ada mode.
@@ -1267,7 +1267,7 @@ Non-@code{nil} means that the current line will also be re-indented
 before inserting a newline, when you press @key{RET}.
 @end table
 
-Most of the time, the indentation will be automatic, i.e when you
+Most of the time, the indentation will be automatic, i.e., when you
 press @key{RET}, the cursor will move to the correct column on the
 next line.
 
diff --git a/doc/misc/bovine.texi b/doc/misc/bovine.texi
index 48d5cf9e18a..978345e5cc8 100644
--- a/doc/misc/bovine.texi
+++ b/doc/misc/bovine.texi
@@ -314,7 +314,7 @@ The first object spliced into the list (assuming it is a list from a
 non-terminal).
 
 @item '$1
-The first object matched, placed in a list.  i.e. @code{( $1 )}.
+The first object matched, placed in a list.  I.e., @code{( $1 )}.
 
 @item foo
 The symbol @code{foo} (exactly as displayed).
diff --git a/doc/misc/calc.texi b/doc/misc/calc.texi
index 6d036910877..ba491a569b7 100644
--- a/doc/misc/calc.texi
+++ b/doc/misc/calc.texi
@@ -14011,7 +14011,7 @@ conventions.  Like C mode, Pascal mode interprets array brackets and uses
 a different table of operators.  Hexadecimal numbers are entered and
 displayed with a preceding dollar sign.  (Thus the regular meaning of
 @kbd{$2} during algebraic entry does not work in Pascal mode, though
-@kbd{$} (and @kbd{$$}, etc.) not followed by digits works the same as
+@kbd{$} (and @kbd{$$}, etc.)@: not followed by digits works the same as
 always.)  No special provisions are made for other non-decimal numbers,
 vectors, and so on, since there is no universally accepted standard way
 of handling these in Pascal.
diff --git a/doc/misc/cc-mode.texi b/doc/misc/cc-mode.texi
index 55b7028101a..bb6a5b001ad 100644
--- a/doc/misc/cc-mode.texi
+++ b/doc/misc/cc-mode.texi
@@ -4959,7 +4959,7 @@ the declaration is an annotation.
 
 There are a few occasions where a statement block might be used inside
 an expression.  One is in C or C++ code using the gcc extension for
-this, e.g:
+this, e.g.:
 
 @example
  1: int res = (@{
@@ -5552,7 +5552,7 @@ parentheses and statements within brace blocks.
 @findex lineup-close-paren (c-)
 Line up the closing paren under its corresponding open paren if the
 open paren is followed by code.  If the open paren ends its line, no
-indentation is added.  E.g:
+indentation is added.  E.g.:
 
 @example
 @group
@@ -5606,7 +5606,7 @@ discussion of this ``DWIM'' measure.
 
 @defun c-indent-one-line-block
 @findex indent-one-line-block (c-)
-Indent a one line block @code{c-basic-offset} extra.  E.g:
+Indent a one line block @code{c-basic-offset} extra.  E.g.:
 
 @example
 @group
@@ -5640,7 +5640,7 @@ which makes the function usable in list expressions.
 
 @defun c-indent-multi-line-block
 @findex indent-multi-line-block (c-)
-Indent a multiline block @code{c-basic-offset} extra.  E.g:
+Indent a multiline block @code{c-basic-offset} extra.  E.g.:
 
 @example
 @group
@@ -5679,7 +5679,7 @@ block, which makes the function usable in list expressions.
 Line up statements for coding standards which place the first statement
 in a block on the same line as the block opening brace@footnote{Run-in
 style doesn't really work too well.  You might need to write your own
-custom line-up functions to better support this style.}.  E.g:
+custom line-up functions to better support this style.}.  E.g.:
 
 @example
 @group
@@ -5762,7 +5762,7 @@ indents relative to the surrounding block just like
 @defun c-lineup-whitesmith-in-block
 @findex lineup-whitesmith-in-block (c-)
 Line up lines inside a block in Whitesmith style.  It's done in a way
-that works both when the opening brace hangs and when it doesn't.  E.g:
+that works both when the opening brace hangs and when it doesn't.  E.g.:
 
 @example
 @group
@@ -5816,7 +5816,7 @@ Line up the current argument line under the first argument.
 As a special case, if an argument on the same line as the open
 parenthesis starts with a brace block opener, the indentation is
 @code{c-basic-offset} only.  This is intended as a ``DWIM'' measure in
-cases like macros that contain statement blocks, e.g:
+cases like macros that contain statement blocks, e.g.:
 
 @example
 @group
@@ -5852,7 +5852,7 @@ brace block.
 @defun c-lineup-multi-inher
 @findex lineup-multi-inher (c-)
 Line up the classes in C++ multiple inheritance clauses and member
-initializers under each other.  E.g:
+initializers under each other.  E.g.:
 
 @example
 @group
@@ -5895,7 +5895,7 @@ Line up Java implements and extends declarations.  If class names
 follow on the same line as the @samp{implements}/@samp{extends}
 keyword, they are lined up under each other.  Otherwise, they are
 indented by adding @code{c-basic-offset} to the column of the keyword.
-E.g:
+E.g.:
 
 @example
 @group
@@ -5929,7 +5929,7 @@ same line as the throws keyword, they are lined up under each other.
 Otherwise, they are indented by adding @code{c-basic-offset} to the
 column of the @samp{throws} keyword.  The @samp{throws} keyword itself
 is also indented by @code{c-basic-offset} from the function declaration
-start if it doesn't hang.  E.g:
+start if it doesn't hang.  E.g.:
 
 @example
 @group
@@ -6014,7 +6014,7 @@ line.
 
 @defun c-lineup-argcont
 @findex lineup-argcont (c-)
-Line up a continued argument.  E.g:
+Line up a continued argument.  E.g.:
 
 @example
 @group
@@ -6101,7 +6101,7 @@ function is the same as specifying a list @code{(c-lineup-assignments
 Line up ``cascaded calls'' under each other.  If the line begins with
 @code{->} or @code{.} and the preceding line ends with one or more
 function calls preceded by the same token, then the arrow is lined up
-with the first of those tokens.  E.g:
+with the first of those tokens.  E.g.:
 
 @example
 @group
@@ -6133,7 +6133,7 @@ Line up C++ stream operators (i.e., @samp{<<} and @samp{>>}).
 @findex lineup-string-cont (c-)
 Line up a continued string under the one it continues.  A continued
 string in this sense is where a string literal follows directly after
-another one.  E.g:
+another one.  E.g.:
 
 @example
 @group
@@ -6242,7 +6242,7 @@ is equivalent to @code{(@r{@var{value}} . -1000)}.
 @findex lineup-knr-region-comment (c-)
 Line up a comment in the ``K&R region'' with the declaration.  That is
 the region between the function or class header and the beginning of the
-block.  E.g:
+block.  E.g.:
 
 @example
 @group
@@ -6282,7 +6282,7 @@ already has; think of it as an identity function for lineups.
 @defun c-lineup-cpp-define
 @findex lineup-cpp-define (c-)
 Line up macro continuation lines according to the indentation of the
-construct preceding the macro.  E.g:
+construct preceding the macro.  E.g.:
 
 @example
 @group
@@ -6409,7 +6409,7 @@ that those lines could be analyzed as either topmost-intro-cont or
 statement-cont.  It's used for @code{topmost-intro-cont} by default, but
 you might consider using @code{+} instead.}.  For lines preceding a
 definition, zero is used.  For other lines, @code{c-basic-offset} is
-added to the indentation.  E.g:
+added to the indentation.  E.g.:
 
 @example
 @group
@@ -6507,7 +6507,7 @@ earlier.  Line-up functions are still passed this cons cell, so as to
 preserve compatibility with older configurations.  In the future, we
 may decide to convert to using the full list format---you can prepare
 your setup for this by using the access functions
-(@code{c-langelem-sym}, etc.)  described below.
+(@code{c-langelem-sym}, etc.)@: described below.
 
 @vindex c-syntactic-element
 @vindex syntactic-element (c-)
diff --git a/doc/misc/cl.texi b/doc/misc/cl.texi
index cb04f65cf0d..a16dc92de77 100644
--- a/doc/misc/cl.texi
+++ b/doc/misc/cl.texi
@@ -748,7 +748,7 @@ This function attempts to convert @var{object} to the specified
 @var{type}.  If @var{object} is already of that type as determined by
 @code{cl-typep}, it is simply returned.  Otherwise, certain types of
 conversions will be made:  If @var{type} is any sequence type
-(@code{string}, @code{list}, etc.) then @var{object} will be
+(@code{string}, @code{list}, etc.)@: then @var{object} will be
 converted to that type if possible.  If @var{type} is
 @code{character}, then strings of length one and symbols with
 one-character names can be coerced.  If @var{type} is @code{float},
diff --git a/doc/misc/dired-x.texi b/doc/misc/dired-x.texi
index 2cf25641350..1e3d11f6dc6 100644
--- a/doc/misc/dired-x.texi
+++ b/doc/misc/dired-x.texi
@@ -882,7 +882,7 @@ Dired buffers, is like @code{shell-command}, but it runs with
 
 @file{dired-x} provides a method of visiting or editing a file mentioned in
 the buffer you are viewing (e.g., a mail buffer, a news article, a
-@file{README} file, etc.) or to test if that file exists.  You can then modify
+@file{README} file, etc.)@: or to test if that file exists.  You can then modify
 this in the minibuffer after snatching the file name.
 
 When installed @file{dired-x} will substitute @code{dired-x-find-file} for
diff --git a/doc/misc/ede.texi b/doc/misc/ede.texi
index ddee7e6b5d5..f2e787fd588 100644
--- a/doc/misc/ede.texi
+++ b/doc/misc/ede.texi
@@ -1050,7 +1050,7 @@ other options for that project.  The configuration is saved in
 
 Generic projects are disabled by default because they have the
 potential to interfere with other projects.  To use the generic
-project sytem to start detecting projects, you need to enable it.
+project system to start detecting projects, you need to enable it.
 
 @deffn Command ede-enable-generic-projects
 Enable generic project loaders.
@@ -1956,7 +1956,7 @@ Type: @code{list} @*
 Default Value: @code{(quote ("/include" "../include/"))}
 
 The default locate function expands filenames within a project.
-If a header file (.h, .hh, etc) name is expanded, and
+If a header file (.h, .hh, etc.)@: name is expanded, and
 the @code{:locate-fcn} slot is @code{nil}, then the include path is checked
 first, and other directories are ignored.  For very large
 projects, this optimization can save a lot of time.
diff --git a/doc/misc/ediff.texi b/doc/misc/ediff.texi
index cf4438c8bad..edb2a446cf5 100644
--- a/doc/misc/ediff.texi
+++ b/doc/misc/ediff.texi
@@ -1148,7 +1148,7 @@ packages also use this method).
 Regular files are treated by the @code{patch} utility in the usual manner,
 i.e., the original is renamed into @file{source-name.orig} and the result
 of the patch is placed into the file source-name (@file{_orig} is used
-on systems like DOS, etc.)
+on systems like DOS, etc.).
 
 @node Customization, Credits, Remote and Compressed Files, Top
 @chapter Customization
diff --git a/doc/misc/emacs-mime.texi b/doc/misc/emacs-mime.texi
index 216e4733cd1..b1cf40aa645 100644
--- a/doc/misc/emacs-mime.texi
+++ b/doc/misc/emacs-mime.texi
@@ -993,7 +993,7 @@ Customization}).
 The charset to be used can be overridden by setting the @code{charset}
 @acronym{MML} tag (@pxref{MML Definition}) when composing the message.
 
-The encoding of characters (quoted-printable, 8bit etc) is orthogonal
+The encoding of characters (quoted-printable, 8bit, etc.)@: is orthogonal
 to the discussion here, and is controlled by the variables
 @code{mm-body-charset-encoding-alist} and
 @code{mm-content-transfer-encoding-defaults} (@pxref{Encoding
diff --git a/doc/misc/eshell.texi b/doc/misc/eshell.texi
index 8d398900238..b23d5075b51 100644
--- a/doc/misc/eshell.texi
+++ b/doc/misc/eshell.texi
@@ -625,7 +625,7 @@ string-manipulation expansions because the Elisp library already
 provides many functions for this.}  For example, @code{$var} on a line
 expands to the value of the variable @code{var} when the line is
 executed.  Expansions are usually passed as arguments, but may also be
-used as commands.@footnote{e.g. Entering just @samp{$var} at the prompt
+used as commands.@footnote{E.g., entering just @samp{$var} at the prompt
 is equivalent to entering the value of @code{var} at the prompt.}
 
 @menu
@@ -1158,7 +1158,7 @@ it).
 @item Make the shell spawning commands be visual
 
 That is, make (@command{su}, @command{bash}, @command{telnet},
-@command{rlogin}, @command{rsh}, etc.) be part of
+@command{rlogin}, @command{rsh}, etc.)@: be part of
 @code{eshell-visual-commands}.  The only exception is if the shell is
 being used to invoke a single command.  Then, the behavior should be
 based on what that command is.
diff --git a/doc/misc/faq.texi b/doc/misc/faq.texi
index 8f3c0c2d623..39b4a9037bd 100644
--- a/doc/misc/faq.texi
+++ b/doc/misc/faq.texi
@@ -1909,7 +1909,7 @@ following line to your @file{.emacs}:
 where @var{syntactic-symbol} is the name Emacs shows in the minibuffer
 when you type @kbd{C-c C-o} at the beginning of the line, and
 @var{offset} is one of the indentation symbols listed above (@code{+},
-@code{/}, @code{0}, etc.) that you've chosen during the interactive
+@code{/}, @code{0}, etc.)@: that you've chosen during the interactive
 procedure.
 
 @item
diff --git a/doc/misc/flymake.texi b/doc/misc/flymake.texi
index 1807f108e3b..79259a76503 100644
--- a/doc/misc/flymake.texi
+++ b/doc/misc/flymake.texi
@@ -64,7 +64,7 @@ modify this GNU manual.''
 
 Flymake is a universal on-the-fly syntax checker implemented as an
 Emacs minor mode. Flymake runs the pre-configured syntax check tool
-(compiler for C++ files, @code{perl} for perl files, etc.) in the
+(compiler for C++ files, @code{perl} for perl files, etc.)@: in the
 background, passing it a temporary copy of the current buffer, and
 parses the output for known error/warning message patterns. Flymake
 then highlights erroneous lines (i.e., lines for which at least one
@@ -569,7 +569,7 @@ These modes are handled inside init/cleanup/getfname functions, see
 Flymake contains implementations of all functionality required to
 support different syntax check modes described above (making temporary
 copies, finding master files, etc.), as well as some tool-specific
-(routines for Make, Ant, etc.) code.
+(routines for Make, Ant, etc.)@: code.
 
 
 @node Making a temporary copy
diff --git a/doc/misc/forms.texi b/doc/misc/forms.texi
index 43ffab26c9b..17b117be961 100644
--- a/doc/misc/forms.texi
+++ b/doc/misc/forms.texi
@@ -117,7 +117,7 @@ they make up a forms.
 
 The contents of the forms consist of the contents of the fields of the
 record (e.g., @samp{root}, @samp{0}, @samp{1}, @samp{Super User})
-interspersed with normal text (e.g @samp{User : }, @samp{Uid: }).
+interspersed with normal text (e.g., @samp{User : }, @samp{Uid: }).
 
 If you modify the contents of the fields, Forms mode will analyze your
 changes and update the file appropriately.  You cannot modify the
diff --git a/doc/misc/gnus-faq.texi b/doc/misc/gnus-faq.texi
index 2a1f5ac2cc1..e7367730040 100644
--- a/doc/misc/gnus-faq.texi
+++ b/doc/misc/gnus-faq.texi
@@ -1218,7 +1218,7 @@ from using them):
                 messages?
 * FAQ 5-3::     How to set stuff like From, Organization, Reply-To,
                 signature...?
-* FAQ 5-4::     Can I set things like From, Signature etc group based on
+* FAQ 5-4::     Can I set things like From, Signature etc. group based on
                 the group I post too?
 * FAQ 5-5::     Is there a spell-checker? Perhaps even on-the-fly
                 spell-checking?
diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi
index 35121e84dde..8d0d5cdc40b 100644
--- a/doc/misc/gnus.texi
+++ b/doc/misc/gnus.texi
@@ -2344,8 +2344,8 @@ Gnus considers groups from levels 1 to
 unsubscribed, @code{gnus-level-zombie} to be zombies (walking dead)
 (default 8) and @code{gnus-level-killed} to be killed (completely dead)
 (default 9).  Gnus treats subscribed and unsubscribed groups exactly the
-same, but zombie and killed groups have no information on what articles
-you have read, etc, stored.  This distinction between dead and living
+same, but zombie and killed groups store no information on what articles
+you have read, etc.  This distinction between dead and living
 groups isn't done because it is nice or clever, it is done purely for
 reasons of efficiency.
 
@@ -11127,7 +11127,7 @@ There will never be more than one dead summary buffer at any one time.
 
 @vindex gnus-use-cross-reference
 The data on the current group will be updated (which articles you have
-read, which articles you have replied to, etc.) when you exit the
+read, which articles you have replied to, etc.)@: when you exit the
 summary buffer.  If the @code{gnus-use-cross-reference} variable is
 @code{t} (which is the default), articles that are cross-referenced to
 this group and are marked as read, will also be marked as read in the
@@ -14009,7 +14009,7 @@ The address of the @acronym{NNTP} server.
 Port number to connect to the @acronym{NNTP} server.  The default is
 @samp{nntp}.  If you use @acronym{NNTP} over
 @acronym{TLS}/@acronym{SSL}, you may want to use integer ports rather
-than named ports (i.e, use @samp{563} instead of @samp{snews} or
+than named ports (i.e., use @samp{563} instead of @samp{snews} or
 @samp{nntps}), because external @acronym{TLS}/@acronym{SSL} tools may
 not work with named ports.
 
@@ -18977,7 +18977,7 @@ agent as unread.
 @subsection Agent and flags
 
 The Agent works with any Gnus back end including those, such as
-nnimap, that store flags (read, ticked, etc) on the server.  Sadly,
+nnimap, that store flags (read, ticked, etc.)@: on the server.  Sadly,
 the Agent does not actually know which backends keep their flags in
 the backend server rather than in @file{.newsrc}.  This means that the
 Agent, while unplugged or disconnected, will always record all changes
@@ -19953,7 +19953,7 @@ the article was posted from.  Time zones are such wholesome fun for the
 whole family, eh?)
 
 @item Head, Body, All
-These three match keys use the same match types as the @code{From} (etc)
+These three match keys use the same match types as the @code{From} (etc.)@:
 header uses.
 
 @item Followup
@@ -23774,7 +23774,7 @@ from Bulgarian IPs.
 
 This, unfortunately, is a great way to discard legitimate e-mail.  The
 risks of blocking a whole country (Bulgaria, Norway, Nigeria, China,
-etc.) or even a continent (Asia, Africa, Europe, etc.) from contacting
+etc.)@: or even a continent (Asia, Africa, Europe, etc.)@: from contacting
 you should be obvious, so don't do it if you have the choice.
 
 In another instance, the very informative and useful RISKS digest has
@@ -25827,7 +25827,7 @@ Fortunately, setting up the Gnus registry is pretty easy:
 
 This adds registry saves to Gnus newsrc saves (which happen on exit
 and when you press @kbd{s} from the @code{*Group*} buffer.  It also
-adds registry calls to article actions in Gnus (copy, move, etc.)  so
+adds registry calls to article actions in Gnus (copy, move, etc.)@: so
 it's not easy to undo the initialization.  See
 @code{gnus-registry-initialize} for the gory details.
 
@@ -27904,7 +27904,7 @@ consist of a little new content at the top with a long, untrimmed
 message cited below.
 
 @item
-Smileys (@samp{:-)}, @samp{;-)} etc) are now displayed graphically in
+Smileys (@samp{:-)}, @samp{;-)} etc.)@: are now displayed graphically in
 Emacs too.
 
 Put @code{(setq gnus-treat-display-smileys nil)} in @file{~/.gnus.el} to
@@ -28510,7 +28510,7 @@ A mail message or news article
 
 @item head
 @cindex head
-The top part of a message, where administrative information (etc.) is
+The top part of a message, where administrative information (etc.)@: is
 put.
 
 @item body
@@ -29459,7 +29459,7 @@ There should be no result data from this function.
 @item (nnchoke-request-set-mark GROUP ACTION &optional SERVER)
 
 Set/remove/add marks on articles.  Normally Gnus handles the article
-marks (such as read, ticked, expired etc) internally, and store them in
+marks (such as read, ticked, expired etc.)@: internally, and store them in
 @file{~/.newsrc.eld}.  Some back ends (such as @acronym{IMAP}) however carry
 all information about the articles on the server, so Gnus need to
 propagate the mark information to the server.
diff --git a/doc/misc/idlwave.texi b/doc/misc/idlwave.texi
index 499e169e93b..0c817adcb36 100644
--- a/doc/misc/idlwave.texi
+++ b/doc/misc/idlwave.texi
@@ -2182,8 +2182,8 @@ operators (outside of strings and comments, of course), try this in
 @end lisp
 
 Note that the modified assignment operators which begin with a word
-(@samp{AND=}, @samp{OR=}, @samp{NOT=}, etc.) require a leading space to
-be recognized (e.g @code{vAND=4} would be interpreted as a variable
+(@samp{AND=}, @samp{OR=}, @samp{NOT=}, etc.)@: require a leading space to
+be recognized (e.g., @code{vAND=4} would be interpreted as a variable
 @code{vAND}).  Also note that since, e.g., @code{>} and @code{>=} are
 both valid operators, it is impossible to surround both by blanks while
 they are being typed.  Similarly with @code{&} and @code{&&}.  For
@@ -2195,7 +2195,7 @@ repad everything if @code{idlwave-do-actions} is on).
 @defopt idlwave-surround-by-blank (@code{nil})
 Non-@code{nil} means enable @code{idlwave-surround}.  If non-@code{nil},
 @samp{=}, @samp{<}, @samp{>}, @samp{&}, @samp{,}, @samp{->}, and the
-modified assignment operators (@samp{AND=}, @samp{OR=}, etc.) are
+modified assignment operators (@samp{AND=}, @samp{OR=}, etc.)@: are
 surrounded with spaces by @code{idlwave-surround}.
 @end defopt
 
diff --git a/doc/misc/message.texi b/doc/misc/message.texi
index 0e0bd115bb2..4d5d82aa6bd 100644
--- a/doc/misc/message.texi
+++ b/doc/misc/message.texi
@@ -2344,7 +2344,7 @@ Valid values include:
 @table @code
 @item nil
 Generate the buffer name in the Message way (e.g., *mail*, *news*, *mail
-to whom*, *news on group*, etc.) and continue editing in the existing
+to whom*, *news on group*, etc.)@: and continue editing in the existing
 buffer of that name.  If there is no such buffer, it will be newly
 created.
 
diff --git a/doc/misc/org.texi b/doc/misc/org.texi
index 7b880fc386c..16015e49362 100644
--- a/doc/misc/org.texi
+++ b/doc/misc/org.texi
@@ -1426,7 +1426,7 @@ level).
 Move subtree down (swap with next subtree of same level).
 @orgcmd{M-h,org-mark-element}
 Mark the element at point.  Hitting repeatedly will mark subsequent elements
-of the one just marked.  E.g. hitting @key{M-h} on a paragraph will mark it,
+of the one just marked.  E.g., hitting @key{M-h} on a paragraph will mark it,
 hitting @key{M-h} immediately again will mark the next one.
 @orgcmd{C-c @@,org-mark-subtree}
 Mark the subtree at point.  Hitting repeatedly will mark subsequent subtrees
@@ -2439,7 +2439,7 @@ You may reference a rectangular range of fields by specifying two field
 references connected by two dots @samp{..}.  If both fields are in the
 current row, you may simply use @samp{$2..$7}, but if at least one field
 is in a different row, you need to use the general @code{@@row$column}
-format at least for the first field (i.e the reference must start with
+format at least for the first field (i.e., the reference must start with
 @samp{@@} in order to be interpreted correctly).  Examples:
 
 @example
@@ -11990,7 +11990,7 @@ resource or resource node which is known to TaskJuggler, such as
 @samp{efficiency}, @samp{journalentry}, @samp{rate} for resources or
 @samp{account}, @samp{start}, @samp{note}, @samp{duration}, @samp{end},
 @samp{journalentry}, @samp{milestone}, @samp{reference}, @samp{responsible},
-@samp{scheduling}, etc for tasks.
+@samp{scheduling}, etc.@: for tasks.
 
 @subsection Dependencies
 
diff --git a/doc/misc/reftex.texi b/doc/misc/reftex.texi
index efffc5078cc..15bb2c4cc0a 100644
--- a/doc/misc/reftex.texi
+++ b/doc/misc/reftex.texi
@@ -648,7 +648,7 @@ buffer.
 @vindex reftex-toc-max-level
 Change the maximum level of toc entries displayed in the @file{*toc*}
 buffer.  Without prefix arg, all levels will be included.  With prefix
-arg (e.g @kbd{3 t}), ignore all toc entries with level greater than
+arg (e.g., @kbd{3 t}), ignore all toc entries with level greater than
 @var{arg} (3 in this case).  Chapters are level 1, sections are level 2.
 The mode line @samp{T<>} indicator shows the current value.  The default
 depth can be configured with the variable
@@ -3499,7 +3499,7 @@ make use of this feature, try
 @item
 @b{@LaTeX{} commands}@*
 @cindex LaTeX commands, not found
-@code{\input}, @code{\include}, and @code{\section} (etc.) statements
+@code{\input}, @code{\include}, and @code{\section} (etc.)@: statements
 have to be first on a line (except for white space).
 
 @item
diff --git a/doc/misc/remember.texi b/doc/misc/remember.texi
index 3a80862d0e7..0f541981f1a 100644
--- a/doc/misc/remember.texi
+++ b/doc/misc/remember.texi
@@ -174,7 +174,7 @@ typing it into a buffer, or using the contents of the selected region,
 it will store that data---unindexed, uninterpreted---in a data pool.
 It will also try to remember as much context information as possible
 (any text properties that were set, where you copied it from, when,
-how, etc).  Later, you can walk through your accumulated set of data
+how, etc.).  Later, you can walk through your accumulated set of data
 (both organized, and unorganized) and easily begin moving things
 around, and making annotations that will express the full meaning of
 that data, as far as you know it.
diff --git a/doc/misc/ses.texi b/doc/misc/ses.texi
index f6c35d1de8e..2bef526257e 100644
--- a/doc/misc/ses.texi
+++ b/doc/misc/ses.texi
@@ -842,7 +842,7 @@ Begins with an 014 character, followed by sets of cell-definition
 macros for each row, followed by column-widths, column-printers,
 default-printer, and header-row.  Then there's the global parameters
 (file-format ID, numrows, numcols) and the local variables (specifying
-SES mode for the buffer, etc.)
+SES mode for the buffer, etc.).
 
 When a SES file is loaded, first the numrows and numcols values are
 loaded, then the entire data area is @code{eval}ed, and finally the local
diff --git a/doc/misc/sieve.texi b/doc/misc/sieve.texi
index cbcd6a61f39..b84c3047ec1 100644
--- a/doc/misc/sieve.texi
+++ b/doc/misc/sieve.texi
@@ -159,7 +159,7 @@ press RET on <new script> to create a new script.
 @end example
 
 One of the scripts are highlighted, and standard point navigation
-commands (@kbd{<up>}, @kbd{<down>} etc) can be used to navigate the
+commands (@kbd{<up>}, @kbd{<down>} etc.)@: can be used to navigate the
 list.
 
 The following commands are available in the Manage Sieve buffer:
diff --git a/doc/misc/speedbar.texi b/doc/misc/speedbar.texi
index 62cfcb95af4..1c427c0b47c 100644
--- a/doc/misc/speedbar.texi
+++ b/doc/misc/speedbar.texi
@@ -1180,7 +1180,7 @@ the next line.
 Create a tag line with @var{exp-button-type} for the small expansion
 button.  This is the button that expands or contracts a node (if
 applicable), and @var{exp-button-char} the character in it (@samp{+},
-@samp{-}, @samp{?}, etc).  @var{exp-button-function} is the function
+@samp{-}, @samp{?}, etc.).  @var{exp-button-function} is the function
 to call if it's clicked on.  Button types are @code{bracket},
 @code{angle}, @code{curly}, @code{expandtag}, @code{statictag}, and
 @code{nil}.  @var{exp-button-data} is extra data attached to the text
@@ -1189,7 +1189,7 @@ forming the expansion button.
 Next, @var{tag-button} is the text of the tag.
 @var{tag-button-function} is the function to call if clicked on, and
 @var{tag-button-data} is the data to attach to the text field (such a
-tag positioning, etc).  @var{tag-button-face} is a face used for this
+tag positioning, etc.).  @var{tag-button-face} is a face used for this
 type of tag.
 
 Lastly, @var{depth} shows the depth of expansion.
diff --git a/doc/misc/url.texi b/doc/misc/url.texi
index a26743ed1aa..42b1624aa0a 100644
--- a/doc/misc/url.texi
+++ b/doc/misc/url.texi
@@ -890,7 +890,7 @@ containing the data cached for that URL.
 
 @c With a large cache of documents on the local disk, it can be very handy
 @c when traveling, or any other time the network connection is not active
-@c (a laptop with a dial-on-demand PPP connection, etc).  Emacs/W3 can rely
+@c (a laptop with a dial-on-demand PPP connection, etc.).  Emacs/W3 can rely
 @c solely on its cache, and avoid checking to see if the page has changed
 @c on the remote server.  In the case of a dial-on-demand PPP connection,
 @c this will keep the phone line free as long as possible, only bringing up
diff --git a/doc/misc/vip.texi b/doc/misc/vip.texi
index 06fb5b9288b..327d8d5f45e 100644
--- a/doc/misc/vip.texi
+++ b/doc/misc/vip.texi
@@ -356,7 +356,7 @@ you can abort a partially formed command by typing @kbd{C-g}.@refill
 As in Vi, searching is done by @kbd{/} and @kbd{?}.  The string will be
 searched literally by default.  To invoke a regular expression search,
 first execute the search command @kbd{/} (or @kbd{?}) with empty search
-string.  (I.e, type @kbd{/} followed by @key{RET}.)
+string.  (I.e., type @kbd{/} followed by @key{RET}.)
 A search for empty string will toggle the search mode between vanilla
 search and regular expression search.  You cannot give an offset to the
 search string.  (It is a limitation.)  By default, search will wrap around
diff --git a/doc/misc/viper.texi b/doc/misc/viper.texi
index 41f34957253..69df06a1c57 100644
--- a/doc/misc/viper.texi
+++ b/doc/misc/viper.texi
@@ -3210,7 +3210,7 @@ and they don't look into the value of variable
 syntax tables in order to not thwart the various major modes that set these
 tables.
 
-The usual Emacs convention is used to indicate Control Characters, i.e
+The usual Emacs convention is used to indicate Control Characters, i.e.,
 C-h for Control-h.  @emph{Do not confuse this with a sequence of separate
 characters
 C, -, h!!!} The @kbd{^} is itself, never used to indicate a
diff --git a/doc/misc/woman.texi b/doc/misc/woman.texi
index 8f8fd5f2287..d7ef94872b4 100644
--- a/doc/misc/woman.texi
+++ b/doc/misc/woman.texi
@@ -4,7 +4,7 @@
 @settitle WoMan: Browse Unix Manual Pages ``W.O. (without) Man''
 @c FIXME
 @c Manual last updated:
-@set UPDATED Time-stamp: <2012-12-31 21:44:20 eggert>
+@set UPDATED Time-stamp: <2013-02-12 09:05:54 eggert>
 @c Software version:
 @set VERSION 0.54 (beta)
 @afourpaper
@@ -929,7 +929,7 @@ for a man configuration file.  The default is
 
 @noindent
 [for GNU/Linux and Cygwin respectively.]  A trailing separator (@file{/}
-for UNIX etc.) on directories is optional and the filename matched if a
+for UNIX etc.)@: on directories is optional and the filename matched if a
 directory is specified is the first to match the regexp
 @code{man.*\.conf}.  If the environment variable @code{MANPATH} is not
 set but a configuration file is found then it is parsed instead (or as