summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2011-09-12 15:59:57 +0000
committerph10 <ph10@2f5784b3-3f2a-0410-8824-cb99058d5e15>2011-09-12 15:59:57 +0000
commit59a5ee2055c2150abf29f80b7d0e64de6ba7a1d3 (patch)
tree10cf4e82ac5b1b34590f1ca0ee118b3df2452cbe
parent09f7fbdfcb63f22192a191ed818c1d05a22cb983 (diff)
downloadpcre-59a5ee2055c2150abf29f80b7d0e64de6ba7a1d3.tar.gz
Fix typo.
git-svn-id: svn://vcs.exim.org/pcre/code/trunk@693 2f5784b3-3f2a-0410-8824-cb99058d5e15
-rw-r--r--doc/pcrejit.32
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/pcrejit.3 b/doc/pcrejit.3
index 2500057..30d99c9 100644
--- a/doc/pcrejit.3
+++ b/doc/pcrejit.3
@@ -75,7 +75,7 @@ interpretive code.
If the JIT compiler finds an unsupported item, no JIT data is generated. You
can find out if JIT execution is available after studying a pattern by calling
\fBpcre_fullinfo()\fP with the PCRE_INFO_JIT option. A result of 1 means that
-JIT compilationw was successful. A result of 0 means that JIT support is not
+JIT compilation was successful. A result of 0 means that JIT support is not
available, or the pattern was not studied with PCRE_STUDY_JIT_COMPILE, or the
JIT compiler was not able to handle the pattern.
.