fixed errors that appeared during update to 19.29.

diff --git a/lispref/compile.texi b/lispref/compile.texi
index 6e472b88300187a33ef509e43c0c67c59f10b0ce..c085634c39b07bf9e08ce2036e50b6a47c105879 100644 (file)
--- a/lispref/compile.texi
+++ b/lispref/compile.texi
@@ -238,7 +238,7 @@ call to @code{byte-code}.
 
   Functions and variables loaded from a byte-compiled file access their
 documentation strings dynamically from the file whenever needed.  This
-saves space within Emacs, and make loading faster because the
+saves space within Emacs, and makes loading faster because the
 documentation strings themselves need not be processed while loading the
 file.  Actual access to the documentation strings becomes slower as a
 result, but this normally is not enough to bother users.

diff --git a/lispref/loading.texi b/lispref/loading.texi
index 3f88132b20b00181ee7c65f6364eb06d24a74c62..2694dc44a19d6bdecee8a58585f8ffd47e4449f0 100644 (file)
--- a/lispref/loading.texi
+++ b/lispref/loading.texi
@@ -181,7 +181,7 @@ without altering @code{load-path}.
 Dumping Emacs uses a special value of @code{load-path}.  If the value of
 @code{load-path} at the end of dumping is unchanged (that is, still the
 same special value), the dumped Emacs switches to the ordinary
-@code{load-path} value when it starts up, as decribed above.  But if
+@code{load-path} value when it starts up, as described above.  But if
 @code{load-path} has any other value at the end of dumping, that value
 is used for execution of the dumped Emacs also.
 
@@ -616,7 +616,7 @@ execution of the rest of @var{form}.
 In general, well-designed Lisp programs should not use this feature.
 The clean and modular ways to interact with a Lisp library are (1)
 examine and set the library's variables (those which are meant for
-outside use), and and (2) call the library's functions.  If you wish to
+outside use), and (2) call the library's functions.  If you wish to
 do (1), you can do it immediately---there is no need to wait for when
 the library is loaded.  To do (2), you must load the library (preferably
 with @code{require}).

diff --git a/lispref/numbers.texi b/lispref/numbers.texi
index e7db42f727b9c74ebf7762c8515d562e405bebe6..7b6ef86814200566c967245e8dcb6f83fffa28e9 100644 (file)
--- a/lispref/numbers.texi
+++ b/lispref/numbers.texi
@@ -690,7 +690,7 @@ In binary, in the 28-bit implementation, the argument looks like this:
 
 @example
 @group
-;; @r{Decimal 134.217,727}
+;; @r{Decimal 134,217,727}
 0111  1111 1111  1111 1111  1111 1111         
 @end group
 @end example

diff --git a/lispref/symbols.texi b/lispref/symbols.texi
index 1921dec922cec98c6c79015ea26da18d82d63531..cbe1deea7476910f1a3a836491636d62de1e7256 100644 (file)
--- a/lispref/symbols.texi
+++ b/lispref/symbols.texi
@@ -506,7 +506,7 @@ stored in the property list @var{plist}.  For example,
 @defun plist-put plist property value
 This stores @var{value} as the value of the @var{property} property in
 the property list @var{plist}.  It may modify @var{plist} destructively,
-or it may construct new list structure without altering the old.  The
+or it may construct a new list structure without altering the old.  The
 function returns the modified property list, so you can store that back
 in the place where you got @var{plist}.  For example,