Poky Reference Manual: Spell check performed.

Found and corrected about 6 or 7 mis-spelled words.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
This commit is contained in:
Scott Rifenbark 2010-11-09 14:10:45 -08:00 committed by Richard Purdie
parent 3f9700a286
commit 731cedfb35
1 changed files with 15 additions and 15 deletions

View File

@ -257,14 +257,14 @@ fi
</section> </section>
<section id='usingpoky-extend-customimage'> <section id='usingpoky-extend-customimage'>
<title>Customising Images</title> <title>Customizing Images</title>
<para> <para>
You can customize Poky images to satisfy particular requirements. You can customize Poky images to satisfy particular requirements.
This section describes several methods and provides guidelines for each. This section describes several methods and provides guidelines for each.
</para> </para>
<section id='usingpoky-extend-customimage-custombb'> <section id='usingpoky-extend-customimage-custombb'>
<title>Customising Images Using Custom .bb Files</title> <title>Customizing Images Using Custom .bb Files</title>
<para> <para>
One way to get additional software into an image is to create a custom image. One way to get additional software into an image is to create a custom image.
The following example shows the form for the two lines you need: The following example shows the form for the two lines you need:
@ -295,7 +295,7 @@ IMAGE_INSTALL += "strace"
</section> </section>
<section id='usingpoky-extend-customimage-customtasks'> <section id='usingpoky-extend-customimage-customtasks'>
<title>Customising Images Using Custom Tasks</title> <title>Customizing Images Using Custom Tasks</title>
<para> <para>
For complex custom images, the best approach is to create a custom task package For complex custom images, the best approach is to create a custom task package
that is used to build the image or images. that is used to build the image or images.
@ -350,7 +350,7 @@ RRECOMMENDS_task-custom-tools = "\
</section> </section>
<section id='usingpoky-extend-customimage-imagefeatures'> <section id='usingpoky-extend-customimage-imagefeatures'>
<title>Customising Images Using Custom IMAGE_FEATURES</title> <title>Customizing Images Using Custom IMAGE_FEATURES</title>
<para> <para>
Ultimately users might want to add extra image "features" as used by Poky with the Ultimately users might want to add extra image "features" as used by Poky with the
<glossterm><link linkend='var-IMAGE_FEATURES'>IMAGE_FEATURES</link></glossterm> <glossterm><link linkend='var-IMAGE_FEATURES'>IMAGE_FEATURES</link></glossterm>
@ -368,9 +368,9 @@ RRECOMMENDS_task-custom-tools = "\
</section> </section>
<section id='usingpoky-extend-customimage-localconf'> <section id='usingpoky-extend-customimage-localconf'>
<title>Customising Images Using local.conf</title> <title>Customizing Images Using local.conf</title>
<para> <para>
It is possible to customise image contents by abusing variables used by distribution It is possible to customize image contents by abusing variables used by distribution
maintainers in local.conf. maintainers in local.conf.
This method only allows the addition of packages and is not recommended. This method only allows the addition of packages and is not recommended.
</para> </para>
@ -497,7 +497,7 @@ COMPATIBLE_MACHINE = '(qemux86|qemumips)'
Reasonable defaults are used in most cases, but if customization is Reasonable defaults are used in most cases, but if customization is
necessary you need to create a <filename>machconfig</filename> file necessary you need to create a <filename>machconfig</filename> file
under <filename>meta/packages/formfactor/files/MACHINENAME/</filename>, under <filename>meta/packages/formfactor/files/MACHINENAME/</filename>,
where <literal>MACHINENAME</literal> is the name for which this infomation where <literal>MACHINENAME</literal> is the name for which this information
applies. applies.
For information about the settings available and the defaults, see For information about the settings available and the defaults, see
<filename>meta/packages/formfactor/files/config</filename>. <filename>meta/packages/formfactor/files/config</filename>.
@ -521,8 +521,8 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
<section id="usingpoky-changes"> <section id="usingpoky-changes">
<title>Making and Maintaining Changes</title> <title>Making and Maintaining Changes</title>
<para> <para>
Because Poky offers extreme configurability and fliexibility, we recognize that people will want Because Poky offers extreme configurability and flexibility, we recognize that people will want
to extend, configure or optimise Poky for their specific uses. to extend, configure or optimize Poky for their specific uses.
To best keep pace with future Poky changes we recommend you make controlled changes to Poky. To best keep pace with future Poky changes we recommend you make controlled changes to Poky.
</para> </para>
<para> <para>
@ -546,7 +546,7 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
The Poky tree includes several additional layers such as meta-emenlow and meta-extras The Poky tree includes several additional layers such as meta-emenlow and meta-extras
that demonstrate this functionality. that demonstrate this functionality.
The meta-emenlow layer is an example layer that by default is enabled. The meta-emenlow layer is an example layer that by default is enabled.
However, the meta-extras repostory is not enabled by default. However, the meta-extras repository is not enabled by default.
It is easy though to enable any layer. It is easy though to enable any layer.
You simply add the layer's path to the You simply add the layer's path to the
<glossterm><link linkend='var-BBLAYERS'>BBLAYERS</link></glossterm> variable in your <glossterm><link linkend='var-BBLAYERS'>BBLAYERS</link></glossterm> variable in your
@ -612,7 +612,7 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
Bitbake can locate where other bbclass and configuration files are applied through Bitbake can locate where other bbclass and configuration files are applied through
the <glossterm><link linkend='var-BBPATH'>BBPATH</link></glossterm> the <glossterm><link linkend='var-BBPATH'>BBPATH</link></glossterm>
environment variable. environment variable.
For these cases, Bitake uses the first file with the matching name found in BBPATH. For these cases, Bitbake uses the first file with the matching name found in BBPATH.
This is similar to the way the PATH variable is used for binaries. This is similar to the way the PATH variable is used for binaries.
We recommend, therefore, that you use unique bbclass and configuration file names in your We recommend, therefore, that you use unique bbclass and configuration file names in your
custom layer. custom layer.
@ -659,7 +659,7 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
<literallayout class='monospaced'> <literallayout class='monospaced'>
bitbake/data.py: Add emit_func() and generate_dependencies() functions bitbake/data.py: Add emit_func() and generate_dependencies() functions
These functions allow generation of dependency data between funcitons and These functions allow generation of dependency data between functions and
variables allowing moves to be made towards generating checksums and allowing variables allowing moves to be made towards generating checksums and allowing
use of the dependency information in other parts of bitbake. use of the dependency information in other parts of bitbake.
@ -711,7 +711,7 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
opkg upgrade</filename> (or similar commands for dpkg/apt or rpm-based systems). opkg upgrade</filename> (or similar commands for dpkg/apt or rpm-based systems).
</para> </para>
<para> <para>
The goal is to ensure Poky has upgradable packages in all cases. The goal is to ensure Poky has upgradeable packages in all cases.
</para> </para>
</section> </section>
@ -775,7 +775,7 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
<section id="usingpoky-changes-updatingimages"> <section id="usingpoky-changes-updatingimages">
<title>Updating Existing Images</title> <title>Updating Existing Images</title>
<para> <para>
Often, rather than reflashing a new image you might wish to install updated Often, rather than re-flashing a new image you might wish to install updated
packages into an existing running system. packages into an existing running system.
You can do this by first sharing the You can do this by first sharing the
<filename class="directory">tmp/deploy/ipk/</filename> directory <filename class="directory">tmp/deploy/ipk/</filename> directory
@ -927,7 +927,7 @@ LIC_FILES_CHKSUM = "file://../license.html;md5=5c94767cedb5d6987c902ac850ded2c6"
As mentioned in the previous section the LIC_FILES_CHKSUM variable lists all the As mentioned in the previous section the LIC_FILES_CHKSUM variable lists all the
important files that contain the license text for the source code. important files that contain the license text for the source code.
Using this variable you can specify the line on which the license text starts and ends Using this variable you can specify the line on which the license text starts and ends
by supplyiing "beginline" and "endline" parameters. by supplying "beginline" and "endline" parameters.
If you do not use the "beginline" parameter then it is assumed that the text begins on the If you do not use the "beginline" parameter then it is assumed that the text begins on the
first line of the file. first line of the file.
Similarly, if you do not use the "endline" parameter it is assumed that the license text Similarly, if you do not use the "endline" parameter it is assumed that the license text