Revision: 641
http://www.exim.org/viewvc/pcre2?view=rev&revision=641
Author: ph10
Date: 2016-12-31 17:43:42 +0000 (Sat, 31 Dec 2016)
Log Message:
-----------
Fix typos.
Modified Paths:
--------------
code/trunk/doc/pcre2api.3
code/trunk/doc/pcre2stack.3
Modified: code/trunk/doc/pcre2api.3
===================================================================
--- code/trunk/doc/pcre2api.3 2016-12-31 17:40:45 UTC (rev 640)
+++ code/trunk/doc/pcre2api.3 2016-12-31 17:43:42 UTC (rev 641)
@@ -1993,7 +1993,7 @@
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
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
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
Modified: code/trunk/doc/pcre2stack.3
===================================================================
--- code/trunk/doc/pcre2stack.3 2016-12-31 17:40:45 UTC (rev 640)
+++ code/trunk/doc/pcre2stack.3 2016-12-31 17:43:42 UTC (rev 641)
@@ -107,7 +107,7 @@
\fBpcre2api\fP
.\"
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
if possible while \fBpcre2_match()\fP is running. They are all freed just
before it exits.
