summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2011-08-23 13:06:37 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-08-24 19:49:35 -0700
commite4e0d026c17bf628d18fb8ee9e6c59498c37e57c (patch)
tree33405033f29d4550820a920c04919c8588ca3cab /documentation
parent82fd0556c2a9c6c6b319b9fd44ba26124dd052ab (diff)
downloadast2050-yocto-poky-e4e0d026c17bf628d18fb8ee9e6c59498c37e57c.zip
ast2050-yocto-poky-e4e0d026c17bf628d18fb8ee9e6c59498c37e57c.tar.gz
documentation: typo, spelling & minor grammar fixes
(From yocto-docs rev: a5b069b04979a566b08415cf27af2ad6abf90f2f) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/bsp-guide/bsp.xml4
-rw-r--r--documentation/poky-ref-manual/development.xml2
-rw-r--r--documentation/poky-ref-manual/faq.xml10
-rw-r--r--documentation/poky-ref-manual/ref-bitbake.xml4
-rw-r--r--documentation/poky-ref-manual/ref-classes.xml6
-rw-r--r--documentation/poky-ref-manual/ref-images.xml2
-rw-r--r--documentation/poky-ref-manual/ref-structure.xml8
-rw-r--r--documentation/poky-ref-manual/ref-variables.xml10
-rw-r--r--documentation/poky-ref-manual/resources.xml2
-rw-r--r--documentation/poky-ref-manual/usingpoky.xml2
10 files changed, 25 insertions, 25 deletions
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 492a795..7f793c8 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -131,7 +131,7 @@
meta-crownbay/conf/machine/crownbay.conf
meta-crownbay/recipes-bsp/formfactor/formfactor/crownbay/machconfig
meta-crownbay/recipes-bsp/formfactor/formfactor_0.0.bbappend
- meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay/xcorg.conf
+ meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay/xorg.conf
meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin/.gitignore
meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin_1.7.99.2.bb
@@ -355,7 +355,7 @@
All files that are needed for the BSP to support a display are kept here.
For example, in the Crownbay BSP several display support files exist:
<literallayout class='monospaced'>
- meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay/xcorg.conf
+ meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config/crownbay/xorg.conf
meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin/.gitignore
meta-crownbay/recipes-graphics/xorg-xserver/xserver-xf86-emgd-bin_1.7.99.2.bb
diff --git a/documentation/poky-ref-manual/development.xml b/documentation/poky-ref-manual/development.xml
index 53e6904..15f40fe 100644
--- a/documentation/poky-ref-manual/development.xml
+++ b/documentation/poky-ref-manual/development.xml
@@ -292,7 +292,7 @@
<para>It is worth remembering that when using <filename>devshell</filename>
you need to use the full compiler name such as <filename>arm-poky-linux-gnueabi-gcc</filename>
instead of just using <filename>gcc</filename>.
- The same applies to other applications such as <filename>bintuils</filename>,
+ The same applies to other applications such as <filename>binutils</filename>,
<filename>libtool</filename> and so forth.
The Yocto Project has setup environment variables such as <filename>CC</filename>
to assist applications, such as <filename>make</filename> to find the correct tools.</para>
diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml
index 0982d9d..6a1f741 100644
--- a/documentation/poky-ref-manual/faq.xml
+++ b/documentation/poky-ref-manual/faq.xml
@@ -124,7 +124,7 @@
</question>
<answer>
<para>
- The <ulink url='http://vernier.com/labquest/'>Vernier Labquest</ulink> is using Poky (for more about the Labquest see the case study at OpenedHand). There are a number of pre-production devices using Poky and we will announce those as soon as they are released.
+ The <ulink url='http://vernier.com/labquest/'>Vernier LabQuest</ulink> is using Poky (for more about the LabQuest see the case study at OpenedHand). There are a number of pre-production devices using Poky and we will announce those as soon as they are released.
</para>
</answer>
</qandaentry>
@@ -299,7 +299,7 @@
<qandaentry>
<question>
<para>
- I'm using Ubuntu Intrepid and am seeing build failures. Whats wrong?
+ I'm using Ubuntu Intrepid and am seeing build failures. What’s wrong?
</para>
</question>
<answer>
@@ -315,7 +315,7 @@
<qandaentry>
<question>
<para>
- Whats the difference between foo and foo-native?
+ What’s the difference between foo and foo-native?
</para>
</question>
<answer>
@@ -473,7 +473,7 @@
<answer>
<para>
The way Poky obtains source code is highly configurable.
- You can setup Poky to get source code in most environmnents if
+ You can setup Poky to get source code in most environments if
HTTP transport is available.
</para>
<para>
@@ -501,7 +501,7 @@
<para>
These changes cause Poky to intercept GIT, FTP, HTTP, and HTTPS
requests and direct them to the <filename>http://</filename> sources mirror.
- You can use <filename>file://</filename> urls to point to local directories
+ You can use <filename>file://</filename> URLs to point to local directories
or network shares as well.
</para>
<para>
diff --git a/documentation/poky-ref-manual/ref-bitbake.xml b/documentation/poky-ref-manual/ref-bitbake.xml
index f081610..b11bd5a 100644
--- a/documentation/poky-ref-manual/ref-bitbake.xml
+++ b/documentation/poky-ref-manual/ref-bitbake.xml
@@ -70,7 +70,7 @@
The <filename>base.bbclass</filename> file is always included.
Other classes that are specified in the configuration using the
<filename><link linkend='var-INHERIT'>INHERIT</link></filename>
- variable are also inculded.
+ variable are also included.
Class files are searched for in a <filename>classes</filename> subdirectory
under the paths in <filename>BBPATH</filename> in the same way as
configuration files.
@@ -128,7 +128,7 @@
<para>
Sometimes a target might have multiple providers.
A common example is "virtual/kernel", which is provided by each kernel package.
- Each machine often elects the best kernel provider by using a line similar to the
+ Each machine often selects the best kernel provider by using a line similar to the
following in the machine configuration file:
</para>
diff --git a/documentation/poky-ref-manual/ref-classes.xml b/documentation/poky-ref-manual/ref-classes.xml
index d054df1..905538d 100644
--- a/documentation/poky-ref-manual/ref-classes.xml
+++ b/documentation/poky-ref-manual/ref-classes.xml
@@ -81,7 +81,7 @@
<title>Alternatives - <filename>update-alternatives.bbclass</filename></title>
<para>
- Several programs can fulfill the same or similar function and be installed with the same name.
+ Several programs can fulfil the same or similar function and be installed with the same name.
For example, the <filename>ar</filename> command is available from the
<filename>busybox</filename>, <filename>binutils</filename> and
<filename>elfutils</filename> packages.
@@ -211,7 +211,7 @@
Recipes for Perl modules are simple.
These recipes usually only need to point to the source's archive and then inherit the
proper <filename>.bbclass</filename> file.
- Building is split into two methods dependling on which method the module authors used.
+ Building is split into two methods depending on which method the module authors used.
</para>
<para>
@@ -360,7 +360,7 @@
used to provide cached test results so these tests can be skipped over but
still make the correct values available.
The <filename><link linkend='structure-meta-site'>meta/site directory</link></filename>
- contains test results sorted into different categories such as architecture, endianess, and
+ contains test results sorted into different categories such as architecture, endianness, and
the libc used.
Site information provides a list of files containing data relevant to
the current build in the
diff --git a/documentation/poky-ref-manual/ref-images.xml b/documentation/poky-ref-manual/ref-images.xml
index 19a2a37..c67a01f 100644
--- a/documentation/poky-ref-manual/ref-images.xml
+++ b/documentation/poky-ref-manual/ref-images.xml
@@ -86,7 +86,7 @@
from a USB device or CD as is.</para></listitem>
<listitem><para><emphasis><filename>core-image-clutter</filename>:</emphasis>
An image with support for the Open GL-based toolkit Clutter, which enables development of
- rich and animated graphical user interaces.</para></listitem>
+ rich and animated graphical user interfaces.</para></listitem>
<listitem><para><emphasis><filename>core-image-sato</filename>:</emphasis>
An image with Sato support, a mobile environment and visual style that works well
with mobile devices.
diff --git a/documentation/poky-ref-manual/ref-structure.xml b/documentation/poky-ref-manual/ref-structure.xml
index 3e3b794..be81faf 100644
--- a/documentation/poky-ref-manual/ref-structure.xml
+++ b/documentation/poky-ref-manual/ref-structure.xml
@@ -173,7 +173,7 @@
<title><filename>build/pseudodone</filename></title>
<para>
- This tag file indicates that the intitial pseudo binary was created.
+ This tag file indicates that the initial pseudo binary was created.
The file is built the first time BitBake is invoked.
</para>
</section>
@@ -468,7 +468,7 @@
Any distribution-specific configuration is controlled from this directory.
The Yocto Project only contains the Yocto Project distribution so
<filename>defaultsetup.conf</filename> is the main file here.
- This directory includes the versions and SRCDATES for applications that are configured here.
+ This directory includes the versions and SRCDATEs for applications that are configured here.
An example of an alternative configuration is <filename>poky-bleeding.conf</filename>
although this file mainly inherits its configuration from the Yocto Project itself.
</para>
@@ -479,7 +479,7 @@
<para>
This directory contains anything linking to specific hardware or hardware configuration information
- such as "uboot" and "grub".
+ such as "u-boot" and "grub".
</para>
</section>
@@ -575,7 +575,7 @@
<para>
This directory contains recipes that used by other recipes, but that are not directly
- included in images (i.e. depenendies of other recipes).
+ included in images (i.e. dependencies of other recipes).
</para>
</section>
diff --git a/documentation/poky-ref-manual/ref-variables.xml b/documentation/poky-ref-manual/ref-variables.xml
index 40ef56d..e60f2ae 100644
--- a/documentation/poky-ref-manual/ref-variables.xml
+++ b/documentation/poky-ref-manual/ref-variables.xml
@@ -76,7 +76,7 @@
<glossdef>
<para>Identifies layer-specific <filename>.bbfiles</filename>, which contain recipes
used by BitBake to build software.
- The Variable is appended with a layer name.</para>
+ The variable is appended with a layer name.</para>
</glossdef>
</glossentry>
@@ -322,7 +322,7 @@
<filename><link linkend='var-IMAGE_FEATURES'>IMAGE_FEATURES</link></filename>
variable generally configured in image recipes.
You can use this variable to add more features in addition to those.
- Here are some exmaples of features you can add:</para>
+ Here are some examples of features you can add:</para>
<literallayout class='monospaced'>
"dbg-pkgs" - Adds -dbg packages for all installed packages
including symbol information for debugging and
@@ -647,7 +647,7 @@
<glossentry id='var-PACKAGE_DESCRIPTION'><glossterm>PACKAGE_DESCRIPTION</glossterm>
<glossdef>
- <para>The long form description of the binary package for packaging sytems such as
+ <para>The long form description of the binary package for packaging systems such as
<filename>ipkg</filename>, <filename>rpm</filename> or <filename>debian</filename>.
By default, this variable inherits <filename>DESCRIPTION</filename>.</para>
</glossdef>
@@ -664,7 +664,7 @@
<glossentry id='var-PACKAGE_SUMMARY'><glossterm>PACKAGE_SUMMARY</glossterm>
<glossdef>
<para>The short (72 character limit suggested) summary of the binary
- package for packaging sytems such as <filename>ipkg</filename>,
+ package for packaging systems such as <filename>ipkg</filename>,
<filename>rpm</filename> or <filename>debian</filename>.
By default, this variable inherits <filename>DESCRIPTION</filename>.</para>
</glossdef>
@@ -1026,7 +1026,7 @@
<glossentry id='var-TERMCMD'><glossterm>TERMCMD</glossterm>
<glossdef>
<para>
- This command is used by BitBake to lauch a terminal window with a
+ This command is used by BitBake to launch a terminal window with a
shell.
The shell is unspecified so the user's default shell is used.
By default, the variable is set to "gnome-terminal" but it can
diff --git a/documentation/poky-ref-manual/resources.xml b/documentation/poky-ref-manual/resources.xml
index eae37fe..69e998b 100644
--- a/documentation/poky-ref-manual/resources.xml
+++ b/documentation/poky-ref-manual/resources.xml
@@ -72,7 +72,7 @@
<itemizedlist>
<listitem><para>
<ulink url='http://yoctoproject.org'>The Yocto Project website</ulink> - The home site
- for Yocto Project.
+ for the Yocto Project.
</para></listitem>
<!-- <listitem><para>
<ulink url='http://pokylinux.org'>The Poky website</ulink> - The home site
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml
index d26b2b7..4abe93f 100644
--- a/documentation/poky-ref-manual/usingpoky.xml
+++ b/documentation/poky-ref-manual/usingpoky.xml
@@ -468,7 +468,7 @@
Here are some other tips that you might find useful:
<itemizedlist>
<listitem><para>When adding new packages, it is worth watching for
- undesireable items making their way into compiler command lines.
+ undesirable items making their way into compiler command lines.
For example, you do not want references to local system files like
<filename>/usr/lib/</filename> or <filename>/usr/include/</filename>.
</para></listitem>
OpenPOWER on IntegriCloud