(Sorting the Summary Buffer): Index.

diff --git a/texi/ChangeLog b/texi/ChangeLog
index e07eba5..c831fe4 100644 (file)
--- a/texi/ChangeLog
+++ b/texi/ChangeLog
@@ -1,3 +1,7 @@
+2003-07-17  Jesper Harder  <harder@ifa.au.dk>
+
+       * gnus.texi (Sorting the Summary Buffer): Index.
+
 2003-07-15  Reiner Steib  <Reiner.Steib@gmx.de>
 
        * gnus-faq.texi ([3.8]): Fixed example.

diff --git a/texi/gnus.texi b/texi/gnus.texi
index e73e3bb..c396363 100644 (file)
--- a/texi/gnus.texi
+++ b/texi/gnus.texi
@@ -6908,7 +6908,8 @@ Matching}).
 @findex gnus-thread-sort-by-number
 @findex gnus-thread-sort-by-random
 @vindex gnus-thread-sort-functions
-@findex gnus-thread-sort-by-most-recent-thread
+@findex gnus-thread-sort-by-most-recent-number
+@findex gnus-thread-sort-by-most-recent-date
 If you are using a threaded summary display, you can sort the threads by
 setting @code{gnus-thread-sort-functions}, which can be either a single
 function, a list of functions, or a list containing functions and
@@ -22266,7 +22267,7 @@ non-spam messages.
 So, what happens when you load @file{spam.el}?  
 
 First of all, you @strong{must} set the variable
-@code{spam-install-hooks} to t and install the @code{spam.el} hooks:
+@code{spam-install-hooks} to @code{t} and install the @code{spam.el} hooks:
 
 @example
 (setq spam-install-hooks t)