From dc124306b5ac150b1d63febcedaf316137309aa7 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Thu, 20 Jan 2011 10:06:10 -0800
Subject: [PATCH] documentation/yocto-project-qs/yocto-project-qs.xml:  Added
 sub-sections to pre-built image section

The pre-built image section was one long section that naturally
broke into several areas.  I inserted some sub-sections for better
organization.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
---
 .../yocto-project-qs/yocto-project-qs.xml     | 42 ++++++++++++-------
 1 file changed, 27 insertions(+), 15 deletions(-)

diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index b97b1db875..f52c699c82 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -325,6 +325,8 @@
              </listitem>
          </itemizedlist>
 
+        <section id='installing-the-toolchain-and-setting-up-the-environment'>
+        <title>Installing the Toolchain and Setting Up the Environment</title>
          <para>
              You can download the pre-built toolchain, which includes the poky-qemu script and 
              support files, from <ulink url='http://yoctoproject.org/downloads/yocto-0.9/toolchain/'></ulink>.  
@@ -371,6 +373,24 @@
              </literallayout>
          </para>
 
+         <para>
+             The following command form sets up the emulation environment.
+         </para>
+
+         <literallayout class='monospaced'>
+     $ source /opt/poky/environment-setup-&lt;<emphasis>arch</emphasis>&gt;-poky-linux-&lt;<emphasis>if</emphasis>&gt; 
+
+     Where:
+         &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture: 
+                i586, x86-64, ppc603e, mips, or armv5te.
+
+         &lt;<emphasis>if</emphasis>&gt; is a string representing an embedded application binary interface.
+                Not all setup scripts include this string.
+         </literallayout>
+         </section>
+
+        <section id='downloading-the-pre-built-linux-kernel'>
+        <title>Downloading the Pre-Built Linux Kernel</title>
          <para>
              You can download the pre-built Linux kernel and the filesystem image suitable for 
              running in the emulator QEMU from 
@@ -390,7 +410,10 @@
          &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture: 
                 x86, x86-64, ppc, mips, or arm.
          </literallayout>
+         </section>
 
+        <section id='downloading-the-filesystem'>
+        <title>Downloading the Filesystem</title>
          <para>
              The filesystem image has two forms.
              One form is an <filename>ext3</filename> filesystem image.
@@ -409,22 +432,10 @@
          &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture: 
                 x86, x86-64, ppc, mips, or arm.
           </literallayout>
+         </section>
 
-         <para>
-             The following command form sets up the emulation environment.
-         </para>
-
-         <literallayout class='monospaced'>
-     $ source /opt/poky/environment-setup-&lt;<emphasis>arch</emphasis>&gt;-poky-linux-&lt;<emphasis>if</emphasis>&gt; 
-
-     Where:
-         &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture: 
-                i586, x86-64, ppc603e, mips, or armv5te.
-
-         &lt;<emphasis>if</emphasis>&gt; is a string representing an embedded application binary interface.
-                Not all setup scripts include this string.
-         </literallayout>
-
+        <section id='starting-the-qemu-emulator'>
+        <title>Starting the QEMU Emulator</title>
          <para>
               Finally, this command form invokes the QEMU emulator 
          </para>
@@ -453,6 +464,7 @@
      $ source /opt/poky/environment-setup-i586-poky-linux 
      $ poky-qemu qemui586 zImage-2.6.34-qemux86-0.9 yocto-image-sdk-qemux86-0.9.rootfs.ext3 ext3
          </literallayout>
+         </section>
          
     </section>
 </section>