documentation/poky-ref-manual: Yocto Project scrub

I have changed as many "Yocto Project" terms as possible so that
better reflect reality.

(From yocto-docs rev: 5f729e53b0cb653c97621e4e6598d9295d60ada5)

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

1 files changed, 11 insertions, 10 deletions

diff --git a/documentation/poky-ref-manual/development.xml b/documentation/poky-ref-manual/development.xml
index b897efd550..9628fcbd15 100644
--- a/documentation/poky-ref-manual/development.xml
+++ b/documentation/poky-ref-manual/development.xml
@@ -10,7 +10,7 @@
     <para>
         The Yocto Project supports several methods of application development through which 
         you can create user-space software designed to run on an embedded device that uses
-        a Linux Yocto image developed with the Yocto Project. 
+        a Yocto Project image, which was developed with the OpenEmbedded build system. 
         This flexibility allows you to choose the method that works best for you.  
         This chapter describes each development method.
     </para>
@@ -25,12 +25,12 @@
             section in that when you invoke <filename>devshell</filename> source files are 
             extracted into your working directory and patches are applied. 
             Then, a new terminal is opened and you are placed in the working directory.
-            In the new terminal all the Yocto Project build-related environment variables are 
+            In the new terminal, all the OpenEmbedded build-related environment variables are 
             still defined so you can use commands such as <filename>configure</filename> and 
             <filename>make</filename>. 
-            The commands execute just as if the Yocto Project build system were executing them. 
+            The commands execute just as if the OpenEmbedded build system were executing them. 
             Consequently, working this way can be helpful when debugging a build or preparing 
-            software to be used with the Yocto Project build system.
+            software to be used with the OpenEmbedded build system.
         </para>
 
         <para>
@@ -45,7 +45,7 @@
         </para>
 
         <para>
-            This command opens a terminal with a shell prompt within the Poky 
+            This command opens a terminal with a shell prompt within the Yocto Project 
             environment. 
             The following occurs:
             <itemizedlist>
@@ -58,7 +58,7 @@
             </itemizedlist>
             Within this environment, you can run <filename>configure</filename>
             or <filename>compile</filename> commands as if they were being run by 
-            the Yocto Project build system itself.
+            the OpenEmbedded build system itself.
             As noted earlier, the working directory also automatically changes to the 
             source directory (<filename><link linkend='var-S'>S</link></filename>).
         </para>
@@ -71,8 +71,8 @@
             The default shell used by <filename>devshell</filename> is xterm. 
             For examples of available options, see the "UI/Interaction Configuration"
             section of the  
-            <filename>meta/conf/bitbake.conf</filename> configuration file in the Yocto Project
-            files. 
+            <filename>meta/conf/bitbake.conf</filename> configuration file in the 
+            <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. 
         </para>
 
         <para>
@@ -99,7 +99,7 @@
 
         <para>
             If you're working on a recipe that pulls from an external Source Code Manager (SCM), it 
-            is possible to have the Yocto Project build system notice new changes added to the 
+            is possible to have the OpenEmbedded build system notice new changes added to the 
             SCM and then build the package that depends on them using the latest version. 
             This only works for SCMs from which it is possible to get a sensible revision number for changes.
             Currently, you can do this with Apache Subversion (SVN), Git, and Bazaar (BZR) repositories.
@@ -107,7 +107,8 @@
 
         <para>
             To enable this behavior, simply add the following to the <filename>local.conf</filename>
-            configuration file in the build directory of the Yocto Project files:
+            configuration file found in the 
+            <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink>:
             <literallayout class='monospaced'>
      SRCREV_pn-&lt;PN&gt; = "${AUTOREV}"
             </literallayout>