diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2011-03-17 14:00:27 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-03-18 16:44:34 +0000 |
commit | 45039d008519c13f97d9b195bba4505b3865b5ea (patch) | |
tree | 99fcf189bab76f2eee84f7c4312a2116c7612865 | |
parent | 5062c0e09b5e2c4894ccfe322977fdd432b87e39 (diff) | |
download | openembedded-core-45039d008519c13f97d9b195bba4505b3865b5ea.tar.gz openembedded-core-45039d008519c13f97d9b195bba4505b3865b5ea.tar.bz2 openembedded-core-45039d008519c13f97d9b195bba4505b3865b5ea.zip |
documentation/kernel-manual/kernel-how-to.xml: Spell checked
Performed a spell check and found a couple items.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
-rw-r--r-- | documentation/kernel-manual/kernel-how-to.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/kernel-manual/kernel-how-to.xml b/documentation/kernel-manual/kernel-how-to.xml index 3ca17465c4..79c8526705 100644 --- a/documentation/kernel-manual/kernel-how-to.xml +++ b/documentation/kernel-manual/kernel-how-to.xml @@ -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> |