Fix typos.
This commit is contained in:
parent
396a7c7d29
commit
9fca0deabf
|
@ -1993,7 +1993,7 @@ Information about a successful or unsuccessful match is placed in a match
|
||||||
data block, which is an opaque structure that is accessed by function calls. In
|
data block, which is an opaque structure that is accessed by function calls. In
|
||||||
particular, the match data block contains a vector of offsets into the subject
|
particular, the match data block contains a vector of offsets into the subject
|
||||||
string that define the matched part of the subject and any substrings that were
|
string that define the matched part of the subject and any substrings that were
|
||||||
captured. This is know as the \fIovector\fP.
|
captured. This is known as the \fIovector\fP.
|
||||||
.P
|
.P
|
||||||
Before calling \fBpcre2_match()\fP, \fBpcre2_dfa_match()\fP, or
|
Before calling \fBpcre2_match()\fP, \fBpcre2_dfa_match()\fP, or
|
||||||
\fBpcre2_jit_match()\fP you must create a match data block by calling one of
|
\fBpcre2_jit_match()\fP you must create a match data block by calling one of
|
||||||
|
|
|
@ -107,7 +107,7 @@ in the
|
||||||
\fBpcre2api\fP
|
\fBpcre2api\fP
|
||||||
.\"
|
.\"
|
||||||
documentation. Since the block sizes are always the same, it may be possible to
|
documentation. Since the block sizes are always the same, it may be possible to
|
||||||
implement customized a memory handler that is more efficient than the standard
|
implement a customized memory handler that is more efficient than the standard
|
||||||
function. The memory blocks obtained for this purpose are retained and re-used
|
function. The memory blocks obtained for this purpose are retained and re-used
|
||||||
if possible while \fBpcre2_match()\fP is running. They are all freed just
|
if possible while \fBpcre2_match()\fP is running. They are all freed just
|
||||||
before it exits.
|
before it exits.
|
||||||
|
|
Loading…
Reference in New Issue