dev-manual: Re-worded the "Customizing Images Using Custom .bb Files"

Changed the wording so that it reflects better what is actually
going on when use IMAGE_INSTALL to afect an image.

Reported-by: Robert P. J. Day <rpjday@crashcourse.ca>
(From yocto-docs rev: 36178822a53f9eb7065513c8b2b1b01fc166b771)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 4 insertions, 3 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 653f3da438..d6f5727114 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -891,7 +891,8 @@
             <title>Customizing Images Using Custom .bb Files</title>
 
             <para>
-                One way to get additional software into an image is to create a custom image.
+                One way to customize an image is to create a custom recipe
+                that defines additional software as part of the image.
                 The following example shows the form for the two lines you need:
                 <literallayout class='monospaced'>
      IMAGE_INSTALL = "packagegroup-core-x11-base package1 package2"
@@ -901,8 +902,8 @@
             </para>
 
             <para>
-                By creating a custom image, a developer has total control
-                over the contents of the image.
+                Defining the software using a custom recipe gives you total 
+                control over the contents of the image.
                 It is important to use the correct names of packages in the
                 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-IMAGE_INSTALL'>IMAGE_INSTALL</ulink></filename>
                 variable.