documentation/kernel-manual/kernel-concepts.xml: Changed git to Git as needed (From yocto-docs rev: 3e4f2e32c0b98ccbc1eaa370832c0147f1a48045)

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

documentation/kernel-manual/kernel-concepts.xml

@@ -46,11 +46,11 @@
             the baseline kernel is the most stable official release.</para></listitem>
             <listitem><para>Include major technological features as part of Yocto Project's up-rev 
             strategy.</para></listitem>
-            <listitem><para>Present a git tree, that just like the upstream kernel.org tree, has a 
+            <listitem><para>Present a Git tree, that just like the upstream kernel.org tree, has a 
             clear and continuous history.</para></listitem>
             <listitem><para>Deliver a key set of supported kernel types, where each type is tailored 
             to a specific use case (i.g. networking, consumer, devices, and so forth).</para></listitem>
-            <listitem><para>Employ a git branching strategy that from a customer's point of view
+            <listitem><para>Employ a Git branching strategy that from a customer's point of view
             results in a linear path from the baseline kernel.org, through a select group of features and
             ends with their BSP-specific commits.</para></listitem>
         </itemizedlist>
@@ -170,7 +170,7 @@
                 You can think of the Yocto Project kernel as consisting of a baseline kernel with
                 added features logically structured on top of the baseline.
                 The features are tagged and organized by way of a branching strategy implemented by the 
-                source code manager (SCM) git. 
+                source code manager (SCM) Git. 
                 The result is that the user has the ability to see the added features and 
                 the commits that make up those features.
                 In addition to being able to see added features, the user can also view the history of what 
@@ -279,15 +279,15 @@
         </section>
      
         <section id='source-code-manager-git'>
-            <title>Source Code Manager - git</title>
+            <title>Source Code Manager - Git</title>
             <para>
-                The Source Code Manager (SCM) is git and it is the obvious mechanism for meeting the 
+                The Source Code Manager (SCM) is Git and it is the obvious mechanism for meeting the 
                 previously mentioned goals.  
-                Not only is it the SCM for kernel.org but git continues to grow in popularity and
+                Not only is it the SCM for kernel.org but Git continues to grow in popularity and
                 supports many different work flows, front-ends and management techniques.
             </para>
             <note><para> 
-                It should be noted that you can use as much, or as little, of what git has to offer 
+                It should be noted that you can use as much, or as little, of what Git has to offer 
                 as is appropriate to your project.
             </para></note>
         </section>
@@ -308,7 +308,7 @@ kernel are:
     <listitem><para>the ability to group patches into named, reusable features</para></listitem>
     <listitem><para>to allow top down control of included features</para></listitem>
     <listitem><para>the binding of kernel configuration to kernel patches/features</para></listitem>
-    <listitem><para>the presentation of a seamless git repository that blends Yocto Project value with the kernel.org history and development</para></listitem>
+    <listitem><para>the presentation of a seamless Git repository that blends Yocto Project value with the kernel.org history and development</para></listitem>
 </itemizedlist>
 </para>
 <!--<para>