concepts-manual: Updated how the general build figure is referenced

this figure had been being referred to as the YP build process.
However, it is really more of the OpenEmbedded build system process.
Basically, what goes on during a build.  I changed the way the
general figure is referred to.

(From yocto-docs rev: 1cb79b04182bd660b37637d9cec7d6edf33fc292)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 13 insertions, 13 deletions

diff --git a/documentation/concepts-manual/concepts-manual-concepts.xml b/documentation/concepts-manual/concepts-manual-concepts.xml
index 0d01372c2e..c4c022205d 100644
--- a/documentation/concepts-manual/concepts-manual-concepts.xml
+++ b/documentation/concepts-manual/concepts-manual-concepts.xml
@@ -191,13 +191,13 @@
         <title>Development Concepts</title>
 
         <para>
-            This section takes a more detailed look inside the development
-            process.
-            The following diagram represents development at a high level.
+            This section takes a more detailed look inside the build
+            process used by the OpenEmbedded build system.
+            The following diagram represents the build at a high level.
             The remainder of this section expands on the fundamental input,
             output, process, and
-            <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>) blocks
-            that make up development in the Yocto Project environment.
+            <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
+            blocks that make up the build process.
         </para>
 
         <para id='general-yocto-environment-figure'>
@@ -205,7 +205,7 @@
         </para>
 
         <para>
-            In general, development consists of several functional areas:
+            In general, the build process consists of several functional areas:
             <itemizedlist>
                 <listitem><para>
                     <emphasis>User Configuration:</emphasis>
@@ -264,7 +264,7 @@
             <para>
                 The following figure shows an expanded representation of the
                 "User Configuration" box of the
-                <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>:
+                <link linkend='general-yocto-environment-figure'>general Build Process figure</link>:
             </para>
 
             <para>
@@ -535,7 +535,7 @@
                 The following figure shows an expanded representation of the
                 Metadata, Machine Configuration, and Policy Configuration input
                 (layers) boxes of the
-                <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>:
+                <link linkend='general-yocto-environment-figure'>general Build Process figure</link>:
             </para>
 
             <para>
@@ -698,7 +698,7 @@
                 In order for the OpenEmbedded build system to create an
                 image or any target, it must be able to access source files.
                 The
-                <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>
+                <link linkend='general-yocto-environment-figure'>general Build Process figure</link>
                 represents source files using the "Upstream Project Releases",
                 "Local Projects", and "SCMs (optional)" boxes.
                 The figure represents mirrors, which also play a role in
@@ -762,7 +762,7 @@
                 The remainder of this section provides a deeper look into the
                 source files and the mirrors.
                 Here is a more detailed look at the source file area of the
-                base figure:
+                <link linkend='general-yocto-environment-figure'>general Build Process figure</link>:
                 <imagedata fileref="figures/source-input.png" align="center" width="7in" depth="7.5in" />
             </para>
 
@@ -882,7 +882,7 @@
                 in the
                 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>.
                 The
-                <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>
+                <link linkend='general-yocto-environment-figure'>general Build Process figure</link>
                 shows this package feeds area in the upper-right corner.
             </para>
 
@@ -976,7 +976,7 @@
                 <ulink url='&YOCTO_DOCS_REF_URL;#bitbake-term'>BitBake</ulink>
                 to produce images.
                 You can see from the
-                <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>,
+                <link linkend='general-yocto-environment-figure'>general Build Process figure</link>,
                 the BitBake area consists of several functional areas.
                 This section takes a closer look at each of those areas.
             </para>
@@ -1731,7 +1731,7 @@
                 are compressed forms of the
                 root filesystem that are ready to boot on a target device.
                 You can see from the
-                <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>
+                <link linkend='general-yocto-environment-figure'>general Build Process figure</link>
                 that BitBake output, in part, consists of images.
                 This section is going to look more closely at this output:
                 <imagedata fileref="figures/images.png" align="center" width="5.5in" depth="5.5in" />