summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorph10 <ph10@6239d852-aaf2-0410-a92c-79f79f948069>2016-12-31 17:43:42 +0000
committerph10 <ph10@6239d852-aaf2-0410-a92c-79f79f948069>2016-12-31 17:43:42 +0000
commit2910fbebd069787d50a89ab026c49215bb9d1cc8 (patch)
tree29f0cb9d844b1573c9388a1769c4b9573e971582
parent9c63b32be361e637bf9797d66dc5995b5451809c (diff)
downloadpcre2-2910fbebd069787d50a89ab026c49215bb9d1cc8.tar.gz
Fix typos.
git-svn-id: svn://vcs.exim.org/pcre2/code/trunk@641 6239d852-aaf2-0410-a92c-79f79f948069
-rw-r--r--doc/pcre2api.32
-rw-r--r--doc/pcre2stack.32
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/pcre2api.3 b/doc/pcre2api.3
index fc434fd..a24ae95 100644
--- a/doc/pcre2api.3
+++ b/doc/pcre2api.3
@@ -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
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
diff --git a/doc/pcre2stack.3 b/doc/pcre2stack.3
index 4c3d4f0..10c95c2 100644
--- a/doc/pcre2stack.3
+++ b/doc/pcre2stack.3
@@ -107,7 +107,7 @@ in the
\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.