documentation/poky-ref-manual: Fixed various references to YP

I did a scrub for "Yocto Project" and found some that could be
changed.

(From yocto-docs rev: 985062b6a9320e8a3ca3d3dafb6516db4fbc5bd5)

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

1 files changed, 11 insertions, 11 deletions

diff --git a/documentation/poky-ref-manual/technical-details.xml b/documentation/poky-ref-manual/technical-details.xml
index 2c6f7c2b98..717015be5c 100644
--- a/documentation/poky-ref-manual/technical-details.xml
+++ b/documentation/poky-ref-manual/technical-details.xml
@@ -15,7 +15,7 @@
 
     <para>
         The BitBake task executor together with various types of configuration files form the 
-        Yocto Project core.
+        OpenEmbedded Core.
         This section overviews the BitBake task executor and the
         configuration files by describing what they are used for and how they interact.
     </para>
@@ -55,7 +55,7 @@
         <title>BitBake</title>
 
         <para>
-            BitBake is the tool at the heart of the Yocto Project and is responsible
+            BitBake is the tool at the heart of the OpenEmbedded build system and is responsible
             for parsing the metadata, generating a list of tasks from it,
             and then executing those tasks. 
             To see a list of the options BitBake supports, use the following help command:
@@ -115,8 +115,8 @@
 
         <para>
             The term "package" can also be used to describe recipes.
-            However, since the same word is used for the packaged output from the Yocto 
-            Project (i.e. <filename>.ipk</filename> or <filename>.deb</filename> files), 
+            However, since the same word is used for the packaged output from the OpenEmbedded 
+            build system (i.e. <filename>.ipk</filename> or <filename>.deb</filename> files), 
             this document avoids using the term "package" when referring to recipes.
         </para>
     </section>
@@ -143,7 +143,7 @@
             These files fall into several areas that define machine configuration options, 
             distribution configuration options, compiler tuning options, general common configuration
             options and user configuration options (<filename>local.conf</filename>, which is found
-            in the Yocto Project files build directory).
+            in the <ulink url='build-directory'>build directory</ulink>).
         </para>
     </section>
 </section>
@@ -171,7 +171,7 @@
     <para>
         The Yocto Project implements shared state code that supports incremental builds.
         The implementation of the shared state code answers the following questions that
-        were fundamental roadblocks within the Yocto Project incremental build support system:
+        were fundamental roadblocks within the OpenEmbedded incremental build support system:
         <itemizedlist>
             <listitem>What pieces of the system have changed and what pieces have not changed?</listitem>
             <listitem>How are changed pieces of software removed and replaced?</listitem>
@@ -485,7 +485,7 @@
         <title>Tips and Tricks</title>
 
         <para>
-            The code in the Yocto Project that supports incremental builds is not 
+            The code in the build system that supports incremental builds is not 
             simple code.
             This section presents some tips and tricks that help you work around 
             issues related to shared state code.
@@ -691,10 +691,10 @@
         <title>Tracking License Changes</title>
 
         <para>
-            The license of an upstream project might change in the future. In order to prevent these changes
-            going unnoticed, the Yocto Project provides a 
+            The license of an upstream project might change in the future. 
+            In order to prevent these changes going unnoticed, the  
             <filename><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link></filename>
-            variable to track changes to the license text. The checksums are validated at the end of the
+            variable tracks changes to the license text. The checksums are validated at the end of the
             configure step, and if the checksums do not match, the build will fail.
         </para>
 
@@ -714,7 +714,7 @@
             </para>
 
             <para>
-                The Yocto Project uses the 
+                The build system uses the 
                 <filename><link linkend='var-S'>S</link></filename> variable as the 
                 default directory used when searching files listed in 
                 <filename>LIC_FILES_CHKSUM</filename>.