# HG changeset patch
# User Christian Ebert <blacktrash@gmx.net>
# Date 1357835106 0
# Node ID 5eb5ba3b9e99170ae48feb06f6a5681c4bd79e3f
# Parent  0cdba0354b87f747b0ca5c89fbb2fc333dc6d3c6
test: improve grammar and spelling in branchcache note

See: 769eb1b179b5

diff -r 0cdba0354b87 -r 5eb5ba3b9e99 tests/test-keyword.t
--- a/tests/test-keyword.t	Thu Jan 10 16:02:08 2013 +0000
+++ b/tests/test-keyword.t	Thu Jan 10 16:25:06 2013 +0000
@@ -750,13 +750,13 @@
 |Note:
 |
 | After the last rollback, the "unserved" branchheads cache became invalid, but
-| all changeset in the repo were public. So filtering wise:
+| all changesets in the repo were public. For filtering this means:
 |   "mutable" == "unserved" == ø.
 |
-| As the "unserved" cache is invalid, we fall back to "mutable" cache. But not
-| update is needed between "mutable" and "unserved" cache and the "unserved"
-| cache is not updated on disk. The on disk version therefor stay invalid for
-| some time. This explains why the "unserved" branchheads cache is detect
+| As the "unserved" cache is invalid, we fall back to the "mutable" cache. But
+| no update is needed between "mutable" and "unserved" and the "unserved" cache
+| is not updated on disk. The on-disk version therefore stays invalid for some
+| time. This explains why the "unserved" branchheads cache is detected as
 | invalid here.
 
   $ hg --debug commit -l log -d '2 0' -u 'User Name <user@example.com>'