]> code.ossystems Code Review - openembedded-core.git/commitdiff
documentation/kernel-manual/kernel-how-to.xml: Spell checked
authorScott Rifenbark <scott.m.rifenbark@intel.com>
Thu, 17 Mar 2011 20:00:27 +0000 (14:00 -0600)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Fri, 18 Mar 2011 16:44:34 +0000 (16:44 +0000)
Performed a spell check and found a couple items.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
documentation/kernel-manual/kernel-how-to.xml

index 3ca17465c42a8332a1da306c2d45de1e30c3deb8..79c8526705d22b9680df7ae90d118604823a61d5 100644 (file)
@@ -475,7 +475,7 @@ repository.
                 <para>
                     You can use many other comparisons to isolate BSP changes.
                     For example, you can compare against kernel.org tags (e.g. v2.6.27.18, etc), or
-                    you can compare agains subsystems (e.g. git whatchanged mm).
+                    you can compare against subsystems (e.g. git whatchanged mm).
                 </para>
             </section>
         </section>
@@ -600,7 +600,7 @@ repository.
                 <para>
                     Distributed development with git is possible when you use a universally 
                     agreed-upon unique commit identifier (set by the creator of the commit) that maps to a
-                    specific changeset with a specific parent.  
+                    specific change set with a specific parent.  
                     This identifier is created for you when
                     you create a commit, and is re-created when you amend, alter or re-apply
                     a commit.  
@@ -1059,7 +1059,7 @@ That's it. Configure and build.
                         (linux-yocto is the kernel listed in
                         <filename>meta-emenlow/conf/machine/emenlow.conf</filename>)</para></listitem>.
                         <listitem><para>Add a new entry in the <filename>build/conf/bblayers.conf</filename> 
-                        so the new layer can be found by Bitbake.</para></listitem>
+                        so the new layer can be found by BitBake.</para></listitem>
                     </itemizedlist>
                 </para></listitem>