diff options
author | Andrzej Zaborowski <balrog@zabor.org> | 2008-12-05 13:07:12 +0100 |
---|---|---|
committer | Andrzej Zaborowski <balrog@zabor.org> | 2008-12-05 13:07:12 +0100 |
commit | 73b22007249f98c96c425ef8379762b425dc2d61 (patch) | |
tree | e2c5c6b1bf22fd1bb356d9e0be9963d93ef17dbb /handbook/extendpoky.xml | |
parent | bcb58a0cd0783b67de316100f0d21fa8e33016a0 (diff) | |
download | openembedded-core-73b22007249f98c96c425ef8379762b425dc2d61.tar.gz openembedded-core-73b22007249f98c96c425ef8379762b425dc2d61.tar.bz2 openembedded-core-73b22007249f98c96c425ef8379762b425dc2d61.tar.xz openembedded-core-73b22007249f98c96c425ef8379762b425dc2d61.zip |
handbook: Correct a bunch of misc typos.
Diffstat (limited to 'handbook/extendpoky.xml')
-rw-r--r-- | handbook/extendpoky.xml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/handbook/extendpoky.xml b/handbook/extendpoky.xml index cc0dc1fd2..f259d2ef0 100644 --- a/handbook/extendpoky.xml +++ b/handbook/extendpoky.xml @@ -215,7 +215,7 @@ pkg_postinst_PACKAGENAME () { <para> Sometimes it is necessary that the execution of a post-installation script is delayed until the first boot, because the script - needs to be executed the device itself. To delay script execution + needs to be executed on the device itself. To delay script execution until boot time, the post-installation function should have the following structure: </para> @@ -268,7 +268,7 @@ inherit poky-image <para> By creating a custom image, a developer has total control - over the contents of the image. It is important use + over the contents of the image. It is important to use the correct names of packages in the <glossterm><link linkend='var-IMAGE_INSTALL'>IMAGE_INSTALL</link></glossterm> variable. The names must be in @@ -295,11 +295,11 @@ IMAGE_INSTALL += "strace" <title>Customising Images through custom tasks</title> <para> - For for complex custom images, the best approach is to create a custom - task package which is them used to build the image (or images). A good + For complex custom images, the best approach is to create a custom + task package which is then used to build the image (or images). A good example of a tasks package is <filename>meta/packages/tasks/task-poky.bb </filename>. The <glossterm><link linkend='var-PACKAGES'>PACKAGES</link></glossterm> - variable lists the task packages to build (along with the complimentary + variable lists the task packages to build (along with the complementary -dbg and -dev packages). For each package added, <glossterm><link linkend='var-PACKAGES'>RDEPENDS</link></glossterm> and <glossterm><link linkend='var-PACKAGES'>RRECOMMENDS</link></glossterm> |