documentation/adt-manual: Adjustments to Yocto Project term

Changes throughout the manual that either eliminate or change
many of the "Yocto Project" strings.  The file structure for
the meta data is now called "source directory."  The build
directory is referred as just that - "build directory."  Any
where the build system is referred to it is called the
"OpenEmbedded build system."

(From yocto-docs rev: 1210c19f90d4a52042fec12657212ae3e58e13d6)

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

1 files changed, 3 insertions, 3 deletions

diff --git a/documentation/adt-manual/adt-package.xml b/documentation/adt-manual/adt-package.xml
index 26b5dc18d8..0da301b123 100644
--- a/documentation/adt-manual/adt-package.xml
+++ b/documentation/adt-manual/adt-package.xml
@@ -17,7 +17,7 @@
     <title>Package Management Systems</title>
 
     <para>
-        The Yocto Project supports the generation of sysroot files using 
+        The OpenEmbedded build system supports the generation of sysroot files using 
         three different Package Management Systems (PMS):
         <itemizedlist>
             <listitem><para><emphasis>OPKG:</emphasis> A less well known PMS whose use 
@@ -28,7 +28,7 @@
             <listitem><para><emphasis>RPM:</emphasis> A more widely known PMS intended for GNU/Linux 
                 distributions.  
                 This PMS works with files packaged in an <filename>.rms</filename> format.
-                The Yocto Project currently installs through this PMS by default.  
+                The build system currently installs through this PMS by default.  
                 See <ulink url='http://en.wikipedia.org/wiki/RPM_Package_Manager'></ulink>
                 for more information about RPM.</para></listitem>
             <listitem><para><emphasis>Debian:</emphasis> The PMS for Debian-based systems 
@@ -75,7 +75,7 @@
     </para>
 
     <para>
-        Next, source the environment setup script found in the Yocto Project files.  
+        Next, source the environment setup script found in the source directory.  
         Follow that by setting up the installation destination to point to your 
         sysroot as <filename>&lt;sysroot_dir&gt;</filename>.  
         Finally, have an OPKG configuration file <filename>&lt;conf_file&gt;</filename>