[Emacs-diffs] Changes to emacs/lispref/modes.texi,v

[Richard M. Stallman]

CVSROOT:        /cvsroot/emacs
Module name:    emacs
Changes by:     Richard M. Stallman <rms>       06/07/18 00:04:37

Index: modes.texi
===================================================================
RCS file: /cvsroot/emacs/emacs/lispref/modes.texi,v
retrieving revision 1.143
retrieving revision 1.144
diff -u -b -r1.143 -r1.144
--- modes.texi  17 Jul 2006 20:56:18 -0000      1.143
+++ modes.texi  18 Jul 2006 00:04:37 -0000      1.144
@@ -145,7 +145,7 @@
 
 It is best to design your hook functions so that the order in which they
 are executed does not matter.  Any dependence on the order is ``asking
-for trouble''.  However, the order is predictable: normally,
+for trouble.''  However, the order is predictable: normally,
 @var{function} goes at the front of the hook list, so it will be
 executed first (barring another @code{add-hook} call).  If the optional
 argument @var{append} is address@hidden, the new hook function goes at
@@ -1139,7 +1139,7 @@
 
   When you defined a major mode using @code{define-derived-mode}, it
 automatically makes sure these conventions are followed.  If you
-define a major mode ``from scratch'', not using
+define a major mode ``from scratch,'' not using
 @code{define-derived-mode}, make sure the major mode command follows
 these and other conventions.  @xref{Major Mode Conventions}.  You use
 these functions to do it properly.
@@ -1456,7 +1456,7 @@
 @end smallexample
 
 @noindent
-This defines a minor mode named ``Hungry mode'', a command named
+This defines a minor mode named ``Hungry mode,'' a command named
 @code{hungry-mode} to toggle it, a variable named @code{hungry-mode}
 which indicates whether the mode is enabled, and a variable named
 @code{hungry-mode-map} which holds the keymap that is active when the