documentation/poky-ref-manual/technical-details.xml: Fixed various terms

I fixed several "Yocto Project build system" terms and some "Yocto
Project Build Directory" terms.

(From yocto-docs rev: 10c1d50380336ac684243525646ac9aa3c1812d4)

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

diff --git a/documentation/poky-ref-manual/technical-details.xml b/documentation/poky-ref-manual/technical-details.xml
index 4cc1a7b395d8a9fa9d8a861063f17f033c8218f6..2c6f7c2b9820ea8312c8fb2abc72d9d97c88ec11 100644 (file)
--- a/documentation/poky-ref-manual/technical-details.xml
+++ b/documentation/poky-ref-manual/technical-details.xml
@@ -87,8 +87,8 @@
             would build a cross compiler and <filename>eglibc</filename> if they had not already 
             been built.
             <note>This release of the Yocto Project does not support the <filename>glibc</filename>
-                GNU version of the Unix standard C library.  By default, the Yocto Project builds with
-                <filename>eglibc</filename>.</note>
+                GNU version of the Unix standard C library.  By default, the OpenEmbedded build system
+                builds with <filename>eglibc</filename>.</note>
         </para>
 
         <para>
@@ -139,7 +139,7 @@
 
         <para>
             The configuration files (<filename>.conf</filename>) define various configuration variables
-            that govern the Yocto Project build process. 
+            that govern the OpenEmbedded build process. 
             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
@@ -152,7 +152,7 @@
     <title>Shared State Cache</title>
 
     <para>
-        By design, the Yocto Project build system builds everything from scratch unless 
+        By design, the OpenEmbedded build system builds everything from scratch unless 
         BitBake can determine that parts don't need to be rebuilt.
         Fundamentally, building from scratch is attractive as it means all parts are 
         built fresh and there is no possibility of stale data causing problems. 
@@ -640,8 +640,7 @@
             Yocto Project, you can follow these steps to use the x32 spABI:
             <itemizedlist>
                 <listitem><para>Add the <filename>experimental/meta-x32</filename> layer to your local
-                    <ulink url='&YOCTO_DOCS_DEV_URL;#yocto-project-build-directory'>Yocto Project 
-                    Build Directory</ulink>.  
+                    <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink>.  
                     You can find the <filename>experimental/meta-x32</filename> source repository at
                     <ulink url='&YOCTO_GIT_URL;'></ulink>.</para></listitem>
                 <listitem><para>Edit your <filename>conf/bblayers.conf</filename> file so that it includes
@@ -682,7 +681,7 @@
     <title>Licenses</title>
 
     <para>
-        This section describes the mechanism by which the Yocto Project build system 
+        This section describes the mechanism by which the OpenEmbedded build system 
         tracks changes to licensing text.
         The section also describes how to enable commercially licensed recipes, 
         which by default are disabled.
@@ -797,7 +796,7 @@
         <title>Enabling Commercially Licensed Recipes</title>
 
         <para>
-            By default, the Yocto Project build system disables
+            By default, the OpenEmbedded build system disables
             components that have commercial or other special licensing
             requirements.  
             Such requirements are defined on a