changeset 76878:e4d2810db0e9

wording matters

--- a/lispref/ChangeLog	Sun Apr 01 17:45:58 2007 +0000
+++ b/lispref/ChangeLog	Sun Apr 01 18:11:15 2007 +0000
@@ -1,3 +1,10 @@
[phone]  Karl Berry  <[e-mail]>
+
+	* processes.texi (Low-Level Network): typo.
+	* loading.texi (Hooks for Loading): avoid double "the".
+	* keymaps.texi (Key Sequences): no double "and".
+	(Changing Key Bindings): shorten to improve line break.
+
 2007-03-31  Glenn Morris  <[e-mail]>
 
 	* os.texi (Timers): Fix description of run-at-time TIME formats.

--- a/lispref/commands.texi	Sun Apr 01 17:45:58 2007 +0000
+++ b/lispref/commands.texi	Sun Apr 01 18:11:15 2007 +0000
@@ -1605,19 +1605,19 @@
 The command is called with no arguments, and the specific signal event is
 available in @code{last-input-event}.  For example:
 
-@example
+@smallexample
 (defun sigusr-handler ()
   (interactive)
   (message "Caught signal %S" last-input-event))
 
 (define-key special-event-map [sigusr1] 'sigusr-handler)
-@end example
+@end smallexample
 
 To test the signal handler, you can make Emacs send a signal to itself:
 
-@example
+@smallexample
 (signal-process (emacs-pid) 'sigusr1)
-@end example
+@end smallexample
 @end table
 
   If one of these events arrives in the middle of a key sequence---that

--- a/lispref/keymaps.texi	Sun Apr 01 17:45:58 2007 +0000
+++ b/lispref/keymaps.texi	Sun Apr 01 18:11:15 2007 +0000
@@ -53,7 +53,7 @@
 a key sequence as an argument can handle both representations.
 
   In the string representation, alphanumeric characters ordinarily
-stand for themselves; for example, @code{"a"} represents @kbd{a} and
+stand for themselves; for example, @code{"a"} represents @kbd{a}
 and @code{"2"} represents @kbd{2}.  Control character events are
 prefixed by the substring @code{"\C-"}, and meta characters by
 @code{"\M-"}; for example, @code{"\C-x"} represents the key @kbd{C-x}.
@@ -1278,7 +1278,7 @@
 does matter for menu keymaps (@pxref{Menu Keymaps}).
 @end defun
 
-  Here is an example that creates a sparse keymap and makes a number of
+  This example creates a sparse keymap and makes a number of
 bindings in it:
 
 @smallexample

--- a/lispref/loading.texi	Sun Apr 01 17:45:58 2007 +0000
+++ b/lispref/loading.texi	Sun Apr 01 18:11:15 2007 +0000
@@ -64,22 +64,23 @@
 
 To find the file, @code{load} first looks for a file named
 @file{@var{filename}.elc}, that is, for a file whose name is
-@var{filename} with @samp{.elc} appended.  If such a file exists, it is
-loaded.  If there is no file by that name, then @code{load} looks for a
-file named @file{@var{filename}.el}.  If that file exists, it is loaded.
-Finally, if neither of those names is found, @code{load} looks for a
-file named @var{filename} with nothing appended, and loads it if it
-exists.  (The @code{load} function is not clever about looking at
-@var{filename}.  In the perverse case of a file named @file{foo.el.el},
-evaluation of @code{(load "foo.el")} will indeed find it.)
+@var{filename} with the extension @samp{.elc} appended.  If such a
+file exists, it is loaded.  If there is no file by that name, then
+@code{load} looks for a file named @file{@var{filename}.el}.  If that
+file exists, it is loaded.  Finally, if neither of those names is
+found, @code{load} looks for a file named @var{filename} with nothing
+appended, and loads it if it exists.  (The @code{load} function is not
+clever about looking at @var{filename}.  In the perverse case of a
+file named @file{foo.el.el}, evaluation of @code{(load "foo.el")} will
+indeed find it.)
 
-If Auto Compression mode is enabled, as it is by default, then
-if @code{load} can not find a file, it searches for a compressed
-version of the file before trying other file names.  It decompresses
-and loads it if it exists.  It looks for compressed versions by
-appending the suffixes in @code{jka-compr-load-suffixes} to the file
-name.  The value of this variable must be a list of strings. Its
-standard value is @code{(".gz")}.
+If Auto Compression mode is enabled, as it is by default, then if
+@code{load} can not find a file, it searches for a compressed version
+of the file before trying other file names.  It decompresses and loads
+it if it exists.  It looks for compressed versions by appending each
+of the suffixes in @code{jka-compr-load-suffixes} to the file name.
+The value of this variable must be a list of strings. Its standard
+value is @code{(".gz")}.
 
 If the optional argument @var{nosuffix} is non-@code{nil}, then
 @code{load} does not try the suffixes @samp{.elc} and @samp{.el}.  In
@@ -958,7 +959,7 @@
 
 The key @var{regexp-or-feature} is either a regular expression or a
 symbol, and the value is a list of forms.  The forms are evaluated when
-the key matches the the absolute true name of the file being
+the key matches the absolute true name of the file being
 @code{load}ed or the symbol being @code{provide}d.
 @end defvar
 

--- a/lispref/processes.texi	Sun Apr 01 17:45:58 2007 +0000
+++ b/lispref/processes.texi	Sun Apr 01 18:11:15 2007 +0000
@@ -1726,7 +1726,7 @@
 @section Low-Level Network Access
 
   You can also create network connections by operating at a lower
-level that that of @code{open-network-stream}, using
+level than that of @code{open-network-stream}, using
 @code{make-network-process}.
 
 @menu