diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 57079fa0c5..fbd12946e1 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -119,6 +119,63 @@
     </para>
 </section>
 
+<section id='yocto-project-terms'>
+    <title>Yocto Project Terms</title>
+
+    <para>
+        Following is a list of terms and definitions users new to the Yocto Project development 
+        environment might find helpful.
+        Some terms are universal but are included here just in case:
+    <itemizedlist>
+        <listitem><para><emphasis>Image</emphasis> - An image is a collection of recipes created with 
+            Bitbake (baked).  
+            Images run on specific hardware and use cases.</para></listitem>
+        <listitem><para><emphasis>Recipe</emphasis> - A set of instructions for building packages.  
+            A recipe describes where you get source code and which patches to apply.
+            Recipes describe dependencies for libraries or for other recipes and they 
+            also contain configuration and compilation options.  
+            Recipes also let you ‘install’ customizations.  
+            Recipes contain the logical unit of execution, the software/images to build and 
+            use the <filename>.bb</filename> file extension.</para></listitem>
+        <listitem><para><emphasis>BitBake</emphasis> - The task executor and scheduler used by Yocto Project
+            to build images. 
+            For more information on BitBake, see the <ulink url='http://bitbake.berlios.de/manual/'>
+            BitBake documentation</ulink>.</para></listitem>
+        <listitem><para><emphasis>Package</emphasis> - A collection of ‘baked’ recipes.  
+            You ‘bake’ something by running it through Bitbake.</para></listitem>
+        <listitem><para><emphasis>Layer</emphasis> - A logical collection of recipes representing the core, 
+            a BSP, or an application stack.</para></listitem>
+        <listitem><para><emphasis>Metadata</emphasis> - Information for a build that is generally 
+            architecture-independent.  
+            This information includes Task definitions in recipes, classes, and configuration 
+            information.</para></listitem>
+        <listitem><para><emphasis>Configuration File</emphasis>:  Configuration information in the 
+            <filename>.conf</filename> files provides global definitions of variables.  
+            The <filename>build/conf/local.conf</filename> configuration file defines local user-defined variables.  
+            The <filename>distro/poky.conf</filename> configuration file defines Yocto ‘distro’ configuration 
+            variables.  
+            The <filename>machine/beagleboard.conf</filename> configuration file defines machine-specific variables
+            (i.e. Texas Instruments ARM Cortex-A8 development board in this example.  
+            Configuration files end with a <filename>.conf</filename> filename extension.</para></listitem>
+        <listitem><para><emphasis>Classes</emphasis> - Files that encapsulate and inherit logic.  
+            Class files end with the <filename>.bbclass</filename> filename extension.</para></listitem>
+        <listitem><para><emphasis>Append Files</emphasis> - Files that append build information to 
+            a recipe file.  
+            Information in append files override the information in the similarly-named recipe file.
+            Append files use the <filename>.bbappend</filename> filename suffix.</para></listitem>
+        <listitem><para><emphasis>Tasks</emphasis> - Arbitrary groups of software used to contain Recipes.  
+            You simply use Tasks to hold recipes that when build usually accomplished a single task.  
+            For example, a task could contain the recipes for a company’s proprietary or value-add software.  
+            Or the task could contain the recipes that enable graphics. 
+            A task is really just another recipe.  
+            Because task files are recipes, they end with the <filename>.bb</filename> filename 
+            extension.</para></listitem>
+        <listitem><para><emphasis>Common OE-Core</emphasis> - A core set of metadata originating 
+            with OpenEmbedded (OE) that is shared between OE and the Yocto Project.</para></listitem>
+    </itemizedlist>
+    </para>
+</section>
+
 <section id='licensing'>
     <title>Licensing</title>
 
@@ -286,52 +343,6 @@
         Again, if you are familiar with this type of development environment you might want to just skip the section. 
     </para>
 
-    <para>
-        Following are the definitions for some terms used in the Yocto Project.
-        [WRITER NOTE: I need to move this list of definitions somewhere useful.]
-    <itemizedlist>
-        <listitem><para><emphasis>Image</emphasis> - An image is a collection of recipes created with 
-            Bitbake (baked).  Images run on specific hardware and use cases.</para></listitem>
-        <listitem><para><emphasis>Recipe</emphasis> - A set of instructions for building packages.  
-            A recipe describes where you get the source and which patches to apply.
-            Recipes describe dependencies for libraries or for other recipes and they 
-            also contain configuration and compilation options.  
-            Recipes also let you ‘install’ customizations.  
-            Recipes contain the logical unit of execution, the software/images to build and 
-            use the <filename>.bb</filename> file extension.</para></listitem>
-        <listitem><para><emphasis>BitBake</emphasis> - The task executor and scheduler used by Yocto Project
-            to build images. 
-            For more information on BitBake, see the <ulink url='http://bitbake.berlios.de/manual/'>
-            BitBake documentation</ulink>.</para></listitem>
-        <listitem><para><emphasis>Package</emphasis> - A collection of ‘baked’ recipes.  
-            You ‘bake’ something by running it through Bitbake.</para></listitem>
-        <listitem><para><emphasis>Layer</emphasis> - A logical collection of recipes representing the core, 
-            a BSP, or an application stack.</para></listitem>
-        <listitem><para><emphasis>Metadata</emphasis> - Information for a build that is generally 
-            architecture-independent.  
-            This information includes Task definitions in recipes, classes, and configuration 
-            information.</para></listitem>
-        <listitem><para><emphasis>Configuration File</emphasis>:  Configuration information in the 
-            <filename>.conf</filename> files provides global definition of variables.  
-            The <filename>build/conf/local.conf</filename> configuration file defines local user-defined variables.  
-            The <filename>distro/poky.conf</filename> configuration file defines Yocto ‘distro’ configuration 
-            variables.  
-            The <filename>machine/beagleboard.conf</filename> configuration file defines machine-specific variables.  
-            Configuration files end with a <filename>.conf</filename> filename extension.</para></listitem>
-        <listitem><para><emphasis>Classes</emphasis> - Files that encapsulate and inherit logic.  
-            Class files end with the <filename>.bbclass</filename> filename extension.</para></listitem>
-        <listitem><para><emphasis>Tasks</emphasis> - Arbitrary groups of software used to contain Recipes.  
-            You simply use Tasks to hold recipes that when build usually accomplished a single task.  
-            For example, a task could contain the recipes for a company’s proprietary or value-add software.  
-            Or the task could contain the recipes that enable graphics. 
-            A task is really just another recipe.  
-            Because task files are recipes, they end with the <filename>.bb</filename> filename 
-            extension.</para></listitem>
-        <listitem><para><emphasis>Common OE-Core</emphasis> - A core set of metadata originating 
-            with OpenEmbedded (OE) that is shared between OE and the Yocto Project.</para></listitem>
-    </itemizedlist>
-    </para>
-
     <para>
         A master Git repository exists that contains the project.  
         Usually a key individual is responsible for this repository.