diff --git a/committing.rst b/committing.rst
--- a/committing.rst
+++ b/committing.rst
@@ -276,6 +276,8 @@
 
 See :ref:`checkout` to find information about cloning and switching branches.
 
+.. _multiple-clones:
+
 Multiple Clones Approach
 ''''''''''''''''''''''''
 
diff --git a/faq.rst b/faq.rst
--- a/faq.rst
+++ b/faq.rst
@@ -335,7 +335,13 @@
 I want to keep a separate working copy per development branch, is it possible?
 ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
 
-Just clone your local repository and update each clone to a different branch::
+There are two ways:
+
+1) Use the "`share extension`_" as described in the :ref:`multiple-clones`
+   section;
+2) Create several clones of your local repository;
+
+If you want to use the second way, you can do::
 
    $ hg clone cpython py33
    updating to branch default
@@ -347,6 +353,8 @@
 The current branch in a working copy is "sticky": if you pull in some new
 changes, ``hg update`` will update to the head of the *current branch*.
 
+.. _share extension: http://mercurial.selenic.com/wiki/ShareExtension
+
 
 .. _hg-paths:
 
@@ -726,17 +734,6 @@
 These FAQs are intended mainly for core developers.
 
 
-How do I avoid repeated pulls and pushes between my local repositories?
-'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
-
-The "`share extension`_" allows you to share a single local repository
-between several working copies: each commit you make in a working copy will
-be immediately available in other working copies, even though they might
-be checked out on different branches.
-
-.. _share extension: http://mercurial.selenic.com/wiki/ShareExtension
-
-
 .. _hg-commit:
 
 How do I commit a change to a file?