aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDmitry Mikhirev2014-11-18 21:49:13 +0300
committerDmitry Mikhirev2014-11-18 21:49:13 +0300
commit22005d1fb873470df37c031f5db33fd0b3301a43 (patch)
tree5ba14d8b0b41374dd44bd7aa84858e096a0340cc
parent7f81a08e36b1dd8a996c1bc3b8cf6d331e3489f3 (diff)
downloadmake_pcre-22005d1fb873470df37c031f5db33fd0b3301a43.tar.gz
make_pcre-22005d1fb873470df37c031f5db33fd0b3301a43.tar.bz2
make_pcre-22005d1fb873470df37c031f5db33fd0b3301a43.tar.xz
make_pcre-22005d1fb873470df37c031f5db33fd0b3301a43.zip
mistyping
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index e420630..8d1abf8 100644
--- a/README.md
+++ b/README.md
@@ -64,7 +64,7 @@ because it will reset them.
`pcre_find` also provides ability to set named variables to matched substrings.
It can be useful if you want to preserve captured value after another matching
-function called or if your pattern is quiet complicated, and it is difficult
+function called or if your pattern is quite complicated, and it is difficult
to handle substring numbers.
In PCRE, a subpattern can be named in one of three ways: `(?<name>...)`