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, 3 insertions, 3 deletions

diff --git a/documentation/poky-ref-manual/ref-images.xml b/documentation/poky-ref-manual/ref-images.xml
index a4cd926d0d..0ffea5d19f 100644
--- a/documentation/poky-ref-manual/ref-images.xml
+++ b/documentation/poky-ref-manual/ref-images.xml
@@ -6,7 +6,7 @@
     <title>Reference: Images</title>
 
     <para>
-        The Yocto Project build process supports several types of images to satisfy different needs.  
+        The OpenEmbedded build process supports several types of images to satisfy different needs.  
         When you issue the <filename>bitbake</filename> command you provide a “top-level” recipe 
         that essentially begins the build for the type of image you want.
     </para>
@@ -32,8 +32,8 @@
         These recipes reside in the <filename>meta/recipes-core/images</filename>,
         <filename>meta/recipes-extended/images</filename>, 
         <filename>meta/recipes-graphics/images</filename>, and 
-        <filename>meta/recipes-sato/images</filename> directories of your local Yocto Project 
-        file structure (Git repository or extracted release tarball).  
+        <filename>meta/recipes-sato/images</filename> directories 
+        within the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>.  
         Although the recipe names are somewhat explanatory, here is a list that describes them:
     </para>