changeset 24952:a6db4671c7a0

*** empty log message ***

--- a/lispref/customize.texi	Sat Jul 17 02:15:13 1999 +0000
+++ b/lispref/customize.texi	Sat Jul 17 02:23:12 1999 +0000
@@ -385,9 +385,9 @@
 the hook; see @ref{Variable Definitions}.
 
 @item alist
-The value must be a list of cons-cells, the car of each cell
-representing a key, and the cdr of the same cell representing and
-associated value.  The use can add and a delete key/value pairs, and
+The value must be a list of cons-cells, the @sc{car} of each cell
+representing a key, and the @sc{cdr} of the same cell representing an
+associated value.  The user can add and delete key/value pairs, and
 edit both the key and the value of each pair.
 
 You can specify the key and value types like this:
@@ -444,7 +444,7 @@
 :options '("foo" ((function-item some-function) integer) "baz")
 @end example
 
-Many alist uses lists with two elements, instead of cons cells.  For
+Many alists use lists with two elements, instead of cons cells.  For
 example,
 
 @example

--- a/lispref/files.texi	Sat Jul 17 02:15:13 1999 +0000
+++ b/lispref/files.texi	Sat Jul 17 02:23:12 1999 +0000
@@ -113,8 +113,8 @@
 buffer and reads the file into it.  You may make the buffer current or
 display it in a window if you wish, but this function does not do so.
 
-If @var{wildcards} is non-@code{nil}, which is always true in an
-interactive call, then @code{find-file-noselect} expands wildcard
+If @var{wildcards} is non-@code{nil},
+then @code{find-file-noselect} expands wildcard
 characters in @var{filename} and visits all the matching files.
 
 When @code{find-file-noselect} uses an existing buffer, it first
@@ -1925,9 +1925,9 @@
 @tindex file-expand-wildcards
 @defun file-expand-wildcards pattern &optional full
 This function expands the wildcard pattern @var{pattern}, returning
-alist of file names that match it.
+a list of file names that match it.
 
-If @var{pattern} is written as an absolute relative file name,
+If @var{pattern} is written as an absolute file name,
 the values are absolute also.
 
 If @var{pattern} is written as a relative file name, it is interpreted

--- a/lispref/keymaps.texi	Sat Jul 17 02:15:13 1999 +0000
+++ b/lispref/keymaps.texi	Sat Jul 17 02:23:12 1999 +0000
@@ -1639,7 +1639,7 @@
 (menu-item "Debug on Error" toggle-debug-on-error
            :button (:toggle
                     . (and (boundp 'debug-on-error)
-                           debug-on-error))
+                           debug-on-error)))
 @end example
 
 @noindent

--- a/lispref/nonascii.texi	Sat Jul 17 02:15:13 1999 +0000
+++ b/lispref/nonascii.texi	Sat Jul 17 02:23:12 1999 +0000
@@ -64,8 +64,8 @@
 
   In a buffer, the buffer-local value of the variable
 @code{enable-multibyte-characters} specifies the representation used.
-The representation for a string is determined when the string is
-constructed and recorded in the string.
+The representation for a string is determined and recorded in the string
+when the string is constructed.
 
 @defvar enable-multibyte-characters
 @tindex enable-multibyte-characters
@@ -984,7 +984,7 @@
 matter it is not worth the trouble to treat this case differently.
 
   When a multibyte buffer contains illegitimate byte sequences,
-sometimes insertion or deleteion can cause them to coalesce into a
+sometimes insertion or deletion can cause them to coalesce into a
 legitimate multibyte character.  For example, suppose the buffer
 contains the sequence 129 68 192, 68 being the character @samp{D}.  If
 you delete the @samp{D}, the bytes 129 and 192 become adjacent, and thus