summaryrefslogtreecommitdiff
path: root/lisp/follow.el
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2011-11-19 23:30:16 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2011-11-19 23:30:16 -0800
commit40ba43b4b71df1d51954bdad071e74243c4aea7c (patch)
treee4cb03937e72463278264e9684481d68ece4698c /lisp/follow.el
parent24901d610c9ff524e7e7c132dca1cd4312368db0 (diff)
downloademacs-40ba43b4b71df1d51954bdad071e74243c4aea7c.tar.gz
Spelling fixes.
Diffstat (limited to 'lisp/follow.el')
-rw-r--r--lisp/follow.el2
1 files changed, 1 insertions, 1 deletions
diff --git a/lisp/follow.el b/lisp/follow.el
index 7375b15ad16..852944a8061 100644
--- a/lisp/follow.el
+++ b/lisp/follow.el
@@ -562,7 +562,7 @@ Keys specific to Follow mode:
;;
;; Almost like the real thing, except when the cursor ends up outside
;; the top or bottom... In our case however, we end up outside the
-;; window and hence we are recenterd. Should we let `recenter' handle
+;; window and hence we are recentered. Should we let `recenter' handle
;; the point position we would never leave the selected window. To do
;; it ourselves we would need to do our own redisplay, which is easier
;; said than done. (Why didn't I do a real display abstraction from