Fix unclear wording pointed out by Tim Peters, about the interaction between

    ^ and the pos argument to re.match().
Also, fixed a typo in libregex.tex.

diff --git a/Doc/lib/libre.tex b/Doc/lib/libre.tex
index a47723f81b0cab150fe5820460c6240d5b807838..a1bcf06c9f8548b35243a0d700d5d95561c3be5d 100644 (file)
--- a/Doc/lib/libre.tex
+++ b/Doc/lib/libre.tex
@@ -476,9 +476,11 @@ attributes:
   match.
   
   The optional second parameter \var{pos} gives an index in the string
-  where the search is to start; it defaults to \code{0}.  The
-  \character{\^} pattern character will not match at the index where the
-  search is to start.
+  where the search is to start; it defaults to \code{0}.  This is not
+  completely equivalent to slicing the string; the \code{'\^'} pattern
+  character matches at the real beginning of the string and at positions
+  just after a newline, but not necessarily at the index where the search
+  is to start.
 
   The optional parameter \var{endpos} limits how far the string will
   be searched; it will be as if the string is \var{endpos} characters

diff --git a/Doc/lib/libregex.tex b/Doc/lib/libregex.tex
index fabc182c882048b680f96df202907fcf40fe19cf..e3adf55701a53c9d3f248aff58ed17500a7e2054 100644 (file)
--- a/Doc/lib/libregex.tex
+++ b/Doc/lib/libregex.tex
@@ -288,7 +288,7 @@ Compiled regular expression objects support these methods:
   The optional second parameter, \var{pos}, gives an index in the string
   where the search is to start; it defaults to \code{0}.  This is not
   completely equivalent to slicing the string; the \code{'\^'} pattern
-  character matches at the real begin of the string and at positions
+  character matches at the real beginning of the string and at positions
   just after a newline, not necessarily at the index where the search
   is to start.
 \end{funcdesc}