diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml
index 69b679bbf7..af8797bbf5 100644
--- a/documentation/ref-manual/faq.xml
+++ b/documentation/ref-manual/faq.xml
@@ -31,31 +31,19 @@
     <qandaentry>
         <question>
             <para>
-                I only have Python 2.4 or 2.5 but BitBake requires Python 2.6 or 2.7.
+                My development system does not have Python 2.7.3 or greater,
+                which the Yocto Project requires.
                 Can I still use the Yocto Project?
             </para>
         </question>
         <answer>
             <para>
-                You can use a stand-alone tarball to provide Python 2.6.
-                You can find pre-built 32 and 64-bit versions of Python 2.6 at the following locations:
-                <itemizedlist>
-                    <listitem><para><ulink url='&YOCTO_PYTHON-i686_DL_URL;'>32-bit tarball</ulink></para></listitem>
-                    <listitem><para><ulink url='&YOCTO_PYTHON-x86_64_DL_URL;'>64-bit tarball</ulink></para></listitem>
-                </itemizedlist>
-            </para>
-            <para>
-                These tarballs are self-contained with all required libraries and should work
-                on most Linux systems.
-                To use the tarballs extract them into the root
-                directory and run the appropriate command:
-                <literallayout class='monospaced'>
-     $ export PATH=/opt/poky/sysroots/i586-pokysdk-linux/usr/bin/:$PATH
-     $ export PATH=/opt/poky/sysroots/x86_64-pokysdk-linux/usr/bin/:$PATH
-                </literallayout>
-            </para>
-            <para>
-                Once you run the command, BitBake uses Python 2.6.
+                You can get the required tools on your host development
+                system a couple different ways (i.e. building a tarball or
+                downloading a tarball).
+                See the
+                "<link linkend='required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</link>"
+                section for steps on how to update your build tools.
             </para>
         </answer>
     </qandaentry>
@@ -682,7 +670,7 @@
             <para>
                 Yes - you can easily do this.
                 When you use BitBake to build an image, all the build output
-                goes into the directory created when you run the 
+                goes into the directory created when you run the
                 build environment setup script (i.e.
                 <link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link>
                 or