documentation: Section Heading change for pushing commits

Changed the section heading for the part describing how to
push changes upstream via the poky scripts.  Also had to
change one cross-reference to the section in the kernel
manual.

(From yocto-docs rev: be7712aba044238e8781cdf869c5d14e77eb09a2)

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

1 files changed, 6 insertions, 6 deletions

diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 5ea6194ae0..8b58bb675e 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -987,11 +987,11 @@
                 your detailed description.
                 For example, the Yocto Project uses a specific convention for bug
                 references - any commit that addresses a specific bug should include the
-                bug ID in the description (typically at the end) as follows:
+                bug ID in the description (typically at the beginning) as follows:
                 <literallayout class='monospaced'>
-     &lt;detailed description of change&gt;
-
      [YOCTO #&lt;bug-id&gt;]
+
+     &lt;detailed description of change&gt;
                 </literallayout></para></listitem>
                 Where &lt;bug-id&gt; is replaced with the specific bug ID from the
                 Yocto Project Bugzilla instance.
@@ -1009,7 +1009,7 @@
     </para> 
 
     <section id='pushing-a-change-upstream'>
-        <title>Pushing a Change Upstream and Requesting a Pull</title>
+        <title>Using Scripts to Push a Change Upstream and Request a Pull</title>
 
         <para>
             The basic flow for pushing a change to an upstream "contrib" Git repository is as follows:
@@ -1100,8 +1100,8 @@
                     see <filename>GIT_FORMAT_PATCH(1)</filename> displayed using the  
                     <filename>man git-format-patch</filename> command.</para>
                     <note>If you have many patches to submit, you might consider using the 
-                    method described in the "<link linkend='pushing-a-change-upstream'>Pushing
-                    a change Upstream and Requesting a Pull</link>" section described 
+                    method described in the "<link linkend='pushing-a-change-upstream'>Using Scripts to Push
+                    a change Upstream and Request a Pull</link>" section described 
                     earlier in the manual.
                     This method uses the <filename>create-pull-request</filename> and 
                     <filename>send-pull-request</filename> scripts that automate much of the