summaryrefslogtreecommitdiff
path: root/doc/pcre2pattern.3
diff options
context:
space:
mode:
Diffstat (limited to 'doc/pcre2pattern.3')
-rw-r--r--doc/pcre2pattern.36
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/pcre2pattern.3 b/doc/pcre2pattern.3
index c2d12d3..c88ce03 100644
--- a/doc/pcre2pattern.3
+++ b/doc/pcre2pattern.3
@@ -75,7 +75,7 @@ Another special sequence that may appear at the start of a pattern is (*UCP).
This has the same effect as setting the PCRE2_UCP option: it causes sequences
such as \ed and \ew to use Unicode properties to determine character types,
instead of recognizing only characters with codes less than 256 via a lookup
-table. If also causes upper/lower casing operations to use Unicode properties
+table. If also causes upper/lower casing operations to use Unicode properties
for characters with code points greater than 127, even when UTF is not set.
.P
Some applications that allow their users to supply patterns may wish to
@@ -2676,8 +2676,8 @@ pattern. If this is not the case, the rest of the pattern match fails exactly
as before because nothing has changed, so using a non-atomic assertion just
wastes resources.
.P
-There is one exception to backtracking into a non-atomic assertion. If an
-(*ACCEPT) control verb is triggered, the assertion succeeds atomically. That
+There is one exception to backtracking into a non-atomic assertion. If an
+(*ACCEPT) control verb is triggered, the assertion succeeds atomically. That
is, a subsequent match failure cannot backtrack into the assertion.
.P
Non-atomic assertions are not supported by the alternative matching function