ref-manual: Updated "Application Development SDK" section.

Applied review comments to the section.

(From yocto-docs rev: 83871d0f6cd996be2d3476bdfc0f2adef9ff52a7)

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

diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml
index 2cbc10605a00d1ddbe49e2e58eca59d89d5a8f89..e237b3266f2a291bf40bd88b047db290d3082d0f 100644 (file)
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -1300,9 +1300,14 @@
             In the
             <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>,
             the output labeled "Application Development SDK" represents an
-            SDK (standard or extensible).
+            SDK.
+            The SDK generation process differs depending on whether you build
+            a standard SDK
+            (e.g. <filename>bitbake -c populate_sdk</filename> <replaceable>imagename</replaceable>)
+            or an extensible SDK
+            (e.g. <filename>bitbake -c populate_sdk_ext</filename> <replaceable>imagename</replaceable>).
             This section is going to take a closer look at this output:
-            <imagedata fileref="figures/sdk.png" align="center" />
+            <imagedata fileref="figures/sdk.png" align="center" width="9in" depth="7.25in" />
         </para>
 
         <para>
@@ -1317,8 +1322,8 @@
             part because it runs on the SDK machine.
             You can think of the libraries and headers as the "target"
             part because they are built for the target hardware.
-            The setup script is added so that you can initialize the
-            environment before using the tools.
+            The environment setup script is added so that you can initialize
+            the environment before using the tools.
         </para>
 
         <note>
@@ -1389,22 +1394,22 @@
                     Points to the <filename>deploy</filename> directory.
                     </para></listitem>
                 <listitem><para><link linkend='var-SDK_EXT_TYPE'><filename>SDK_EXT_TYPE</filename></link>:
-                    Specifies the required shared state artifacts for the
-                    extensible SDK.
+                    Controls whether or not shared state artifacts are copied
+                    into the extensible SDK.
                     By default, all required shared state artifacts are copied
                     into the SDK.
                     </para></listitem>
                 <listitem><para><link linkend='var-SDK_INCLUDE_PKGDATA'><filename>SDK_INCLUDE_PKGDATA</filename></link>:
-                    Includes as part of the extensible SDK the packagedata for
-                    all recipes in the "world" target.
+                    Specifies whether or not packagedata will be included in
+                    the extensible SDK for all recipes in the "world" target.
                     </para></listitem>
                 <listitem><para><link linkend='var-SDK_LOCAL_CONF_WHITELIST'><filename>SDK_LOCAL_CONF_WHITELIST</filename></link>:
                     A list of variables allowed through from the build system
                     configuration into the extensible SDK configuration.
                     </para></listitem>
                 <listitem><para><link linkend='var-SDK_LOCAL_CONF_BLACKLIST'><filename>SDK_LOCAL_CONF_BLACKLIST</filename></link>:
-                    A list of variables allowed through from the build system
-                    configuration into the extensible SDK configuration.
+                    A list of variables not allowed through from the build
+                    system configuration into the extensible SDK configuration.
                     </para></listitem>
                 <listitem><para><link linkend='var-SDK_INHERIT_BLACKLIST'><filename>SDK_INHERIT_BLACKLIST</filename></link>:
                     A list of classes to remove from the