docs/comparing: Fix documentation errors

* Fixed up typos and other errors in the documentation.

Acked-by: Koen Kooi <k-kooi@ti.com>
Signed-off-by: Chase Maupin <chase.maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denis@denix.org>

1 files changed, 9 insertions, 9 deletions

diff --git a/docs/usermanual/chapters/comparing.xml b/docs/usermanual/chapters/comparing.xml
index 1347010977..cfdaa95fbe 100644
--- a/docs/usermanual/chapters/comparing.xml
+++ b/docs/usermanual/chapters/comparing.xml
@@ -5,13 +5,13 @@
   <section id="comparing_buildroot">
     <title>buildroot</title>
 
-    <para>Writing of <application>BitBake</application> recipes is more easy
+    <para>Writing of <application>BitBake</application> recipes is easier
     and more intuitive than writing Makefiles while providing higher
     flexibility. This allows you to tweak specific recipes for your very
-    special needs and to add new recipes very fast. You can build toolchains,
+    special needs and to add new recipes quickly. You can build toolchains,
     Software Distribution Kits (SDKs), complete Distributions or just single
-    packages. The flexibility of OpenEmbedded allows you to reuse the once
-    written recipes for many different purposes. OpenEmbedded provides
+    packages. The flexibility of OpenEmbedded allows you to reuse recipes
+    for many different purposes. OpenEmbedded provides 
     everything buildroot will be able to provide. But in contrast to buildroot
     OpenEmbedded will allow you to achieve what you really want to achieve.
     You can add new package formats, new filesystems, new output formats
@@ -21,11 +21,11 @@
   <section id="comparing_crosstool">
     <title>crosstool</title>
 
-    <para>Crosstool allows to create toolchains for you. It can only create
+    <para>Crosstool allows the creation of toolchains. It can only create
     the initial toolchain for you. It will not compile other needed libraries
-    or applications for you, it will not be able to track dependencies or to
+    or applications for you, it will not be able to track dependencies or
     package them properly. OpenEmbedded supports all configurations crosstool
-    supports. You can start to create toolchains with OpenEmbedded, then as
+    supports. You can start by creating toolchains with OpenEmbedded, then as
     your needs grow create a more complete SDK from already present base
     libraries and applications and if you recognize you need to have packages
     for the target you have them almost built already.</para>
@@ -38,7 +38,7 @@
     cross-compiling is hard itself but many people misuse the buildsystem they
     use to build their software. This will lead to a variety of issues you can
     run into. This can be failing tests on configuration because of executing
-    cross compiled binaries or crashes at run-time due wrong sizes of basic
+    cross compiled binaries or crashes at run-time due to wrong sizes of basic
     types. When utilizing OpenEmbedded you avoid searching for patches at many
     different places and will be able to get things done more quickly.
     <application>OpenEmbedded</application> allows you to choose from a pool
@@ -48,4 +48,4 @@
     output formats and filesystems. This allows you to create complete and
     specialized distributions easily.</para>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>