summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2016-05-20 01:00:22 -0700
committerKaz Kylheku <kaz@kylheku.com>2016-05-20 01:00:22 -0700
commit672f67915f5e905af2985c15b16934e9c174fd45 (patch)
treed3f5f08d4e6e57cfd1c417b6369dd5b9df6797cb
parente286db242a753857bdba3088825e953768d4731e (diff)
downloadtxr-672f67915f5e905af2985c15b16934e9c174fd45.tar.gz
txr-672f67915f5e905af2985c15b16934e9c174fd45.tar.bz2
txr-672f67915f5e905af2985c15b16934e9c174fd45.zip
No such word: expressivity.
* txr.1: Replace Expressivity with Expressiveness.
-rw-r--r--txr.12
1 files changed, 1 insertions, 1 deletions
diff --git a/txr.1 b/txr.1
index e610852b..eefe331e 100644
--- a/txr.1
+++ b/txr.1
@@ -43151,7 +43151,7 @@ than a positive match for the exact set we want), then we can
intersect this over-generalized set with the complemented set of
another regular expression which matches the particulars that we wish excluded.
-.TP* "Expressivity versus Power"
+.TP* "Expressiveness versus Power"
It turns out that regular expressions which do not make use of the
complement or intersection operators are just as powerful as expressions