1 files changed, 10 insertions, 7 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 9e269c1cdb..23ea2df38e 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -5369,12 +5369,15 @@
         <title>Using an External SCM</title>
 
         <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 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.
+            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 recipe changes added to the SCM and then build
+            the resulting packages that depend 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>
 
         <para>
@@ -5384,7 +5387,7 @@
             <literallayout class='monospaced'>
      SRCREV_pn-&lt;PN&gt; = "${AUTOREV}"
             </literallayout>
-            where <ulink url='&YOCTO_DOCS_REF_URL;#var-PN'><filename>PN</filename></ulink>
+            <ulink url='&YOCTO_DOCS_REF_URL;#var-PN'><filename>PN</filename></ulink>
             is the name of the recipe for which you want to enable automatic source
             revision updating.
         </para>