1 files changed, 56 insertions, 31 deletions

diff --git a/documentation/kernel-dev/kernel-dev-intro.xml b/documentation/kernel-dev/kernel-dev-intro.xml
index 67d8d93f08..32a4040e4b 100644
--- a/documentation/kernel-dev/kernel-dev-intro.xml
+++ b/documentation/kernel-dev/kernel-dev-intro.xml
@@ -3,44 +3,69 @@
 [<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
 
 <chapter id='kernel-dev-intro'>
-
 <title>Introduction</title>
 
-    <para>
-        Regardless of how you intend to make use of the Yocto Project,
-        chances are you are going to need to work with the Linux kernel.
-        The Yocto Project provides a powerful set of tools for managing
-        Linux kernel sources and configuration data.
-        You can use this tooling to help you make a single configuration change,
-        apply a couple of patches, or work with your own sources.
-    </para>
-
-    <para>
-        The Yocto Project Kernel Development Manual describes common tasks
-        you can perform using the kernel tooling as well as provides information
-        about the metadata needed to work with the kernel inside the
-        Yocto Project.
-    </para>
-
-    <section id='kernel-dev-background'>
-        <title>Background</title>
+    <section id='kernel-dev-overview'>
+        <title>Overview</title>
 
         <para>
-            Each Yocto Project release introduces a new set of linux-yocto
-            kernel recipes that tracks the latest upstream developments and
-            introduces newly supported platforms.
-            In addition to the new kernel recipes, the previous recipes are
-            refreshed and supported for at least one additional release.
+            Regardless of how you intend to make use of the Yocto Project,
+            chances are you will work with the Linux kernel.
+            This manual provides background information on the Yocto Linux kernel
+            <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>,
+            describes common tasks you can perform using the kernel tools,
+            and shows you how to use the Metadata needed to work with
+            the kernel inside the Yocto Project.
+       </para>
+
+       <para>
+            Each Yocto Project release has a set of linux-yocto recipes, whose
+            Git repositories you can view in the Yocto
+            <ulink url='&YOCTO_GIT_URL;'>Source Repositories</ulink> under
+            the "Yocto Linux Kernel" heading.
+            New recipes for the release track the latest upstream developments
+            and introduce newly supported platforms.
+            Previous recipes in the release are refreshed and supported for at
+            least one additional release.
             As they align, these previous releases are updated to include the
             latest from the Long Term Support Initiative (LTSI) project.
-            Besides these recipes, a <filename>linux-yocto-dev.bb</filename>
-            recipe is available for working with the very latest in upstream
-            Linux kernel development as well as metadata development.
+            Also included is a linux-yocto development recipe
+            (<filename>linux-yocto-dev.bb</filename>) should you want to work
+            with the very latest in upstream Linux kernel development and
+            Metadata development.
+        </para>
+
+        <para>
+            The Yocto Project also provides a powerful set of kernel
+            tools for managing Linux kernel sources and configuration data.
+            You can use these tools to make a single configuration change,
+            apply multiple patches, or work with your own kernel sources.
+        </para>
+
+        <para>
+            In particular, the kernel tools allow you to generate configuration
+            fragments that specify only what you must, and nothing more.
+            Configuration fragments only need to contain the highest level
+            visible <filename>CONFIG</filename> options as presented by the Linux
+            kernel <filename>menuconfig</filename> system.
+            Contrast this against a complete Linux kernel
+            <filename>.config</filename>, which includes all the automatically
+            selected <filename>CONFIG</filename> options.
+            This efficiency reduces your maintenance effort and allows you
+            to further separate your configuration in ways that make sense for
+            your project.
+            A common split separates policy and hardware.
+            For example, all your kernels might support
+            the <filename>proc</filename> and <filename>sys</filename> filesystems,
+            but only specific boards require sound, USB, or specific drivers.
+            Specifying these configurations individually allows you to aggregate
+            them together as needed, but maintains them in only one place.
+            Similar logic applies to separating source changes.
         </para>
 
         <para>
             If you do not maintain your own kernel sources and need to make
-            only minimal changes to the sources, these recipes provide a
+            only minimal changes to the sources, the released recipes provide a
             vetted base upon which to layer your changes.
             Doing so allows you to benefit from the continual kernel
             integration and testing performed during development of the
@@ -50,8 +75,8 @@
         <para>
             If, instead, you have a very specific Linux kernel source tree
             and are unable to align with one of the many official linux-yocto
-            releases, an alternative exists by which you can use the Yocto
-            Project Linux kernel tools with your own sources.
+            recipes, an alternative exists by which you can use the Yocto
+            Project Linux kernel tools with your own kernel sources.
         </para>
     </section>
 
@@ -61,7 +86,7 @@
         <para>
             The sections that follow provide instructions for completing
             specific Linux kernel development tasks.
-            These instructions assume you are familiar with working with
+            These instructions assume you are comfortable working with
             <ulink url='http://developer.berlios.de/projects/bitbake/'>BitBake</ulink>
             recipes and basic open-source development tools.
             Understanding these concepts will facilitate the process of working