Fix typos.

diff --git a/lispref/display.texi b/lispref/display.texi
index 75a64924516b4db0612e91d803cbecec95cc16fa..14d44a1b99514d0c16d9408709a15dd95a702d4e 100644 (file)
--- a/lispref/display.texi
+++ b/lispref/display.texi
@@ -1099,7 +1099,7 @@ object that belongs to a particular buffer, and has a specified
 beginning and end.  It also has properties that you can examine and set;
 these affect the display of the text within the overlay.
 
-An overlays uses markers to record its beginning and end; thus,
+An overlay uses markers to record its beginning and end; thus,
 editing the text of the buffer adjusts the beginning and end of each
 overlay so that it stays with the text.  When you create the overlay,
 you can specify whether text inserted at the beginning should be
@@ -1737,7 +1737,7 @@ The purpose of @var{spec} is to specify how the face should appear on
 different kinds of terminals.  It should be an alist whose elements
 have the form @code{(@var{display} @var{atts})}.  Each element's
 @sc{car}, @var{display}, specifies a class of terminals.  (The first
-element, if it s @sc{car} is @code{default}, is special---it specifies
+element, if its @sc{car} is @code{default}, is special---it specifies
 defaults for the remaining elements).  The element's @sc{cadr},
 @var{atts}, is a list of face attributes and their values; it
 specifies what the face should look like on that kind of terminal.
@@ -4258,8 +4258,8 @@ this is a simple underline, like a typical web-page link.
 
   For convenience, there are two sorts of button-creation functions,
 those that add button properties to an existing region of a buffer,
-called @code{make-...button}, and those also insert the button text,
-called @code{insert-...button}.
+called @code{make-...button}, and those that also insert the button
+text, called @code{insert-...button}.
 
   The button-creation functions all take the @code{&rest} argument
 @var{properties}, which should be a sequence of @var{property value}

diff --git a/lispref/keymaps.texi b/lispref/keymaps.texi
index 40165963e37fad52a25532ad110f4cd5e6d86ade..f30fb5c9659fd61b0d081266eb196358640fe30b 100644 (file)
--- a/lispref/keymaps.texi
+++ b/lispref/keymaps.texi
@@ -569,7 +569,7 @@ additional active keymaps through the variable
 text or overlay property.  If that is non-@code{nil}, it is the first
 keymap to be processed, in normal circumstances.
 
-  However, there are also special ways for program can to substitute
+  However, there are also special ways for programs to substitute
 other keymaps for some of those.  The variable
 @code{overriding-local-map}, if non-@code{nil}, specifies a keymap
 that replaces all the usual active keymaps except the global keymap.

diff --git a/lispref/modes.texi b/lispref/modes.texi
index 15954ed1d1decda512f83706ad95b547f3a835f8..ed6f0bc7f8267bd245b9b6a79ca44e4a2bcc87b6 100644 (file)
--- a/lispref/modes.texi
+++ b/lispref/modes.texi
@@ -1423,7 +1423,7 @@ variable @code{@var{mode}-hook}.
 @end defmac
 
   The initial value must be @code{nil} except in cases where (1) the
-mode is preloaded in Emacs, or (2) it is painless to for loading to
+mode is preloaded in Emacs, or (2) it is painless for loading to
 enable the mode even though the user did not request it.  For
 instance, if the mode has no effect unless something else is enabled,
 and will always be loaded by that time, enabling it by default is
@@ -2254,7 +2254,7 @@ If this variable is non-@code{nil}, its value should be a function that
 finds the next ``definition'' to put in the buffer index, scanning
 backward in the buffer from point.  It should return @code{nil} if it
 doesn't find another ``definition'' before point.  Otherwise it should
-leave point at the place it finds a ``definition,'' and return any
+leave point at the place it finds a ``definition'' and return any
 non-@code{nil} value.
 
 Setting this variable makes it buffer-local in the current buffer.

diff --git a/lispref/positions.texi b/lispref/positions.texi
index d1a7813aa60369e15a26b291b4d55b2eac9527a1..83ac383ddae2b57ab87fea81c4cab122d0d991a9 100644 (file)
--- a/lispref/positions.texi
+++ b/lispref/positions.texi
@@ -417,7 +417,7 @@ Here is an example of using @code{count-lines}:
 @defun line-number-at-pos &optional pos
 @cindex line number
 This function returns the line number in the current buffer
-corresponding the buffer position @var{pos}.  If @var{pos} is @code{nil}
+corresponding to the buffer position @var{pos}.  If @var{pos} is @code{nil}
 or omitted, the current buffer position is used.
 @end defun
 

diff --git a/lispref/text.texi b/lispref/text.texi
index b37715be5a0cdb13fa48c81292e825562a528e46..8e269cbbd5636ccff77ccd7b92b0ca084694fe8e 100644 (file)
--- a/lispref/text.texi
+++ b/lispref/text.texi
@@ -2714,7 +2714,7 @@ list.
 
 @defun remove-list-of-text-properties start end list-of-properties &optional object
 Like @code{remove-text-properties} except that
-@var{list-of-properties} is a list property names only, not an
+@var{list-of-properties} is a list of property names only, not an
 alternating list of property names and values.
 @end defun