(replace-regexp): Fix typo in docstring.

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 97d390e..7ada1dd 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,7 +1,11 @@
+2007-01-07  Chris Moore  <christopher.ian.moore@gmail.com>  (tiny change)
+
+       * replace.el (replace-regexp): Fix typo in docstring.
+
 2007-01-07  Alan Mackenzie  <acm@muc.de>
 
-       * progmodes/cc-langs.el (c-operators, c-filter-ops): Amend
-       doc-string and comments.
+       * progmodes/cc-langs.el (c-operators, c-filter-ops):
+       Amend doc-string and comments.
 
 2007-01-06  Eli Zaretskii  <eliz@gnu.org>
 

diff --git a/lisp/replace.el b/lisp/replace.el
index 610fd9d..c51985c 100644 (file)
--- a/lisp/replace.el
+++ b/lisp/replace.el
@@ -467,10 +467,9 @@ at the given position for each replacement.
 In interactive calls, the replacement text may contain `\\,'
 followed by a Lisp expression used as part of the replacement
 text.  Inside of that expression, `\\&' is a string denoting the
-whole match, `\\N' a partial matches, `\\#&' and `\\#N' the
-respective numeric values from `string-to-number', and `\\#'
-itself for `replace-count', the number of replacements occured so
-far.
+whole match, `\\N' a partial match, `\\#&' and `\\#N' the respective
+numeric values from `string-to-number', and `\\#' itself for
+`replace-count', the number of replacements occurred so far.
 
 If your Lisp expression is an identifier and the next letter in
 the replacement string would be interpreted as part of it, you