# HG changeset patch
# User Robert J. Chassell <bob@rattlesnake.com>
# Date 1050591384 0
# Node ID 0e3a9e34f995dbc0cec2fffccdc62ae70df6cb45
# Parent  c76e37ef3b1002855249ea0c0c8db064407e5eab
Thanks to Hugo Gayosso, fix minor typos.

diff -r c76e37ef3b10 -r 0e3a9e34f995 lispintro/emacs-lisp-intro.texi
--- a/lispintro/emacs-lisp-intro.texi	Thu Apr 17 02:41:12 2003 +0000
+++ b/lispintro/emacs-lisp-intro.texi	Thu Apr 17 14:56:24 2003 +0000
@@ -5681,7 +5681,7 @@
 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
-value of the variable @code{buffer} is actually a buffer rather then
+value of the variable @code{buffer} is actually a buffer rather than
 its name, the true-or-false-test returns false and the @code{if}
 expression does not evaluate the then-part.  This is fine, since we do
 not need to do anything to the variable @code{buffer} if it really is
@@ -8337,7 +8337,7 @@
 argument.  In this case, this is the expression @code{(< end beg)}.
 This expression does not directly determine whether the killed text in
 this command is located before or after the kill text of the last
-command; what is does is determine whether the value of the variable
+command; what it does is determine whether the value of the variable
 @code{end} is less than the value of the variable @code{beg}.  If it
 is, it means that the user is most likely heading towards the
 beginning of the buffer.  Also, the result of evaluating the predicate