ref-manual: Updates to "Image Generation" section.

Fixed wording on how the OpenEmbedded build system dynamically
generates do_image_* tasks as needed during image generation.

(From yocto-docs rev: 9df98d77a446cd5d27c4e87418117a904b1f4231)

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

1 files changed, 10 insertions, 9 deletions

diff --git a/documentation/ref-manual/ref-development-environment.xml b/documentation/ref-manual/ref-development-environment.xml
index 13399016b1..543a669e05 100644
--- a/documentation/ref-manual/ref-development-environment.xml
+++ b/documentation/ref-manual/ref-development-environment.xml
@@ -2243,15 +2243,16 @@
             </para>
 
             <para>
-                The <filename>do_image</filename> task dynamically creates
-                other <filename>do_image_*</filename> tasks as needed, which
-                include compressing the root filesystem image to reduce the
-                overall size of the image.
-                The process turns everything into an image file or a set of
-                image files.
-                The formats used for the root filesystem depend on the
+                The OpenEmbedded build system dynamically creates
+                <filename>do_image_*</filename> tasks as needed, based
+                on the image types specified in the
                 <link linkend='var-IMAGE_FSTYPES'><filename>IMAGE_FSTYPES</filename></link>
                 variable.
+                The process turns everything into an image file or a set of
+                image files and compresses the root filesystem image to reduce
+                the overall size of the image.
+                The formats used for the root filesystem depend on the
+                <filename>IMAGE_FSTYPES</filename> variable.
             </para>
 
             <para>
@@ -2262,8 +2263,8 @@
      do_image_<replaceable>type</replaceable>[depends]
                 </literallayout>
                 So, if the <replaceable>type</replaceable> as specified by the
-                <link linkend='var-IMAGE_FSTYPES'><filename>IMAGE_FSTYPES</filename></link>
-                were <filename>ext4</filename>, the dynamically generated task
+                <filename>IMAGE_FSTYPES</filename> were
+                <filename>ext4</filename>, the dynamically generated task
                 would be as follows:
                 <literallayout class='monospaced'>
      do_image_ext4[depends]