summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2010-01-20 07:36:43 -0800
committerKaz Kylheku <kaz@kylheku.com>2010-01-20 07:36:43 -0800
commit35e9e76cd262cd67719019199cc7dd84ffc43aac (patch)
tree23e5f06fb810555c93f22c9c1bd6adf0d7f162ca
parent18c10df68095f97b1c2168b2a0dad7fdeb8729c0 (diff)
downloadtxr-35e9e76cd262cd67719019199cc7dd84ffc43aac.tar.gz
txr-35e9e76cd262cd67719019199cc7dd84ffc43aac.tar.bz2
txr-35e9e76cd262cd67719019199cc7dd84ffc43aac.zip
Missing word.
-rw-r--r--txr.16
1 files changed, 3 insertions, 3 deletions
diff --git a/txr.1 b/txr.1
index 92daab58..fb0af09b 100644
--- a/txr.1
+++ b/txr.1
@@ -751,9 +751,9 @@ In
.B txr,
regular expression matches do not span multiple lines. The regex language has
no feature for multi-line matching. However, the @(freeform) directive
-allows the remaining portion of the input to be treated as one big
-sequence of, in which line terminators appear as explicit
-characters. Regular expressions may freely match through this sequence.
+allows the remaining portion of the input to be treated as one string
+in which line terminators appear as explicit characters. Regular expressions
+may freely match through this sequence.
It's possible for a regular expression to match an empty string.
For instance, if the next input character is z, facing a