--- a/mercurial/help/extensions.txt	Thu Jun 06 13:37:41 2013 -0400
+++ b/mercurial/help/extensions.txt	Thu Jun 06 14:05:03 2013 -0400
@@ -3,14 +3,6 @@
 existing commands, change the default behavior of commands, or
 implement hooks.
 
-Extensions are not loaded by default for a variety of reasons:
-they can increase startup overhead; they may be meant for advanced
-usage only; they may provide potentially dangerous abilities (such
-as letting you destroy or modify history); they might not be ready
-for prime time; or they may alter some usual behaviors of stock
-Mercurial. It is thus up to the user to activate extensions as
-needed.
-
 To enable the "foo" extension, either shipped with Mercurial or in the
 Python search path, create an entry for it in your configuration file,
 like this::
@@ -23,6 +15,16 @@
   [extensions]
   myfeature = ~/.hgext/myfeature.py
 
+See :hg:`help config` for more information on configuration files.
+
+Extensions are not loaded by default for a variety of reasons:
+they can increase startup overhead; they may be meant for advanced
+usage only; they may provide potentially dangerous abilities (such
+as letting you destroy or modify history); they might not be ready
+for prime time; or they may alter some usual behaviors of stock
+Mercurial. It is thus up to the user to activate extensions as
+needed.
+
 To explicitly disable an extension enabled in a configuration file of
 broader scope, prepend its path with !::