ongrep

commit 26126fb0832b74b70517f0a7a07ef50d33d17b67
parent e590bddbfd3654a09ee327c8701eb331ca660ff0
Author: Jordan Ritter <jpr5@darkridge.com>
Date:   Tue, 22 Feb 2005 06:28:14 +0000

grammatical changes

Diffstat:
M
doc/REGEX.txt
 | 
6
+++---

1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/REGEX.txt b/doc/REGEX.txt
@@ -21,7 +21,7 @@ A note about PCRE vs. GNU regex:
       well-formulated regex certainly performs more efficiently than a
       simple substring match.  However, this test is reasonably
       indicative of how most people use ngrep, so the test results are
-      still important.
+      still useful.
 
       Granted, on the single-match level the time difference is
       absolutely unnoticeable (it took 100 million loop iterations to
@@ -29,8 +29,8 @@ A note about PCRE vs. GNU regex:
       you.  Likewise, the stripped binary sizes are also within 10k of
       each other on the test compile box.
 
-      If licensing terms are more sensitive for you than speed, then
-      compile against PCRE which is available under the Artistic
+      If licensing terms are more sensitive for you than speed then
+      compile against PCRE, which is available under the Artistic
       License (Free as in Beer).  Otherwise, in all other cases the
       GNU regex library is the best candidate, and the speed can
       really help when piping those 500MB pcap dump files through