[Emacs-diffs] emacs-24 r117378: Fix bug #18025 with typos in Emacs Lisp Introduction manual.

[Eli Zaretskii]

------------------------------------------------------------
revno: 117378
revision-id: address@hidden
parent: address@hidden
fixes bug: http://debbugs.gnu.org/18025
author: Alvar Jesus Ibeas Martin <address@hidden>
committer: Eli Zaretskii <address@hidden>
branch nick: emacs-24
timestamp: Tue 2014-07-15 19:06:49 +0300
message:
  Fix bug #18025 with typos in Emacs Lisp Introduction manual.
  
   doc/lispintro/emacs-lisp-intro.texi (Variables, Buffer Names, if & or)
   (Symbols as Chest, fwd-para while): Fix typos.
modified:
  doc/lispintro/ChangeLog        changelog-20091113204419-o5vbwnq5f7feedwu-6128
  doc/lispintro/emacs-lisp-intro.texi 
emacslispintro.texi-20091113204419-o5vbwnq5f7feedwu-6143

=== modified file 'doc/lispintro/ChangeLog'
--- a/doc/lispintro/ChangeLog   2014-06-29 02:33:50 +0000
+++ b/doc/lispintro/ChangeLog   2014-07-15 16:06:49 +0000
@@ -1,3 +1,8 @@
+2014-07-15  Álvar Jesús Ibeas Martín  <address@hidden>  (tiny change)
+
+       * emacs-lisp-intro.texi (Variables, Buffer Names, if & or)
+       (Symbols as Chest, fwd-para while): Fix typos.
+
 2014-06-29  Glenn Morris  <address@hidden>
 
        * emacs-lisp-intro.texi (Note for Novices, Finding More, Conclusion):

=== modified file 'doc/lispintro/emacs-lisp-intro.texi'
--- a/doc/lispintro/emacs-lisp-intro.texi       2014-06-29 02:33:50 +0000
+++ b/doc/lispintro/emacs-lisp-intro.texi       2014-07-15 16:06:49 +0000
@@ -1700,7 +1700,7 @@
 of drawers.  The function definition is put in one drawer, the value in
 another, and so on.  What is put in the drawer holding the value can be
 changed without affecting the contents of the drawer holding the
-function definition, and vice-verse.
+function definition, and vice versa.
 
 @menu
 * fill-column Example::
@@ -2653,7 +2653,7 @@
 evaluate the symbols as variables.  @xref{Variables}.)
 
 In spite of the distinction between files and buffers, you will often
-find that people refer to a file when they mean a buffer and vice-verse.
+find that people refer to a file when they mean a buffer and vice versa.
 Indeed, most people say, ``I am editing a file,'' rather than saying,
 ``I am editing a buffer which I will soon save to a file.''  It is
 almost always clear from context what people mean.  When dealing with
@@ -5756,7 +5756,7 @@
 @noindent
 @code{not} is a function that returns true if its argument is false
 and false if its argument is true.  So if @code{(bufferp buffer)}
-returns true, the @code{not} expression returns false and vice-verse:
+returns true, the @code{not} expression returns false and vice versa:
 what is ``not true'' is false and what is ``not false'' is true.
 
 Using this test, the @code{if} expression works as follows: when the
@@ -9805,7 +9805,7 @@
 being a chest of drawers.  The function definition is put in one
 drawer, the value in another, and so on.  What is put in the drawer
 holding the value can be changed without affecting the contents of the
-drawer holding the function definition, and vice-verse.
+drawer holding the function definition, and vice versa.
 
 Actually, what is put in each drawer is the address of the value or
 function definition.  It is as if you found an old chest in the attic,
@@ -13235,7 +13235,7 @@
 @noindent
 This @code{while} loop has us searching forward for
 @code{sp-parstart}, which is the combination of possible whitespace
-with a the local value of the start of a paragraph or of a paragraph
+with the local value of the start of a paragraph or of a paragraph
 separator.  (The latter two are within an expression starting
 @code{\(?:} so that they are not referenced by the
 @code{match-beginning} function.)