1 files changed, 20 insertions, 1 deletions

diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index fbe43213e2..6c55a572b0 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -258,13 +258,32 @@ apply the new configuration before rebuilding the Linux kernel.
         <title>Iterative Development</title>
 
         <para>
-        If you do not have existing patches or configuration files, you can easily
+            If you do not have existing patches or configuration files,
+            you can iteratively generate them from within the BitBake build
+            environment as described within this section.
+            During an iterative workflow, running a previously completed BitBake
+            task causes BitBake to invalidate the tasks that follow that
+            task in the build sequence.
+            This invalidation causes the tasks to rebuild the next
+            time you invoke the build.
+        </para>
+
+        <para>
+            As you read this section, be sure to substitute "linux-yocto" with
+            the name of the Linux kernel recipe with which you are working.
+        </para>
+
+        <para>
+            Original Text:
+            <literallayout class='monospaced'>
+If you do not have existing patches or configuration files, you can easily
 generate them from within the bitbake build environment, as will be described
 below. As you do, running previously completed bitbake tasks will cause bitbake
 to invalidate the tasks that follow them in the build sequence, causing them to
 rebuild at the next invocation of the build. Throughout this section, be sure to
 substitute "linux-yocto" with the name of the Linux kernel recipe you are
 working with.
+             </literallayout>
         </para>
 
         <section id='generating-configuration-files'>