dev-manual, kernel-dev, ref-manual: Updated task name usage.

There was inconsistency on how we refer to a task name throughout
the YP manual set.  The proper way is "do_<taskname>".  Some
occurrences did not include the "do_" prefix.  These have been
fixed.

(From yocto-docs rev: b32821bb0d3e6de7bca68b25c662a023526a10c4)

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

1 files changed, 8 insertions, 4 deletions

diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 4fd4c4e1e3..59e19a2bae 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -1773,8 +1773,10 @@
                     Make your changes in the temporary source code to the files you added
                     to the patch.</para></listitem>
                 <listitem><para><emphasis>Test Your Changes:</emphasis>
-                    Once you have modified the source code, the easiest way to test your changes
-                    is by calling the <filename>compile</filename> task as shown in the following example:
+                    Once you have modified the source code, the easiest way to
+                    your changes is by calling the
+                    <filename>do_compile</filename> task as shown in the
+                    following example:
                     <literallayout class='monospaced'>
      $ bitbake -c compile -f &lt;name_of_package&gt;
                     </literallayout>
@@ -1870,8 +1872,10 @@
                 <listitem><para><emphasis>Edit the Files:</emphasis>
                     Make your changes to the temporary source code.</para></listitem>
                 <listitem><para><emphasis>Test Your Changes:</emphasis>
-                    Once you have modified the source code, the easiest way to test your changes
-                    is by calling the <filename>compile</filename> task as shown in the following example:
+                    Once you have modified the source code, the easiest way
+                    to test your changes is by calling the
+                    <filename>do_compile</filename> task as shown in the
+                    following example:
                     <literallayout class='monospaced'>
      $ bitbake -c compile -f &lt;name_of_package&gt;
                     </literallayout>