[oe] [PATCH 2/7] Usermanual/comparing: Fix documentation errors

[Stefan Schmidt]

On Wed, 2010-05-26 at 08:17, Koen Kooi wrote:
> From: Chase Maupin <chase.maupin at ti.com>
> 
> * Fixed up typos and other errors in the documentation.
> 
> Signed-off-by: Chase Maupin <chase.maupin at ti.com>
> Signed-off-by: Koen Kooi <k-kooi at ti.com>

Non-native speaker ack:
Acked-by: Stefan Schmidt <stefan at datenfreihafen.org>

> ---
>  docs/usermanual/chapters/comparing.xml |   18 +++++++++---------
>  1 files changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/docs/usermanual/chapters/comparing.xml b/docs/usermanual/chapters/comparing.xml
> index 1347010..cfdaa95 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>
> -- 
> 1.7.0
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel