documentation/dev-manual/dev-manual-common-tasks.xml: external SCM Update

Updated the section "Using an External SCM."  This section was
written so that PN was refering to a package instead of correctly
refering to the recipe.

(From yocto-docs rev: 2bf44cf78bef08d2dd4d9e596100900913777d60)

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 e456d540a07affdab1677759b51fb256c8c515f1..b42a09bf2baa55df14a188a6c3c2ce759ea822d7 100644 (file)
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1716,8 +1716,9 @@
 
         <para>
             If you're working on a recipe that pulls from an external Source Code Manager (SCM), it 
-            is possible to have the OpenEmbedded build system notice new changes added to the 
-            SCM and then build the package that depends on them using the latest version. 
+            is possible to have the OpenEmbedded build system notice new recipe changes added to the 
+            SCM and then build the resulting package that depends on the new recipes by using the latest 
+            versions. 
             This only works for SCMs from which it is possible to get a sensible revision number for changes.
             Currently, you can do this with Apache Subversion (SVN), Git, and Bazaar (BZR) repositories.
         </para>
@@ -1730,7 +1731,7 @@
      SRCREV_pn-&lt;PN&gt; = "${AUTOREV}"
             </literallayout>
             where <filename>PN</filename> 
-            is the name of the package for which you want to enable automatic source 
+            is the name of the recipe for which you want to enable automatic source 
             revision updating.
         </para>
     </section>