summaryrefslogtreecommitdiff
path: root/doc/lispintro
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2017-10-09 22:53:19 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2017-10-09 22:55:06 -0700
commit5d51403ceb9b86a1bfa66f00c7af39f1200e65f1 (patch)
tree66e10eb5d1a72390812ac8e71f4dc1dc2c7d6ba3 /doc/lispintro
parent0d004ed01abb5fa025bdc9d58fce2a3abff0b6a4 (diff)
downloademacs-5d51403ceb9b86a1bfa66f00c7af39f1200e65f1.tar.gz
; Typo fixes, mostly repeated words
Diffstat (limited to 'doc/lispintro')
-rw-r--r--doc/lispintro/emacs-lisp-intro.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi
index d9493879b1d..65ded50c396 100644
--- a/doc/lispintro/emacs-lisp-intro.texi
+++ b/doc/lispintro/emacs-lisp-intro.texi
@@ -831,7 +831,7 @@ An expert programmer who reviewed this text said to me:
@i{I prefer to learn from reference manuals. I ``dive into'' each
paragraph, and ``come up for air'' between paragraphs.}
-@i{When I get to the end of a paragraph, I assume that that subject is
+@i{When I get to the end of a paragraph, I assume that subject is
done, finished, that I know everything I need (with the
possible exception of the case when the next paragraph starts talking
about it in more detail). I expect that a well written reference manual