Doc polish.

README.rst

@@ -80,7 +80,7 @@ Operations such as these are commonly implemented in native VCL with
 an ``if-elsif-elsif`` sequence of string comparisons or regex matches.
 As the number of matches increases, such a sequence becomes cumbersome
 and scales poorly -- the time needed to execute the sequence increases
-with number of matches to be performed.
+with the number of matches to be performed.
 
 With the VMOD, the strings to be matched are declared in a tabular
 form in ``vcl_init``, and the operation is executed in a few
@@ -174,6 +174,12 @@ matched. In both cases, the time for execution is independent of the
 number of strings in the set, and is predictable and fast for large
 sets of strings.
 
+In the case of non-matches, the search for a match stops as soon as it
+encounters a character in the string such that no string in the set
+can match. Thus if a set contains the strings ``foo``, ``bar`` and
+``baz``, then the search stops after the first character if it is
+neither of ``f`` or ``b``.
+
 When new strings are added to a set (with new ``.add()`` statements in
 ``vcl_init``), the VCL code that executes the various operations
 (rewrites, backend assignment and so forth) can remain unchanged. So

src/vmod_selector.vcc

@@ -69,7 +69,7 @@ Operations such as these are commonly implemented in native VCL with
 an ``if-elsif-elsif`` sequence of string comparisons or regex matches.
 As the number of matches increases, such a sequence becomes cumbersome
 and scales poorly -- the time needed to execute the sequence increases
-with number of matches to be performed.
+with the number of matches to be performed.
 
 With the VMOD, the strings to be matched are declared in a tabular
 form in ``vcl_init``, and the operation is executed in a few
@@ -163,6 +163,12 @@ matched. In both cases, the time for execution is independent of the
 number of strings in the set, and is predictable and fast for large
 sets of strings.
 
+In the case of non-matches, the search for a match stops as soon as it
+encounters a character in the string such that no string in the set
+can match. Thus if a set contains the strings ``foo``, ``bar`` and
+``baz``, then the search stops after the first character if it is
+neither of ``f`` or ``b``.
+
 When new strings are added to a set (with new ``.add()`` statements in
 ``vcl_init``), the VCL code that executes the various operations
 (rewrites, backend assignment and so forth) can remain unchanged. So