diff options
| author |   Michael Jones <michael.jones@matrix-vision.de> | 2010-05-18 05:35:35 +0000 |
|---|---|---|
| committer |   Cliff Brake <cbrake@bec-systems.com> | 2010-05-18 12:02:09 -0400 |
| commit | 8bd97afd2357483726949a34086f9fd8a6bf6f2d (patch) | |
| tree | 67cf17b1d5bbfdd44d2fd04a1f22dab6f29b24c1 /docs/usermanual/chapters/usage.xml | |
| parent | e2a7e630d408fb884d33e7b363572f6b854f7a07 (diff) | |
| download | openembedded-8bd97afd2357483726949a34086f9fd8a6bf6f2d.tar.gz | |
docs/ spelling fixes
Just a few things in the documentation I noticed while reading up on OE. I don't understand why 'git diff' included "\ No newline at end of file" for some of these, or how I could instruct it not to, but I also didn't want to pick apart my patch outside of git.
Signed-off-by: Michael Jones <michael.jones@matrix-vision.de>
Diffstat (limited to 'docs/usermanual/chapters/usage.xml')
| -rw-r--r-- | docs/usermanual/chapters/usage.xml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/usermanual/chapters/usage.xml b/docs/usermanual/chapters/usage.xml index 9f2b7160c7..1563dc3eac 100644 --- a/docs/usermanual/chapters/usage.xml +++ b/docs/usermanual/chapters/usage.xml @@ -5,7 +5,7 @@ <section id="usage_introduction" xreflabel="introduction"> <title>Introduction</title> - <para>If your reading this manual you probably already have some idea of + <para>If you're reading this manual you probably already have some idea of what OpenEmbedded is all about, which is taking a lot of software and creating something that you can run on another device. This involves downloading some source code, compiling it, creating packages (like .deb @@ -13,7 +13,7 @@ device. The difficulties of cross-compiling and the variety of devices which can be supported lead to a lot more complexity in an OpenEmbedded based distribution than you'd find in a typical desktop distribution - (which cross-compiling isn't needed).</para> + (for which cross-compiling isn't needed).</para> <para>A major part of OpenEmbedded deals with compiling source code for various projects. For each project this generally requires the same basic @@ -745,7 +745,7 @@ NOTE: build 200705041709: completed</screen><note> available for other applications to include and link against.</para> <note> - <para>This is different to the <emphasis>install</emphasis> task + <para>This is different from the <emphasis>install</emphasis> task in that this is responsible for making available libraries and headers for use during build on the development host. Therefore it's libraries which normal have to stage things while @@ -853,7 +853,7 @@ NOTE: package perl-5.8.8-r11: task do_listtasks: completed NOTE: package perl-5.8.8: completed $ </screen></para> - <para>If your being observant you'll note that + <para>If you're being observant you'll note that <emphasis>listtasks</emphasis> is in fact a task itself, and that the <emphasis role="bold">-c</emphasis> option to bitbake allows you to explicitly run specific tasks. We'll make use of this in the next section @@ -876,7 +876,7 @@ $ </screen></para> the named recipe only. Note that this ignores any dependencies that are in the recipe, so these must have already been built previously.</para> - <para>Here's a typically example that cleans up the package (using the + <para>Here's a typical example that cleans up the package (using the <emphasis>clean</emphasis> task) and the rebuilds it with debugging output from bitbake enabled:<screen>$ <command>bitbake</command> -b <bb-file> -c clean $ <command>bitbake</command> -b <bb-file> -D</screen></para> |