* commands.texi (Event Input Misc):

* compile.texi (Eval During Compile):
* internals.texi (Buffer Internals):
* minibuf.texi (Initial Input):
* nonascii.texi (Scanning Charsets):
* numbers.texi (Comparison of Numbers):
* windows.texi (Textual Scrolling, Vertical Scrolling):
Fix various typos.

8 files changed, 20 insertions, 9 deletions

diff --git a/lispref/ChangeLog b/lispref/ChangeLog
index 99f2c9ab4f9..064c4f1bc5d 100644
--- a/lispref/ChangeLog
+++ b/lispref/ChangeLog
@@ -1,3 +1,14 @@
+2006-05-07  Romain Francoise  <romain@orebokech.com>
+
+        * commands.texi (Event Input Misc):
+        * compile.texi (Eval During Compile):
+        * internals.texi (Buffer Internals):
+        * minibuf.texi (Initial Input):
+        * nonascii.texi (Scanning Charsets):
+        * numbers.texi (Comparison of Numbers):
+        * windows.texi (Textual Scrolling, Vertical Scrolling):
+        Fix various typos.
+
 2006-05-06  Eli Zaretskii  <eliz@gnu.org>
 
         * hooks.texi (Standard Hooks): Replace inforef to emacs-xtra by
diff --git a/lispref/commands.texi b/lispref/commands.texi
index 797a5ced8e9..fa5d95f0408 100644
--- a/lispref/commands.texi
+++ b/lispref/commands.texi
@@ -2451,7 +2451,7 @@ If a part of @var{body} binds @code{inhibit-quit} to non-@code{nil},
 arrival of input during those parts won't cause an abort until
 the end of that part.
 
-If you want to be able to distingish all possible values computed
+If you want to be able to distinguish all possible values computed
 by @var{body} from both kinds of abort conditions, write the code
 like this:
 
diff --git a/lispref/compile.texi b/lispref/compile.texi
index 1d8823a48c5..4b796697731 100644
--- a/lispref/compile.texi
+++ b/lispref/compile.texi
@@ -412,7 +412,7 @@ automatically @code{eval-and-compile}, the package is loaded both when
 compiling and executing.
 
 @code{autoload} is also effectively @code{eval-and-compile} too.  It's
-recognised when compiling, so uses of such a function don't produce
+recognized when compiling, so uses of such a function don't produce
 ``not known to be defined'' warnings.
 
 Most uses of @code{eval-and-compile} are fairly sophisticated.
@@ -456,7 +456,7 @@ used to load it for compiling, but not executing.  For example,
 The same sort of thing goes for macros or @code{defalias}es defined
 locally and only for use within the file.  They can be defined while
 compiling, but then not needed when executing.  This is good for code
-that's only a fallback for compability with other versions of Emacs.
+that's only a fallback for compatibility with other versions of Emacs.
 For example.
 
 @lisp
diff --git a/lispref/internals.texi b/lispref/internals.texi
index 4df2421554f..f46a162aef1 100644
--- a/lispref/internals.texi
+++ b/lispref/internals.texi
@@ -1019,7 +1019,7 @@ Mode line element that controls the format of the mode line.  If this
 is @code{nil}, no mode line will be displayed.
 
 @item header_line_format
-This field is analoguous to @code{mode_line_format} for the mode
+This field is analogous to @code{mode_line_format} for the mode
 line displayed at the top of windows.
 
 @item keymap
diff --git a/lispref/minibuf.texi b/lispref/minibuf.texi
index dd96a020057..f713f12cdbf 100644
--- a/lispref/minibuf.texi
+++ b/lispref/minibuf.texi
@@ -517,7 +517,7 @@ A history list for arguments that are Lisp expressions to evaluate.
 
 Several of the functions for minibuffer input have an argument called
 @var{initial} or @var{initial-contents}.  This is a mostly-deprecated
-feature for specifiying that the minibuffer should start out with
+feature for specifying that the minibuffer should start out with
 certain text, instead of empty as usual.
 
 If @var{initial} is a string, the minibuffer starts out containing the
diff --git a/lispref/nonascii.texi b/lispref/nonascii.texi
index b09a3fc78a3..c526d419766 100644
--- a/lispref/nonascii.texi
+++ b/lispref/nonascii.texi
@@ -484,7 +484,7 @@ of the text in question.
 @defun charset-after &optional pos
 This function return the charset of a character in the current buffer
 at position @var{pos}.  If @var{pos} is omitted or @code{nil}, it
-defauls to the current value of point.  If @var{pos} is out of range,
+defaults to the current value of point.  If @var{pos} is out of range,
 the value is @code{nil}.
 @end defun
 
diff --git a/lispref/numbers.texi b/lispref/numbers.texi
index 3cbc1a7ae16..bac3b0e114c 100644
--- a/lispref/numbers.texi
+++ b/lispref/numbers.texi
@@ -322,7 +322,7 @@ returns @code{t} if so, @code{nil} otherwise.
 
 @defun eql value1 value2
 This function acts like @code{eq} except when both arguments are
-numbers.  It compares numbers by type and numberic value, so that
+numbers.  It compares numbers by type and numeric value, so that
 @code{(eql 1.0 1)} returns @code{nil}, but @code{(eql 1.0 1.0)} and
 @code{(eql 1 1)} both return @code{t}.
 @end defun
diff --git a/lispref/windows.texi b/lispref/windows.texi
index dc780e7b828..a2746889633 100644
--- a/lispref/windows.texi
+++ b/lispref/windows.texi
@@ -1419,7 +1419,7 @@ buffer is different from the buffer that is displayed in the selected
 window.  @xref{Current Buffer}.
 
   If the window contains a row which is taller than the height of the
-window (for example in the presense of a large image), the scroll
+window (for example in the presence of a large image), the scroll
 functions will adjust the window vscroll to scroll the partially
 visible row.  To disable this feature, Lisp code may bind the variable
 `auto-window-vscroll' to @code{nil} (@pxref{Vertical Scrolling}).
@@ -1656,7 +1656,7 @@ pixels.  In this case, the return value is @var{lines}.
 If this variable is non-@code{nil}, the line-move, scroll-up, and
 scroll-down functions will automatically modify the window vscroll to
 scroll through display rows that are taller that the height of the
-window, for example in the presense of large images.
+window, for example in the presence of large images.
 @end defvar
 
 @node Horizontal Scrolling