documentation: Changes section head for sumbitting change to YP

Fixes [YOCTO #11630]

I changed the section heading for the section that describes how
to make a change to the YP.  It was passive.  I need it to be
active and in line with the "how-to" dev-manual.

(From yocto-docs rev: 340e1b6ab9806ec11ec894d4472bc2c937c2b058)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

documentation/bsp-guide/bsp.xml

@@ -832,7 +832,7 @@
                                     This is the person to whom patches and questions should
                                     be sent.
                                     For information on how to find the right person, see the
-                                    "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>How to Submit a Change</ulink>"
+                                    "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>Submitting a Change to the Yocto Project</ulink>"
                                     section in the Yocto Project Development Manual.
                                     </para></listitem>
                                 <listitem><para>Instructions on how to build the BSP using the BSP

documentation/dev-manual/dev-manual-common-tasks.xml

@@ -11410,7 +11410,7 @@
                 need to submit the fix for the recipe in OE-Core and upstream
                 so that the problem is taken care of at its source.
                 See the
-                "<link linkend='how-to-submit-a-change'>How to Submit a Change</link>"
+                "<link linkend='how-to-submit-a-change'>Submitting a Change to the Yocto Project</link>"
                 section for more information.
             </para>
         </section>

documentation/dev-manual/dev-manual-newbie.xml

@@ -348,14 +348,14 @@
                         to send patches to the project to fix bugs or add features.
                         If you do submit patches, follow the project commit
                         guidelines for writing good commit messages.
-                        See the "<link linkend='how-to-submit-a-change'>How to Submit a Change</link>"
+                        See the "<link linkend='how-to-submit-a-change'>Submitting a Change to the Yocto Project</link>"
                         section.
                         </para></listitem>
                     <listitem><para>
                         Send changes to the core sooner than later
                         as others are likely to run into the same issues.
                         For some guidance on mailing lists to use, see the list in the
-                        "<link linkend='how-to-submit-a-change'>How to Submit a Change</link>"
+                        "<link linkend='how-to-submit-a-change'>Submitting a Change to the Yocto Project</link>"
                         section.
                         For a description of the available mailing lists, see the
                         "<ulink url='&YOCTO_DOCS_REF_URL;#resources-mailinglist'>Mailing Lists</ulink>"
@@ -453,7 +453,7 @@
 </section>
 
 <section id='how-to-submit-a-change'>
-    <title>How to Submit a Change</title>
+    <title>Submitting a Change to the Yocto Project</title>
 
     <para>
         Contributions to the Yocto Project and OpenEmbedded are very welcome.

documentation/kernel-dev/kernel-dev-examples.xml

@@ -693,8 +693,8 @@
                     The messages used to commit changes are a large part of these standards.
                     Consequently, be sure that the headers for each commit have the required information.
                     For information on how to follow the Yocto Project commit message standards, see the
-                    "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>How to Submit a
-                    Change</ulink>" section in the Yocto Project Development Manual.
+                    "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>Submitting a Change to the Yocto Project</ulink>"
+                    section in the Yocto Project Development Manual.
                 </para>
 
                 <para>

documentation/ref-manual/ref-development-environment.xml

@@ -96,7 +96,7 @@
         reflect release strategies and so forth.
         <note>For information on finding out who is responsible for (maintains)
             a particular area of code, see the
-            "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>How to Submit a Change</ulink>"
+            "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>Submitting a Change to the Yocto Project</ulink>"
             section of the Yocto Project Development Manual.
         </note>
     </para>
@@ -143,7 +143,7 @@
         the maintainer include them into "master".
         This process is called “submitting a patch” or "submitting a change."
         For information on submitting patches and changes, see the
-        "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>How to Submit a Change</ulink>"
+        "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>Submitting a Change to the Yocto Project</ulink>"
         section in the Yocto Project Development Manual.
     </para>
 
@@ -249,7 +249,7 @@
                 <filename>git format-patch</filename> and
                 <filename>git send-email</filename>.
                 For information on how to use these scripts, see the
-                "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>How to Submit a Change</ulink>"
+                "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>Sumbitting a Change to the Yocto Project</ulink>"
                 section in the Yocto Project Development Manual.
                 </para></listitem>
         </itemizedlist>

documentation/ref-manual/resources.xml

@@ -27,7 +27,7 @@
         or by submitting patches through email.
         For information on how to do both as well as information on how
         to identify the maintainer for each area of code, see the
-        "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>How to Submit a Change</ulink>"
+        "<ulink url='&YOCTO_DOCS_DEV_URL;#how-to-submit-a-change'>Submitting a Change to the Yocto Project</ulink>"
         section in the Yocto Project Development Manual.
     </para>
 </section>