--- a/tests/test-keyword.out	Mon Jul 23 10:36:00 2007 +0200
+++ b/tests/test-keyword.out	Mon Jul 23 21:17:16 2007 +0200
@@ -22,12 +22,13 @@
 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.
+To force expansion after enabling it, or a configuration change, run
+"hg kwexpand".
 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.
 Caveat: "hg import" fails if the patch context contains an active
-        keyword. In that case run "hg kwshrink", reimport, and then
-        "hg kwexpand".
+        keyword. In that case run "hg kwshrink", and then reimport.
         Or, better, use bundle/unbundle to share changes.
  kwdemo     print [keywordmaps] configuration and an expansion example
  kwexpand   expand keywords in working directory