documentation/kernel-manual/kernel-how-to.xml: Edits to "Tree Construction" (From yocto-docs rev: 601e0fd1bb00c433716170a124b3ca32ca2cdcad)

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

1 files changed, 4 insertions, 4 deletions

diff --git a/documentation/kernel-manual/kernel-how-to.xml b/documentation/kernel-manual/kernel-how-to.xml
index 0cb715404b..a7ae4c2ef8 100644
--- a/documentation/kernel-manual/kernel-how-to.xml
+++ b/documentation/kernel-manual/kernel-how-to.xml
@@ -49,7 +49,7 @@
             particular kernel branch. 
             Instead, you should use git directly to discover the changes
             in a branch.
-            Using git is a efficient and flexible way to inspect changes to the kernel.  
+            Using git is an efficient and flexible way to inspect changes to the kernel.  
             For examples showing how to use git to inspect kernel commits, see the following sections
             in this chapter.
         </para>
@@ -90,8 +90,8 @@
             step #3</para></listitem>
 
             <listitem><para>The script is executed, and a meta-series is produced. 
-            The meta-series is a description of all the branches, tags, patches and configuration that
-            needs to be applied to the base git repository to completely create the
+            The meta-series is a description of all the branches, tags, patches and configurations that
+            need to be applied to the base git repository to completely create the
             BSP source (build) branch.</para></listitem>
 
             <listitem><para>The base repository is cloned, and the actions
@@ -113,7 +113,7 @@
             official Yocto Project kernel repositories is the combination of all
             supported boards and configurations.</para>
   
-            <para>This technique is flexible and allows the seamless blending of an immutable
+            <para>This technique is flexible and allows for seamless blending of an immutable
             history with additional deployment specific patches. 
             Any additions to the kernel become an integrated part of the branches.
         </para></note>