diff --git a/documentation/poky-ref-manual/development.xml b/documentation/poky-ref-manual/development.xml
index 8508a5eb31..4c8c4be077 100644
--- a/documentation/poky-ref-manual/development.xml
+++ b/documentation/poky-ref-manual/development.xml
@@ -15,56 +15,6 @@
         This chapter describes each development method.
     </para>
 
-        <section id="platdev-appdev-external-sdk">
-        <title>External Development Using the Meta-Toolchain</title>
-        <para>
-            The Yocto Project provides toolchains that allow you to develop your application 
-            outside of the Yocto Project build system for specific hardware.
-            These toolchains (called meta-toolchains) contain cross-development tools such as compilers, 
-            linkers, and debuggers that build your application for your target device.
-            The Yocto Project also provides images that have toolchains for supported 
-            architectures included within the image.
-            This allows you to compile, debug, or profile applications directly on the target device.
-            See the 
-            "<link linkend='ref-images'>Reference: Images</link>" appendix for a listing of the image
-            types that Yocto Project supports.
-        </para> 
-        <para>
-            Using the BitBake tool you can build a meta-toolchain or meta-toolchain-sdk target,
-            which generates a tarball. 
-            Unpacking  this tarball into the <filename class="directory">/opt/poky</filename> directory 
-            on your host produces a setup script 
-            (e.g. <filename>/opt/poky/environment-setup-i586-poky-linux</filename>) that 
-            you can <filename>source</filename> to initialize your build environment. 
-            Sourcing this script adds the compiler, QEMU scripts, QEMU binary, a special version of 
-            <filename>pkgconfig</filename> and other 
-            useful utilities to the <filename>PATH</filename> variable used by the Yocto Project
-            build environment. 
-            Variables to assist <filename>pkgconfig</filename> and 
-            Autotools are also defined so that, for example, <filename>configure</filename>
-            can find pre-generated test results for tests that need target hardware on which to run.
-        </para>
-        <para>
-            Using the toolchain with Autotool-enabled packages is straightforward - just pass the 
-            appropriate <filename>host</filename> option to <filename>configure</filename>. 
-            Following is an example:
-            <literallayout class='monospaced'>
-     $ ./configure --host=arm-poky-linux-gnueabi
-            </literallayout>
-            For projects that are not Autotool-enabled, it is usually just a case of ensuring 
-            you point to and use the cross-toolchain.
-            For example, the following two lines of code in a <filename>Makefile</filename>
-            that builds your application
-            specify to use the cross-compiler <filename>arm-poky-linux-gnueabi-gcc</filename>
-            and linker <filename>arm-poky-linux-gnueabi-ld</filename>, which are part of the 
-            meta-toolchain you would have previously established:
-            <literallayout class='monospaced'>
-     CC=arm-poky-linux-gnueabi-gcc;
-     LD=arm-poky-linux-gnueabi-ld;
-            </literallayout>
-        </para>
-        </section>
-
         <section id="using-the-eclipse-and-anjuta-plug-ins">
         <title>External Development Using the Eclipse Plug-in</title>
         <para>