documentation: dev-manual - more wording changes.

I found other changes for underlying/corresponding wordings
regarding the relationship between .bb and .bbappend filenames.

(From yocto-docs rev: 28f12a4ea97a683281cd8cc0bbceb40d2b896aa4)

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

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 48b1cd3d276cb6859af0e2ce692e504e1edc6d93..4911b09dac532ba2d1df4ea9588beef2e510639b 100644 (file)
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -252,14 +252,14 @@
             </para>
 
             <para>
-                Append files files must have the same name as the underlying recipe.
+                Append files files must have the same name as the corresponding recipe.
                 For example, the append file <filename>someapp_&DISTRO;.bbappend</filename> must 
                 apply to <filename>someapp_&DISTRO;.bb</filename>.
                 This means the original recipe and append file names are version number specific.
-                If the underlying recipe is renamed to update to a newer version, the 
-                corresponding <filename>.bbappend</filename> file must be renamed as well.
+                If the corresponding recipe is renamed to update to a newer version, the 
+                underlying <filename>.bbappend</filename> file must be renamed as well.
                 During the build process, BitBake displays an error on starting if it detects a 
-                <filename>.bbappend</filename> file that does not have an underlying recipe 
+                <filename>.bbappend</filename> file that does not have a corresponding recipe 
                 with a matching name.
             </para>