(Buffer Modification): Fix typo.

2 files changed, 7 insertions, 3 deletions

diff --git a/lispref/ChangeLog b/lispref/ChangeLog
index 0d42aac5c85..7febc50fdef 100644
--- a/lispref/ChangeLog
+++ b/lispref/ChangeLog
@@ -1,3 +1,7 @@
+2008-01-19  Martin Rudalics  <rudalics@gmx.at>
+
+        * buffers.texi (Buffer Modification): Fix typo.
+
 2008-01-04  Richard Stallman  <rms@gnu.org>
 
         * display.texi (Faces): Don't talk about internal face vector as arg
@@ -38,7 +42,7 @@
 
 2007-11-24  Richard Stallman  <rms@gnu.org>
 
-        * display.texi (Refresh Screen, Forcing Redisplay): 
+        * display.texi (Refresh Screen, Forcing Redisplay):
         Clarify the text and move items around.
 
 2007-11-15  Martin Rudalics  <rudalics@gmx.at>
diff --git a/lispref/buffers.texi b/lispref/buffers.texi
index d2bbc9bb4d9..658da3a1df2 100644
--- a/lispref/buffers.texi
+++ b/lispref/buffers.texi
@@ -584,7 +584,7 @@ The counter can wrap around occasionally.
 This function returns @var{buffer}'s character-change modification-count.
 Changes to text properties leave this counter unchanged; however, each
 time text is inserted or removed from the buffer, the counter is reset
-to the value that would be returned @code{buffer-modified-tick}.
+to the value that would be returned by @code{buffer-modified-tick}.
 By comparing the values returned by two @code{buffer-chars-modified-tick}
 calls, you can tell whether a character change occurred in that buffer
 in between the calls.  If @var{buffer} is @code{nil} (or omitted), the
@@ -783,7 +783,7 @@ are selected for display in a window (@pxref{Displaying Buffers}), and
 to the end when they are buried (see @code{bury-buffer}, below).
 There are no functions available to the Lisp programmer which directly
 manipulate the buffer list.
-  
+
   In addition to the fundamental Emacs buffer list, each frame has its
 own version of the buffer list, in which the buffers that have been
 selected in that frame come first, starting with the buffers most