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, 32 insertions, 23 deletions

diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml
index 6b56c5abb9..7c2fc11818 100644
--- a/documentation/poky-ref-manual/faq.xml
+++ b/documentation/poky-ref-manual/faq.xml
@@ -13,11 +13,17 @@
         </question>
         <answer>
             <para>
-                Poky is the Yocto Project build system that was derived from <ulink 
+                The term "Poky" is sometimes used to refer to the build system that the 
+                Yocto Project uses.  
+                The build system used in the Yocto project is referred to as the 
+                OpenEmbedded build system because "Poky" was derived from <ulink 
                 url='&OE_HOME_URL;'>OpenEmbedded</ulink>.
                 Poky is a stable, smaller subset focused on the mobile environment. 
                 Development in the Yocto Project using Poky is closely tied to OpenEmbedded with 
                 features being merged regularly between the two for mutual benefit.
+                For a fuller description of the term "Poky", see the 
+                <ulink url='&YOCTO_DOCS_DEV_URL;#poky'>poky</ulink> term in the Yocto Project
+                Development Manual.
             </para>
         </answer>
     </qandaentry>
@@ -64,7 +70,8 @@
             <para>
                 There are three areas that help with stability;
                 <itemizedlist>
-                    <listitem><para>The Yocto Project team keeps Poky small and focused.
+                    <listitem><para>The Yocto Project team keeps 
+                        <ulink url='&YOCTO_DOCS_DEV_URL;#poky'>Poky</ulink> small and focused.
                         It contains around 650 packages as compared to over 5000 for full 
                         OpenEmbedded.</para></listitem>
                     <listitem><para>The Yocto Project only supports hardware that the 
@@ -100,16 +107,17 @@
     <qandaentry>
         <question>
             <para>
-                Are there any products using Poky?
+                Are there any products using the OpenEmbedded build system (poky)?
             </para>
         </question>
         <answer>
             <para>
                 The <ulink url='http://vernier.com/labquest/'>Vernier LabQuest</ulink> is using 
-                the Yocto Project build system Poky.  
+                the OpenEmbedded build system.  
                 See the <ulink url='http://www.vernier.com/products/interfaces/labq/'>Vernier LabQuest</ulink>
                 for more information.
-                There are a number of pre-production devices using Poky and the Yocto Project team
+                There are a number of pre-production devices using the OpenEmbedded build system 
+                and the Yocto Project team
                 announces them as soon as they are released.
             </para>
         </answer>
@@ -118,13 +126,13 @@
     <qandaentry>
         <question>
             <para>
-                What does the Yocto Project build system Poky produce as output?
+                What does the OpenEmbedded build system produce as output?
             </para>
         </question>
         <answer>
             <para>
                 Because the same set of recipes can be used to create output of various formats, the 
-                output of a Yocto Project build depends on how it was started. 
+                output of an OpenEmbedded build depends on how it was started. 
                 Usually, the output is a flashable image ready for the target device.
             </para>
         </answer>
@@ -155,7 +163,7 @@
         </question>
         <answer>
             <para>
-                The Yocto Project can build packages in various formats such as
+                The OpenEmbedded build system can build packages in various formats such as
                 <filename>ipk</filename> for <filename>ipkg</filename>/<filename>opkg</filename>, 
                 Debian package (<filename>.deb</filename>), or RPM. 
                 The packages can then be upgraded using the package tools on the device, much like 
@@ -223,8 +231,8 @@
             </para>
 
             <para>
-                Once these packages are installed, the Yocto Project will be able to build standard 
-                images.
+                Once these packages are installed, the OpenEmbedded build system will be able 
+                to build standard images.
                 However, there might be a problem with the QEMU emulator segfaulting. 
                 You can either disable the generation of binary locales by setting 
                 <filename><link linkend='var-ENABLE_BINARY_LOCALE_GENERATION'>ENABLE_BINARY_LOCALE_GENERATION</link>
@@ -244,14 +252,14 @@
         <answer>
             <para>
                 Nothing is wrong.
-                The Yocto Project checks any configured source mirrors before downloading 
+                The OpenEmbedded build system checks any configured source mirrors before downloading 
                 from the upstream sources. 
-                The Yocto Project does this searching for both source archives and 
+                The build system does this searching for both source archives and 
                 pre-checked out versions of SCM managed software. 
                 These checks help in large installations because it can reduce load on the SCM servers 
                 themselves. 
                 The address above is one of the default mirrors configured into the 
-                Yocto Project.
+                build system.
                 Consequently, if an upstream source disappears, the team 
                 can place sources there so builds continue to work.
             </para>
@@ -284,7 +292,7 @@
         </question>
         <answer>
             <para>
-                Most source fetching by the Yocto Project is done by <filename>wget</filename>
+                Most source fetching by the OpenEmbedded build system is done by <filename>wget</filename>
                 and you therefore need to specify the proxy settings in a 
                 <filename>.wgetrc</filename> file in your home directory. 
                 Example settings in that file would be 
@@ -350,7 +358,7 @@
                 the most likely explanation is that either the hardware you're running the 
                 build on has some problem, or, if you are running the build under virtualisation, 
                 the virtualisation probably has bugs. 
-                The Yocto Project processes a massive amount of data causing lots of network, disk and 
+                The OpenEmbedded build system processes a massive amount of data causing lots of network, disk and 
                 CPU activity and is sensitive to even single bit failures in any of these areas. 
                 True random failures have always been traced back to hardware or virtualisation issues.
             </para>
@@ -449,7 +457,7 @@
         <answer>
             <para>
                 The Yocto Project team has tried to do this before but too many of the tools 
-                the Yocto Project depends on such as <filename>autoconf</filename> 
+                the OpenEmbedded build system depends on such as <filename>autoconf</filename> 
                 break when they find spaces in pathnames.  
                 Until that situation changes, the team will not support spaces in pathnames.
             </para>
@@ -495,14 +503,14 @@
     <qandaentry>
         <question>
             <para id='how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server'>
-                How does the Yocto Project build system obtain source code and will it work behind my 
+                How does the OpenEmbedded build system obtain source code and will it work behind my 
                 firewall or proxy server?
             </para>
         </question>
         <answer>
             <para>
-                The way the Yocto Project obtains source code is highly configurable.
-                You can setup the Yocto Project to get source code in most environments if
+                The way the build system obtains source code is highly configurable.
+                You can setup the build system to get source code in most environments if
                 HTTP transport is available.
             </para>
             <para>
@@ -511,7 +519,8 @@
                 and then MIRRORS in that order.
             </para>
             <para>
-                By default, Poky uses the Yocto Project source PREMIRRORS for SCM-based sources, 
+                By default, the OpenEmbedded build system uses the Yocto Project source PREMIRRORS 
+                for SCM-based sources, 
                 upstreams for normal tarballs, and then falls back to a number of other mirrors 
                 including the Yocto Project source mirror if those fail.
             </para>
@@ -574,7 +583,7 @@
                  any network accesses to anything other than the PREMIRROR would fail.
              </para>
              <para>
-                 Poky also honors the standard shell environment variables 
+                 The build system also honors the standard shell environment variables 
                  <filename>http_proxy</filename>, <filename>ftp_proxy</filename>, 
                  <filename>https_proxy</filename>, and <filename>all_proxy</filename>
                  to redirect requests through proxy servers.
@@ -600,8 +609,8 @@
             </para>
 
             <para>
-                Within the Yocto Project Build Directory is the <filename>tmp</filename>
-                directory. 
+                Within the <ulink url='&YOCTO_DOCS_DEV_URL;buile-directory'>build directory</ulink>
+                is the <filename>tmp</filename> directory. 
                 To remove all the build output yet preserve any source code or downloaded files
                 from previous builds, simply remove the <filename>tmp</filename> directory.
             </para>