# HG changeset patch
# User Juanma Barranquero <lekktu@gmail.com>
# Date 1168195396 0
# Node ID 61dcb71f259c9a8659a083f5d79e10867757eab2
# Parent  b9690e9e273dbcdc6e36656f2878fe7cb75c3542
(replace-regexp): Fix typo in docstring.

diff -r b9690e9e273d -r 61dcb71f259c lisp/replace.el
--- a/lisp/replace.el	Sun Jan 07 13:36:41 2007 +0000
+++ b/lisp/replace.el	Sun Jan 07 18:43:16 2007 +0000
@@ -467,10 +467,9 @@
 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