summaryrefslogtreecommitdiff
path: root/doc/pcre2unicode.3
diff options
context:
space:
mode:
Diffstat (limited to 'doc/pcre2unicode.3')
-rw-r--r--doc/pcre2unicode.34
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/pcre2unicode.3 b/doc/pcre2unicode.3
index 0117561..59e226e 100644
--- a/doc/pcre2unicode.3
+++ b/doc/pcre2unicode.3
@@ -118,8 +118,8 @@ UTF-16 and UTF-32 strings can indicate their endianness by special code knows
as a byte-order mark (BOM). The PCRE2 functions do not handle this, expecting
strings to be in host byte order.
.P
-A UTF string is checked before any other processing takes place. In the case of
-\fBpcre2_match()\fP and \fBpcre2_dfa_match()\fP calls with a non-zero starting
+A UTF string is checked before any other processing takes place. In the case of
+\fBpcre2_match()\fP and \fBpcre2_dfa_match()\fP calls with a non-zero starting
offset, the check is applied only to that part of the subject that could be
inspected during matching, and there is a check that the starting offset points
to the first code unit of a character or to the end of the subject. If there