From e8f5b17e86818ae6346ed40f0330cb19946ab626 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Fri, 4 Nov 2011 14:22:05 -0700
Subject: documentation/dev-manual/dev-manual-bsp-appendix.xml: Tom Zanussi
 edits.

Some wording changes to keep things accurate.  Also inserted some
"&nbsp" characters in some headings to force an extra space between
normal font and courier font words.  It appears the PDF version of
the generated manual shoves these words together with no intervening
space.  Looks like hell.

Reported by: Tom Zanussi
(From yocto-docs rev: 5dcb9ae99f1752599fd56a276ccafd79a52334f8)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/dev-manual/dev-manual-bsp-appendix.xml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

(limited to 'documentation')

diff --git a/documentation/dev-manual/dev-manual-bsp-appendix.xml b/documentation/dev-manual/dev-manual-bsp-appendix.xml
index 987941c87f..eecca8ebd4 100644
--- a/documentation/dev-manual/dev-manual-bsp-appendix.xml
+++ b/documentation/dev-manual/dev-manual-bsp-appendix.xml
@@ -100,7 +100,7 @@
     <para>
         You need to have the base BSP layer on your development system.  
         Similar to the local Yocto Project files, you can get the BSP 
-        layer a couple of different ways:  
+        layer in a couple of different ways:  
         download the BSP tarball and extract it, or set up a local Git repository that 
         has the Yocto Project BSP layers.  
         You should use the same method that you used to get the local Yocto Project files earlier.
@@ -282,7 +282,7 @@
         </para>
 
         <section id='changing-recipes-bsp'>
-            <title>Changing <filename>recipes-bsp</filename></title>
+            <title>Changing&nbsp;&nbsp;<filename>recipes-bsp</filename></title>
 
             <para>
                 First, let's look at <filename>recipes-bsp</filename>.
@@ -299,7 +299,7 @@
         </section>
 
         <section id='changing-recipes-graphics'>
-            <title>Changing <filename>recipes-graphics</filename></title>
+            <title>Changing&nbsp;&nbsp;<filename>recipes-graphics</filename></title>
 
             <para>
                 Now let's look at <filename>recipes-graphics</filename>.
@@ -320,7 +320,7 @@
         </section>
 
         <section id='changing-recipes-core'>
-            <title>Changing <filename>recipes-core</filename></title>
+            <title>Changing&nbsp;&nbsp;<filename>recipes-core</filename></title>
 
             <para>
                 Now let's look at changes in <filename>recipes-core</filename>.
@@ -349,7 +349,7 @@
         </section>
 
         <section id='changing-recipes-kernel'>
-            <title>Changing <filename>recipes-kernel</filename></title>
+            <title>Changing&nbsp;&nbsp;<filename>recipes-kernel</filename></title>
 
             <para>
                 Finally, let's look at <filename>recipes-kernel</filename> changes.
@@ -611,7 +611,7 @@
         Finally, once you have an image, you can try booting it from a device
         (e.g. a USB device).
         To prepare a bootable USB device, insert a USB flash drive into your build system and
-        copy the <filename>.hddimage</filename>, located in the 
+        copy the <filename>.hddimg</filename> file, located in the 
         <filename>poky/build/tmp/deploy/images</filename>
         directory after a successful build to the flash drive.  
         Assuming the USB flash drive takes device <filename>/dev/sdf</filename>, 
@@ -659,8 +659,8 @@
         contents with the contents of <filename>atom-pc.conf</filename> and replace 
         <filename>xorg.conf</filename> with <filename>atom-pc xorg.conf</filename>
         in <filename>meta-yocto</filename> and see if it fares any better.  
-        In any case, following the previous steps should
-        probably give you a buildable and bootable image.  
+        In any case, following the previous steps will give you a buildable image that 
+        will probably boot on most systems.
         Getting things working like you want
         them to for your hardware will normally require some amount of experimentation with
         configuration settings.
-- 
cgit v1.2.3-54-g00ecf