summaryrefslogtreecommitdiff
path: root/lispref/searching.texi
diff options
context:
space:
mode:
authorKarl Heuer <kwzh@gnu.org>1999-07-27 21:01:02 +0000
committerKarl Heuer <kwzh@gnu.org>1999-07-27 21:01:02 +0000
commit3f63de1e217146f1f972df87ccb7d54e14d9e840 (patch)
tree8035c70b3637b2593bfa721000aeee07cc66659c /lispref/searching.texi
parente7029763cae839439b8dc7d9fb90eb4a03de6a9c (diff)
downloademacs-3f63de1e217146f1f972df87ccb7d54e14d9e840.tar.gz
*** empty log message ***
Diffstat (limited to 'lispref/searching.texi')
-rw-r--r--lispref/searching.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/lispref/searching.texi b/lispref/searching.texi
index 4d084166fb8..0f465edc011 100644
--- a/lispref/searching.texi
+++ b/lispref/searching.texi
@@ -699,7 +699,7 @@ simple mirror images. @code{re-search-forward} finds the match whose
beginning is as close as possible to the starting point. If
@code{re-search-backward} were a perfect mirror image, it would find the
match whose end is as close as possible. However, in fact it finds the
-match whose beginning is as close as possible. The reason is that
+match whose beginning is as close as possible. The reason for this is that
matching a regular expression at a given spot always works from
beginning to end, and starts at a specified beginning position.
@@ -988,7 +988,7 @@ Display some help, then ask again.
@section The Match Data
@cindex match data
- Emacs keeps track of the positions of the start and end of segments of
+ Emacs keeps track of the start and end positions of the segments of
text found during a regular expression search. This means, for example,
that you can search for a complex pattern, such as a date in an Rmail
message, and then extract parts of the match under control of the