From 175e4bd923f34e088cd1965b3658a52a52d0b105 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Mon, 1 Oct 2012 08:51:21 -0700
Subject: [PATCH] documentation: dev-manual - Changes to "Source Directory"
 use.

I standardized the use of the term "Source Directory" when
referring to the poky directory as set up on the host.

(From yocto-docs rev: 3eaf7a734a4eecab2be2c8e71bee4d6c2cb7788b)

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

diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index cf489df5c5..54a2beca4c 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -102,11 +102,11 @@
                     "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both
                     in the Yocto Project Quick Start for requirements.</para></listitem>
                 <listitem><para><emphasis>Establish a local copy of the project files on your 
-                    system</emphasis>:  You need this <link linkend='source-directory'>source 
-                    directory</link> available on your host system. 
+                    system</emphasis>:  You need this <link linkend='source-directory'>Source 
+                    Directory</link> available on your host system. 
                     Having these files on your system gives you access to the build
                     process and to the tools you need.
-                    For information on how to set up the source directory, see the
+                    For information on how to set up the Source Directory, see the
                     "<link linkend='getting-setup'>Getting Setup</link>" section.</para></listitem>
                 <listitem><para><emphasis>Establish a local copy of the base BSP files</emphasis>:  Having    
                     the BSP files on your system gives you access to the build
@@ -159,7 +159,7 @@
                     Yocto Project release: <filename>atom-pc</filename>, <filename>beagleboard</filename>,
                     <filename>mpc8315e</filename>, and <filename>routerstationpro</filename>.  
                     The recipes and configurations for these four BSPs are located and dispersed 
-                    within the <link linkend='source-directory'>source directory</link>.
+                    within the <link linkend='source-directory'>Source Directory</link>.
                     On the other hand, BSP layers for Cedar Trail, Chief River, Crown Bay, 
                     Crystal Forest, Emenlow, Fish River, Fish River 2, Jasper Forest, N450, 
                     Romley, sys940x, Sugar Bay, and tlk exist in their own separate layers 
@@ -172,7 +172,7 @@
                     configuration information.  
                     You can see the standard layout for the Crown Bay BSP in this example by examining the 
                     directory structure of the <filename>meta-crownbay</filename> layer inside the 
-                    source directory.</para></listitem>
+                    Source Directory.</para></listitem>
                 <listitem><para><emphasis>Make configuration changes to your new BSP 
                     layer</emphasis>:  The standard BSP layer structure organizes the files you need 
                     to edit in <filename>conf</filename> and several <filename>recipes-*</filename>
@@ -428,7 +428,7 @@
                         fragments, new kernel recipes, and the kernel <filename>.bbappend</filename>
                         file used during the build. 
                         It is good practice to set this repository up inside your local 
-                        source directory.
+                        <link linkend='source-directory'>Source Directory</link>.
                         For information on how to get these files, see the bulleted item
                         "<link linkend='poky-extras-repo'>The <filename>poky-extras</filename> Git Repository</link>"
                         earlier in this manual.
@@ -1442,7 +1442,7 @@ directory.</para></listitem>
                             to open a new recipe wizard.</para></listitem>
                         <listitem><para>Point to your source by filling in the "SRC_URL" field.
                             For example, you can add a recipe to your 
-                            <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>
+                            <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>
                             by defining "SRC_URL" as follows:
                             <literallayout class='monospaced'>
      ftp://ftp.gnu.org/gnu/m4/m4-1.4.9.tar.gz
@@ -1554,7 +1554,7 @@ directory.</para></listitem>
             <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-S'>S</ulink></filename> variable.
             Below is the default value for the <filename>S</filename> variable as defined in the 
             <filename>meta/conf/bitbake.conf</filename> configuration file in the 
-            <link linkend='source-directory'>source directory</link>:
+            <link linkend='source-directory'>Source Directory</link>:
             <literallayout class='monospaced'>
      S = ${WORKDIR}/${BP}
             </literallayout>
@@ -1579,7 +1579,8 @@ directory.</para></listitem>
      ${TMPDIR}/work/${PACKAGE_ARCH}-poky-${TARGET_OS}/${PN}-${PV}-${PR}
             </literallayout>
             Let's look at an example without variables.
-            Assuming a top-level source directory named <filename>poky</filename>
+            Assuming a top-level <link linkend='source-directory'>Source Directory</link>
+            named <filename>poky</filename>
             and a default build directory of <filename>poky/build</filename>, 
             the following is the work directory for the <filename>acl</filename> package:
             <literallayout class='monospaced'>
@@ -1592,7 +1593,7 @@ directory.</para></listitem>
             <literallayout class='monospaced'>
      ${TMPDIR}/work/${MACHINE}-poky-${TARGET_OS}/${PN}-${PV}-${PR}
             </literallayout>
-            Again, assuming top-level source directory named <filename>poky</filename>
+            Again, assuming top-level Source Directory named <filename>poky</filename>
             and a default build directory of <filename>poky/build</filename>, the 
             following is the work directory for the <filename>acl</filename> package that is being 
             built for a MIPS-based device:
@@ -1918,7 +1919,7 @@ directory.</para></listitem>
         or <filename>compile</filename> commands as if they were being run by 
         the OpenEmbedded build system itself.
         As noted earlier, the working directory also automatically changes to the 
-        source directory (<ulink url='&YOCTO_DOCS_REF_URL;#var-S'><filename>S</filename></ulink>).
+        Source Directory (<ulink url='&YOCTO_DOCS_REF_URL;#var-S'><filename>S</filename></ulink>).
     </para>
 
     <para>