overview-manual: Updates to "OpenEmbedded Build System Concepts"

I removed the less than pretty build process figure and swapped
in the more aesthetically pleasing one.  Also, am refering to
the figure as the "general workflow figure".

(From yocto-docs rev: 093f1337131bc658d6afd1b56fb3661a76751aad)

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

1 files changed, 18 insertions, 11 deletions

diff --git a/documentation/overview-manual/overview-manual-concepts.xml b/documentation/overview-manual/overview-manual-concepts.xml
index 8f32dc62b1..e17a973c9f 100644
--- a/documentation/overview-manual/overview-manual-concepts.xml
+++ b/documentation/overview-manual/overview-manual-concepts.xml
@@ -244,29 +244,35 @@
 
         <para>
             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.
+            process used by the
+            <ulink url='&YOCTO_DOCS_REF_URL;#build-system-term'>OpenEmbedded build system</ulink>,
+            which is the build system specific to the Yocto Project.
+            At the heart of the build system is BitBake, the task executor.
+        </para>
+
+        <para>
+            The following diagram represents a 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 the build process.
+            output, process, and metadata logical blocks that make up the
+            OpenEmbedded build system's workflow.
         </para>
 
         <para id='general-yocto-environment-figure'>
-            <imagedata fileref="figures/yocto-environment-ref.png" align="center" width="8in" depth="4.25in" />
+            <imagedata fileref="figures/YP-flow-diagram.png" format="PNG" align='center' width="8in"/>
         </para>
 
         <para>
-            In general, the build process consists of several functional areas:
+            In general, the build's workflow consists of several functional
+            areas:
             <itemizedlist>
                 <listitem><para>
                     <emphasis>User Configuration:</emphasis>
-                    Metadata you can use to control the build process.
+                    metadata you can use to control the build process.
                     </para></listitem>
                 <listitem><para>
                     <emphasis>Metadata Layers:</emphasis>
                     Various layers that provide software, machine, and
-                    distro Metadata.
+                    distro metadata.
                     </para></listitem>
                 <listitem><para>
                     <emphasis>Source Files:</emphasis>
@@ -285,7 +291,8 @@
                     <emphasis>Package Feeds:</emphasis>
                     Directories containing output packages (RPM, DEB or IPK),
                     which are subsequently used in the construction of an
-                    image or SDK, produced by the build system.
+                    image or Software Development Kit (SDK), produced by the
+                    build system.
                     These feeds can also be copied and shared using a web
                     server or other means to facilitate extending or updating
                     existing images on devices at runtime if runtime package
@@ -293,7 +300,7 @@
                     </para></listitem>
                 <listitem><para>
                     <emphasis>Images:</emphasis>
-                    Images produced by the development process.
+                    Images produced by the workflow.
                     </para></listitem>
                 <listitem><para>
                     <emphasis>Application Development SDK:</emphasis>