overview-manual: Minor wording changes to the "Images" section.

(From yocto-docs rev: a3e825e6086ec7674641658cc956020e3e1cd9dd)

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

1 files changed, 4 insertions, 5 deletions

diff --git a/documentation/overview-manual/overview-manual-concepts.xml b/documentation/overview-manual/overview-manual-concepts.xml
index 80cf3ad2d2..c3e4b457ff 100644
--- a/documentation/overview-manual/overview-manual-concepts.xml
+++ b/documentation/overview-manual/overview-manual-concepts.xml
@@ -1955,7 +1955,7 @@
                 You can see from the
                 <link linkend='general-workflow-figure'>general workflow figure</link>
                 that BitBake output, in part, consists of images.
-                This section is going to look more closely at this output:
+                This section takes a closer look at this output:
                 <imagedata fileref="figures/images.png" align="center" width="5.5in" depth="5.5in" />
             </para>
 
@@ -1987,9 +1987,9 @@
                         A kernel binary file.
                         The
                         <ulink url='&YOCTO_DOCS_REF_URL;#var-KERNEL_IMAGETYPE'><filename>KERNEL_IMAGETYPE</filename></ulink>
-                        variable setting determines the naming scheme for the
+                        variable determines the naming scheme for the
                         kernel image file.
-                        Depending on that variable, the file could begin with
+                        Depending on this variable, the file could begin with
                         a variety of naming strings.
                         The
                         <filename>deploy/images/</filename><replaceable>machine</replaceable>
@@ -2003,8 +2003,7 @@
                         <filename>*.bz2</filename> files).
                         The
                         <ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_FSTYPES'><filename>IMAGE_FSTYPES</filename></ulink>
-                        variable setting determines the root filesystem image
-                        type.
+                        variable determines the root filesystem image type.
                         The
                         <filename>deploy/images/</filename><replaceable>machine</replaceable>
                         directory can contain multiple root filesystems for the