From f735e50c63ac9f0cd15ad6ad38e46565846fffe8 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Mon, 22 Oct 2012 14:16:22 -0700
Subject: documentation: poky-ref-manual - Final changes before the 1.3
 lockdown.

various changes as required.

(From yocto-docs rev: 7f166508337c9d4aadad23997470a8871c5e42a4)

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

(limited to 'documentation/poky-ref-manual/usingpoky.xml')

diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml
index 18bd8b7eb0..4ae6545479 100644
--- a/documentation/poky-ref-manual/usingpoky.xml
+++ b/documentation/poky-ref-manual/usingpoky.xml
@@ -30,20 +30,20 @@
             The first thing you need to do is set up the OpenEmbedded build environment by sourcing
             the environment setup script as follows:
             <literallayout class='monospaced'>
-     $ source oe-init-build-env [build_dir]
+     $ source &OE_INIT_FILE; [build_dir]
             </literallayout>
         </para>
 
         <para>
             The <filename>build_dir</filename> is optional and specifies the directory the 
             OpenEmbedded build system uses for the build - 
-            the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink>.
-            If you do not specify a build directory it defaults to <filename>build</filename>
+            the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
+            If you do not specify a Build Directory it defaults to <filename>build</filename>
             in your current working directory.
-            A common practice is to use a different build directory for different targets. 
+            A common practice is to use a different Build Directory for different targets. 
             For example, <filename>~/build/x86</filename> for a <filename>qemux86</filename>
             target, and <filename>~/build/arm</filename> for a <filename>qemuarm</filename> target.
-            See <link linkend="structure-core-script">oe-init-build-env</link>
+            See <link linkend="structure-core-script">&OE_INIT_FILE;</link>
             for more information on this script.
         </para>
 
@@ -58,7 +58,7 @@
             The <filename>target</filename> is the name of the recipe you want to build. 
             Common targets are the images in <filename>meta/recipes-core/images</filename>,
             <filename>/meta/recipes-sato/images</filename>, etc. all found in the 
-            <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>.
+            <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
             Or, the target can be the name of a recipe for a specific piece of software such as 
             <application>busybox</application>. 
             For more details about the images the OpenEmbedded build system supports, see the 
@@ -91,7 +91,7 @@
     <para>
         Once an image has been built, it often needs to be installed. 
         The images and kernels built by the OpenEmbedded build system are placed in the 
-        <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink> in 
+        <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> in 
         <filename class="directory">tmp/deploy/images</filename>. 
         For information on how to run pre-built images such as <filename>qemux86</filename> 
         and <filename>qemuarm</filename>, see the
@@ -268,7 +268,7 @@
             For guidance on how logging is handled in both Python and Bash recipes, see the 
             <filename>logging.bbclass</filename> file in the 
             <filename>meta/classes</filename> folder of the 
-            <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>.
+            <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
         </para>
 
         <section id='logging-with-python'>
-- 
cgit v1.2.3-54-g00ecf