*** empty log message ***

3 files changed, 4 insertions, 4 deletions

diff --git a/lispref/debugging.texi b/lispref/debugging.texi
index 62e78263ff8..bb719ee99a6 100644
--- a/lispref/debugging.texi
+++ b/lispref/debugging.texi
@@ -732,7 +732,7 @@ found the discrepancy, undo the @kbd{C-M-q} with @kbd{C-_}, since the
 old indentation is probably appropriate to the intended parentheses.
 
   After you think you have fixed the problem, use @kbd{C-M-q} again.  If
-the old indentation actually fit the intended nesting of parentheses,
+the old indentation actually fits the intended nesting of parentheses,
 and you have put back those parentheses, @kbd{C-M-q} should not change
 anything.
 
diff --git a/lispref/edebug.texi b/lispref/edebug.texi
index d06275bb9f7..6f7b3af59f4 100644
--- a/lispref/edebug.texi
+++ b/lispref/edebug.texi
@@ -97,7 +97,7 @@ which stops execution.  @xref{Edebug Execution Modes}.
 
   Within Edebug, you normally view an Emacs buffer showing the source of
 the Lisp code you are debugging.  This is referred to as the @dfn{source
-code buffer}, and is is temporarily read-only.
+code buffer}, and it is temporarily read-only.
 
   An arrow at the left margin indicates the line where the function is
 executing.  Point initially shows where within the line the function is
diff --git a/lispref/sequences.texi b/lispref/sequences.texi
index 0b9e2901977..dd64c9af269 100644
--- a/lispref/sequences.texi
+++ b/lispref/sequences.texi
@@ -221,8 +221,8 @@ in the list.
   Emacs defines four types of array, all one-dimensional: @dfn{strings},
 @dfn{vectors}, @dfn{bool-vectors} and @dfn{char-tables}.  A vector is a
 general array; its elements can be any Lisp objects.  A string is a
-specialized array; its elements must be characters (i.e., integers
-between 0 and 255).  Each type of array has its own read syntax.
+specialized array; its elements must be characters.  Each type of array 
+has its own read syntax.
 @xref{String Type}, and @ref{Vector Type}.
 
   All four kinds of array share these characteristics: