--- a/tests/test-keyword.out	Tue Jun 09 22:32:14 2009 +0200
+++ b/tests/test-keyword.out	Tue Jun 09 22:42:23 2009 +0200
@@ -1,32 +1,34 @@
 % help
 keyword extension - keyword expansion in local repositories
-This extension expands RCS/CVS-like or self-customized $Keywords$
-in tracked text files selected by your configuration.
-Keywords are only expanded in local repositories and not stored in
-the change history. The mechanism can be regarded as a convenience
-for the current user or for archive distribution.
-Configuration is done in the [keyword] and [keywordmaps] sections
-of hgrc files.
+This extension expands RCS/CVS-like or self-customized $Keywords$ in
+tracked text files selected by your configuration.
+Keywords are only expanded in local repositories and not stored in the
+change history. The mechanism can be regarded as a convenience for the
+current user or for archive distribution.
+Configuration is done in the [keyword] and [keywordmaps] sections of
+hgrc files.
 Example:
     [keyword]
     # expand keywords in every python file except those matching "x*"
     **.py =
     x*    = ignore
 Note: the more specific you are in your filename patterns
-      the less you lose speed in huge repos.
+      the less you lose speed in huge repositories.
 For [keywordmaps] template mapping and expansion demonstration and
 control run "hg kwdemo".
 An additional date template filter {date|utcdate} is provided.
-The default template mappings (view with "hg kwdemo -d") can be replaced
-with customized keywords and templates.
-Again, run "hg kwdemo" to control the results of your config changes.
+The default template mappings (view with "hg kwdemo -d") can be
+replaced with customized keywords and templates. Again, run "hg
+kwdemo" to control the results of your config changes.
 Before changing/disabling active keywords, run "hg kwshrink" to avoid
-the risk of inadvertedly storing expanded keywords in the change history.
+the risk of inadvertently storing expanded keywords in the change
+history.
 To force expansion after enabling it, or a configuration change, run
 "hg kwexpand".
-Also, when committing with the record extension or using mq's qrecord, be aware
-that keywords cannot be updated. Again, run "hg kwexpand" on the files in
-question to update keyword expansions after all changes have been checked in.
+Also, when committing with the record extension or using mq's qrecord,
+be aware that keywords cannot be updated. Again, run "hg kwexpand" on
+the files in question to update keyword expansions after all changes
+have been checked in.
 Expansions spanning more than one line and incremental expansions,
 like CVS' $Log$, are not supported. A keyword template map
 "Log = {desc}" expands to the first line of the changeset description.