Spacing and punctuation fixes

diff --git a/texi/auth.texi b/texi/auth.texi
index deb9dc9..0d5da95 100644 (file)
--- a/texi/auth.texi
+++ b/texi/auth.texi
@@ -111,9 +111,9 @@ You can use spaces inside a password or other token by surrounding the
 token with either single or double quotes.
 
 You can use single quotes inside a password or other token by
 token with either single or double quotes.
 
 You can use single quotes inside a password or other token by

-surrounding it with double quotes, e.g. @code{"he'llo"}. Similarly you
+surrounding it with double quotes, e.g., @code{"he'llo"}. Similarly you

 can use double quotes inside a password or other token by surrounding
 can use double quotes inside a password or other token by surrounding

-it with single quotes, e.g. @code{'he"llo'}. You can't mix both (so a
+it with single quotes, e.g., @code{'he"llo'}. You can't mix both (so a

 password or other token can't have both single and double quotes).
 
 All this is optional. You could just say (but we don't recommend it,
 password or other token can't have both single and double quotes).
 
 All this is optional. You could just say (but we don't recommend it,

diff --git a/texi/gnus.texi b/texi/gnus.texi
index 97b662a..b448d3e 100644 (file)
--- a/texi/gnus.texi
+++ b/texi/gnus.texi
@@ -11482,7 +11482,7 @@ who wrote the article, the date it was written and the subject of the
 article.  That's well and nice, but there's also lots of information
 most people do not want to see---what systems the article has passed
 through before reaching you, the @code{Message-ID}, the
 article.  That's well and nice, but there's also lots of information
 most people do not want to see---what systems the article has passed
 through before reaching you, the @code{Message-ID}, the

-@code{References}, etc. ad nauseam---and you'll probably want to get rid
+@code{References}, etc.@: ad nauseam---and you'll probably want to get rid

 of some of those lines.  If you want to keep all those lines in the
 article buffer, you can set @code{gnus-show-all-headers} to @code{t}.
 
 of some of those lines.  If you want to keep all those lines in the
 article buffer, you can set @code{gnus-show-all-headers} to @code{t}.
 


@@ -25905,7 +25905,7 @@ Store custom flags and keywords
 The registry can store custom flags and keywords for a message.  For
 instance, you can mark a message ``To-Do'' this way and the flag will
 persist whether the message is in the nnimap, nnml, nnmaildir,
 The registry can store custom flags and keywords for a message.  For
 instance, you can mark a message ``To-Do'' this way and the flag will
 persist whether the message is in the nnimap, nnml, nnmaildir,

-etc. backends.
+etc.@: backends.

 
 @item
 Store arbitrary data
 
 @item
 Store arbitrary data


@@ -25988,7 +25988,7 @@ registry will be pruned back to less than
 @code{gnus-registry-max-entries}.  This option controls exactly how
 much less: the target is calculated as the maximum number of entries
 minus the maximum number times this factor.  The default is 0.1:
 @code{gnus-registry-max-entries}.  This option controls exactly how
 much less: the target is calculated as the maximum number of entries
 minus the maximum number times this factor.  The default is 0.1:

-i.e. if your registry is limited to 50000 entries, pruning will try to
+i.e., if your registry is limited to 50000 entries, pruning will try to

 cut back to 45000 entries.  Entries with keys marked as precious will
 not be pruned.
 @end defvar
 cut back to 45000 entries.  Entries with keys marked as precious will
 not be pruned.
 @end defvar