diff --git a/documentation/kernel-dev/kernel-dev-maint-appx.xml b/documentation/kernel-dev/kernel-dev-maint-appx.xml
index 79e6e26e00..f5fd183fd0 100644
--- a/documentation/kernel-dev/kernel-dev-maint-appx.xml
+++ b/documentation/kernel-dev/kernel-dev-maint-appx.xml
@@ -154,8 +154,8 @@
- Compile Feature:
- Once located, the feature description is either compiled
+ Expand Feature:
+ Once located, the feature description is either expanded
into a simple script of actions, or into an existing
equivalent script that is already part of the shipped
kernel.
@@ -169,8 +169,8 @@
variable in recipes.
- Locate, Compile, and Append Each Feature:
- Each extra feature is located, compiled and appended to
+ Locate, Expand, and Append Each Feature:
+ Each extra feature is located, expanded and appended to
the script as described in step three.
@@ -203,23 +203,46 @@
The kernel tree and cache are ready for developer consumption to
be locally cloned, configured, and built into a Yocto Project
kernel specific to some target hardware.
-
- The generated yocto-kernel-cache
- repository adds to the kernel as shipped with the Yocto Project
- release.
- Any add-ons and configuration data are applied to the end of
- an existing branch.
- The full repository generation that is found in the
- official Yocto Project kernel repositories at
- http://git.yoctoproject.org/cgit.cgi
- is the combination of all supported boards and configurations.
-
-
- The technique the Yocto Project team uses is flexible
- and allows for seamless blending of an immutable history with
- additional patches specific to a deployment.
- Any additions to the kernel become an integrated part of the
- branches.
+ Notes
+
+
+ The generated yocto-kernel-cache
+ repository adds to the kernel as shipped with the Yocto
+ Project release.
+ Any add-ons and configuration data are applied to the
+ end of an existing branch.
+ The full repository generation that is found in the
+ official Yocto Project kernel repositories at
+ http://git.yoctoproject.org/cgit.cgi
+ is the combination of all supported boards and
+ configurations.
+
+
+ The technique the Yocto Project team uses is flexible
+ and allows for seamless blending of an immutable
+ history with additional patches specific to a
+ deployment.
+ Any additions to the kernel become an integrated part
+ of the branches.
+
+
+ The full kernel tree that you see on
+ is
+ generated through repeating the above steps for all
+ valid BSPs.
+ The end result is a branched, clean history tree that
+ makes up the kernel for a given release.
+ You can see the script (kgit-scc)
+ responsible for this in the
+ yocto-kernel-tools
+ repository.
+
+
+ The steps used to construct the full kernel tree are
+ the same steps that BitBake uses when it builds a
+ kernel image.
+
+