Spelling fixes.

6 files changed, 26 insertions, 26 deletions

diff --git a/doc/emacs/display.texi b/doc/emacs/display.texi
index 2313d117a90..90bfcf147c5 100644
--- a/doc/emacs/display.texi
+++ b/doc/emacs/display.texi
@@ -1065,7 +1065,7 @@ present.
   Type @kbd{M-x delete-trailing-whitespace} to delete all trailing
 whitespace.  This command deletes all extra spaces at the end of each
 line in the buffer, and all empty lines at the end of the buffer; to
-ignore the latter, change the varaible @code{delete-trailing-lines} to
+ignore the latter, change the variable @code{delete-trailing-lines} to
 @code{nil}.  If the region is active, the command instead deletes
 extra spaces at the end of each line in the region.
 
diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 93dba237013..9ffa2b74857 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -1952,7 +1952,7 @@ position such events have.
 
 @defun posnp object
 This function returns non-@code{nil} if @var{object} is a mouse
-oposition list, in either of the formats documented in @ref{Click
+position list, in either of the formats documented in @ref{Click
 Events}); and @code{nil} otherwise.
 @end defun
 
diff --git a/doc/lispref/errors.texi b/doc/lispref/errors.texi
index b7b26c8708c..b28ed6e84c4 100644
--- a/doc/lispref/errors.texi
+++ b/doc/lispref/errors.texi
@@ -148,7 +148,7 @@ The message is @samp{No catch for tag}.  @xref{Catch and Throw}.
 @ignore
 @c Not actually used for anything?  Probably definition should be removed.
 @item protected-field
-The message is @samp{Attempt to modify a protected fiel.
+The message is @samp{Attempt to modify a protected file}.
 @end ignore
 
 @item scan-error
@@ -205,7 +205,7 @@ of @code{domain-error}.
 The message is @code{Arithmetic range error}.
 
 @item singularity-error
-The mssage is @samp{Arithmetic singularity error}.  This is a
+The message is @samp{Arithmetic singularity error}.  This is a
 subcategory of @code{domain-error}.
 
 @item underflow-error
diff --git a/doc/misc/ede.texi b/doc/misc/ede.texi
index b0e149b09b6..046cdc99414 100644
--- a/doc/misc/ede.texi
+++ b/doc/misc/ede.texi
@@ -302,7 +302,7 @@ that file to your target.
 . a myprogram RET
 @end example
 
-Note that these promps often have completion, so you can just press
+Note that these prompts often have completion, so you can just press
 @kbd{TAB} to complete the name @file{myprogram}.
 
 If you had many files to add to the same target, you could mark them
@@ -785,7 +785,7 @@ also supports several debugging tools via @file{android.el}.
 An arduino project of type @samp{ede-arduino-project} will read your
 @file{~/.arduino/preferences.txt} file, and identify your sketches.
 You will still need the Arduino IDE to set up your preferences and
-locate your arduino.  After quiting the IDE, Emacs will be able to
+locate your arduino.  After quitting the IDE, Emacs will be able to
 find your sketches, compile them, and upload them to your arduino.
 
 If you have the @file{arduino} command on your path, @ede{} will be
@@ -1169,14 +1169,14 @@ Some example project types are:
 
 @table @code
 @item project-am
-Autmake project which reads existing Automake files.
+Automake project which reads existing Automake files.
 @item ede-proj-project
 This project type will create @file{Makefiles},
 or @file{Makefile.am} files to compile your project.
 @item ede-linux
 This project type will detect linux source trees.
 @item ede-emacs
-This proejct will detect an Emacs source tree.
+This project will detect an Emacs source tree.
 @end table
 
 There are several other project types as well.
@@ -1291,7 +1291,7 @@ it finds the top of the project.  It does this by calling
 @code{ede-toplevel-project}.  If this hasn't already been discovered,
 the directories as scanned upward one at a time until a directory with
 no project is found.  The last found project becomes the project
-root.  If the ofund instance of @code{ede-project-autoload} has a
+root.  If the found instance of @code{ede-project-autoload} has a
 valid @code{proj-root} slot value, then that function is called instead
 of scanning the project by hand.  Some project types have a short-cut
 for determining the root of a project, so this comes in handy.
@@ -3331,7 +3331,7 @@ Bonus: Return a cons cell: (COMPILED . UPTODATE).
 @end deffn
 
 @deffn Method ede-proj-flush-autoconf :AFTER this
-Flush the configure file (current buffer) to accomodate @var{THIS}.
+Flush the configure file (current buffer) to accommodate @var{THIS}.
 @end deffn
 
 @deffn Method ede-buffer-mine :AFTER this buffer
@@ -3920,7 +3920,7 @@ Return the default macro to 'edit' for this object type.
 @end deffn
 
 @deffn Method project-compile-target-command :AFTER this
-Default target t- use when compling a texinfo file.
+Default target to use when compiling a texinfo file.
 @end deffn
 
 @deffn Method ede-documentation :AFTER this
diff --git a/doc/misc/eieio.texi b/doc/misc/eieio.texi
index 9f3625e180f..6b3a87f19fc 100644
--- a/doc/misc/eieio.texi
+++ b/doc/misc/eieio.texi
@@ -595,7 +595,7 @@ This is the default.
 @item :depth-first
 Search for methods in the class hierarchy in a depth first order.
 @item :c3
-Searches for methods in in a learnarized way that most closely matches
+Searches for methods in in a linearized way that most closely matches
 what CLOS does when a monotonic class structure is defined.
 @end table
 
@@ -1010,7 +1010,7 @@ This is the default.
 @item :depth-first
 Search for methods in the class hierarchy in a depth first order.
 @item :c3
-Searches for methods in in a learnarized way that most closely matches
+Searches for methods in in a linearized way that most closely matches
 what CLOS does when CLOS when a monotonic class structure is defined.
 
 This is derived from the Dylan language documents by
@@ -1408,8 +1408,8 @@ provided.
 Read a persistent object from @var{filename}, and return it.
 Signal an error if the object in @var{FILENAME} is not a constructor
 for @var{CLASS}.  Optional @var{allow-subclass} says that it is ok for
-@code{eieio-peristent-read} to load in subclasses of class instead of
-being pendantic."
+@code{eieio-persistent-read} to load in subclasses of class instead of
+being pedantic.
 @end defun
 
 @node eieio-named
@@ -1564,9 +1564,9 @@ texinfo format by using the tools in the file @file{eieio-doc.el}
 
 @deffn Command eieiodoc-class class indexstring &optional skiplist
 
-This will start at the current point, and created an indented menu of
+This will start at the current point, and create an indented menu of
 all the child classes of, and including @var{class}, but skipping any
-classes that might be in @var{skiplist} It will then create nodes for
+classes that might be in @var{skiplist}.  It will then create nodes for
 all these classes, subsection headings, and indexes.
 
 Each class will be indexed using the texinfo labeled index
@@ -1585,7 +1585,7 @@ where @var{indexstring} is replaced with the two letter code.
 Next, an inheritance tree will be created listing all parents of that
 section's class.
 
-Then,all the slots will be expanded in tables, and described
+Then, all the slots will be expanded in tables, and described
 using the documentation strings from the code.  Default values will also
 be displayed.  Only those slots with @code{:initarg} specified will be
 expanded, others will be hidden.  If a slot is inherited from a parent,
diff --git a/doc/misc/org.texi b/doc/misc/org.texi
index 227af8faf10..89c99018460 100644
--- a/doc/misc/org.texi
+++ b/doc/misc/org.texi
@@ -947,7 +947,7 @@ description on Worg}.
 Installing Info files is system dependent, because of differences in the
 @file{install-info} program.  The Info documentation is installed together
 with the rest of Org mode.  If you don't install Org mode, it is possible to
-install the Info documentation seperately (you need to have
+install the Info documentation separately (you need to have
 install-info@footnote{The output from install-info (if any) is system
 dependent.  In particular Debian and its derivatives use two different
 versions of install-info and you may see the message:
@@ -2671,13 +2671,13 @@ durations computations @ref{Durations and time values}.
 @cindex Lisp forms, as table formulas
 
 It is also possible to write a formula in Emacs Lisp.  This can be useful
-for string manipulation and control structures, if Calc's functionality is 
-not enough.  
+for string manipulation and control structures, if Calc's functionality is
+not enough.
 
 If a formula starts with a single-quote followed by an opening parenthesis,
 then it is evaluated as a Lisp form.  The evaluation should return either a
 string or a number.  Just as with @file{calc} formulas, you can specify modes
-and a printf format after a semicolon.  
+and a printf format after a semicolon.
 
 With Emacs Lisp forms, you need to be conscious about the way field
 references are interpolated into the form.  By default, a reference will be
@@ -6114,7 +6114,7 @@ is only necessary if you edit the timestamps directly.  If you change
 them with @kbd{S-@key{cursor}} keys, the update is automatic.
 @orgcmd{C-S-@key{up/down},org-clock-timestamps-up/down}
 On @code{CLOCK} log lines, increase/decrease both timestamps so that the
-clock duration keeps the same. 
+clock duration keeps the same.
 @orgcmd{S-M-@key{up/down},org-timestamp-up/down}
 On @code{CLOCK} log lines, increase/decrease the timestamp at point and
 the one of the previous (or the next clock) timestamp by the same duration.
@@ -16556,7 +16556,7 @@ rely on outline paths, in the hope that these will be unique enough.}.
 Finally, Org writes the file @file{index.org}, containing links to all other
 files.  @i{MobileOrg} first reads this file from the server, and then
 downloads all agendas and Org files listed in it.  To speed up the download,
-MobileOrg will only read files whose checksums@footnote{Checksums are stored 
+MobileOrg will only read files whose checksums@footnote{Checksums are stored
 automatically in the file @file{checksums.dat}} have changed.
 
 @node Pulling from MobileOrg,  , Pushing to MobileOrg, MobileOrg
@@ -16704,7 +16704,7 @@ on @file{org-element.el} and @file{org-export.el} has been outstanding, and
 opened the doors for many new ideas and features.
 
 @item Jambunathan K
-Jambunathan contributed the ODT exporter, definitly a killer feature of
+Jambunathan contributed the ODT exporter, definitely a killer feature of
 Org mode.  He also contributed the new HTML exporter, which is another core
 feature of Org.  Here too, I knew I could rely on him to fix bugs in these
 areas and to patiently explain the users what was the problems and solutions.
@@ -16712,7 +16712,7 @@ areas and to patiently explain the users what was the problems and solutions.
 @item Achim Gratz
 Achim rewrote the building process of Org, turning some @emph{ad hoc} tools
 into a flexible and conceptually clean process.  He patiently coped with the
-many hicups that such a change can create for users.
+many hiccups that such a change can create for users.
 
 @item Nick Dokos
 The Org mode mailing list would not be such a nice place without Nick, who