[gnus git] branch master updated: n0-17-418-g1d2202c =1= Fix typos.

       via  1d2202caaa05cd0afb7cf75314f263ee1e2ae574 (commit)
      from  1f82fce27d889186b9d784a36fa372ea849265de (commit)


- Log -----------------------------------------------------------------
commit 1d2202caaa05cd0afb7cf75314f263ee1e2ae574
Author: Juanma Barranquero <[email protected]>
Date:   Tue Dec 6 04:34:02 2011 +0000

    Fix typos.

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index bb3c122..9d570f2 100644
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,7 @@
+2011-12-06  Juanma Barranquero  <[email protected]>
+
+	* gnus-sum.el (gnus-summary-make-tool-bar): Fix typo.
+
 2011-12-05  Paul Eggert  <[email protected]>
 
 	* netrc.el (netrc-credentials): Spelling fix.
diff --git a/lisp/gnus-sum.el b/lisp/gnus-sum.el
index 7108106..10d1b46 100644
--- a/lisp/gnus-sum.el
+++ b/lisp/gnus-sum.el
@@ -2969,7 +2969,7 @@ When FORCE, rebuild the tool bar."
 					'gnus-summary-mode-map)))
       (when map
 	;; Need to set `gnus-summary-tool-bar-map' because `gnus-article-mode'
-	;; uses it's value.
+	;; uses its value.
 	(setq gnus-summary-tool-bar-map map))))
   (set (make-local-variable 'tool-bar-map) gnus-summary-tool-bar-map))
 
diff --git a/texi/ChangeLog b/texi/ChangeLog
index 5ffe9f2..e6aa9fe 100644
--- a/texi/ChangeLog
+++ b/texi/ChangeLog
@@ -1,3 +1,7 @@
+2011-12-06  Juanma Barranquero  <[email protected]>
+
+	* gnus-faq.texi (FAQ 2-1, FAQ 3-8, FAQ 4-14, FAQ 9-1): Fix typos.
+
 2011-12-05  Paul Eggert  <[email protected]>
 
 	* gnus.texi (Article Washing): Spelling fix.
diff --git a/texi/gnus-faq.texi b/texi/gnus-faq.texi
index b5bb75f..ace7bb4 100644
--- a/texi/gnus-faq.texi
+++ b/texi/gnus-faq.texi
@@ -266,9 +266,9 @@ and how to prevent it?
 @subsubheading Answer
 
 This message means that the last time you used Gnus, it
-wasn't properly exited and therefor couldn't write its
-informations to disk (e.g. which messages you read), you
-are now asked if you want to restore those informations
+wasn't properly exited and therefore couldn't write its
+information to disk (e.g. which messages you read), you
+are now asked if you want to restore that information
 from the auto-save file.
 
 To prevent this message make sure you exit Gnus
@@ -563,7 +563,7 @@ However, the first thing to do is to tell Gnus in which way
 it should store the mail, in Gnus terminology which back end
 to use. Gnus supports many different back ends, the most
 commonly used one is nnml. It stores every mail in one file
-and is therefor quite fast. However you might prefer a one
+and is therefore quite fast. However you might prefer a one
 file per group approach if your file system has problems with
 many small files, the nnfolder back end is then probably the
 choice for you.  To use nnml add the following to ~/.gnus.el:
@@ -580,7 +580,7 @@ As you might have guessed, if you want nnfolder, it's
 @end example
 @noindent
 
-Now we need to tell Gnus, where to get it's mail from. If
+Now we need to tell Gnus, where to get its mail from. If
 it's a POP3 server, then you need something like this:
 
 @example
@@ -1104,11 +1104,11 @@ I don't like the way the Summary buffer looks, how to tweak it?
 @subsubheading Answer
 
 You've got to play around with the variable
-gnus-summary-line-format. It's value is a string of
+gnus-summary-line-format. Its value is a string of
 symbols which stand for things like author, date, subject
 etc. A list of the available specifiers can be found in the
 manual node "Summary Buffer Lines" and the often forgotten
-node "Formatting Variables" and it's sub-nodes. There
+node "Formatting Variables" and its sub-nodes. There
 you'll find useful things like positioning the cursor and
 tabulators which allow you a summary in table form, but
 sadly hard tabulators are broken in 5.8.8.
@@ -2190,7 +2190,7 @@ Starting Gnus is really slow, how to speed it up?
 
 @subsubheading Answer
 
-The reason for this could be the way Gnus reads it's
+The reason for this could be the way Gnus reads its
 active file, see the node "The Active File" in the Gnus
 manual for things you might try to speed the process up.
 An other idea would be to byte compile your ~/.gnus.el (say

-----------------------------------------------------------------------
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we listed those
revisions in full, above.

Summary of changes:
 lisp/ChangeLog     |    4 ++++
 lisp/gnus-sum.el   |    2 +-
 texi/ChangeLog     |    4 ++++
 texi/gnus-faq.texi |   16 ++++++++--------
 4 files changed, 17 insertions(+), 9 deletions(-)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Gnus Project".

The branch, master has been updated


hooks/post-receive
-- 
Gnus Project