documentation/dev-manual/dev-manual-cases.xml: partial - finished edits to BSP section.

(From yocto-docs rev: 3f7f97f869edab6a8ad7678ac05c7a681624e5c8)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 5 insertions, 4 deletions

diff --git a/documentation/dev-manual/dev-manual-cases.xml b/documentation/dev-manual/dev-manual-cases.xml
index c1ebaf9ff7..727995800d 100644
--- a/documentation/dev-manual/dev-manual-cases.xml
+++ b/documentation/dev-manual/dev-manual-cases.xml
@@ -602,7 +602,7 @@
             </para>
 
             <para>
-                To get ready to build your new layer you need to do the following:
+                To get ready to build your image that uses the new layer you need to do the following:
                <orderedlist>
                    <listitem><para>Get the environment ready for the build by sourcing the environment 
                        script. 
@@ -619,7 +619,8 @@
                        Thus, entering the previous command created the <filename>yocto-build</filename> directory.  
                        If you do not provide a name for the build directory it defaults to 
                        <filename>build</filename>.  
-                       The <filename>build</filename> directory contains a <filename>conf</filename> directory that has 
+                       The <filename>yocot-build</filename> directory contains a 
+                       <filename>conf</filename> directory that has 
                        two configuration files you will need to check:  <filename>bblayers.conf</filename>
                        and <filename>local.conf</filename>.</para></listitem>
                    <listitem><para>Check and edit the resulting <filename>local.conf</filename> file.
@@ -721,12 +722,12 @@
                 For example, moving your working directory around could cause problems.  
                 Here is the command for this example:
                 <literallayout class='monospaced'>
-     $ bitbake –k poky-image-sato-live
+     $ bitbake –k core-image-sato-live
                 </literallayout>
             </para>
 
             <para>
-                This command requests an image that has Sato support and can be run from a USB device or 
+                This command specifies an image that has Sato support and that can be run from a USB device or 
                 from a CD without having to first install anything.  
                 The build process takes significant time and includes thousands of tasks, which are reported 
                 at the console.