Documentation: poky-ref-manual - Removed all trailing whitespace.

(From yocto-docs rev: 564a28c2501034ea7e2eb16afc43dfaf931b6f6f)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 130 insertions, 130 deletions

diff --git a/documentation/poky-ref-manual/ref-structure.xml b/documentation/poky-ref-manual/ref-structure.xml
index 166907ceef..673b05a52b 100644
--- a/documentation/poky-ref-manual/ref-structure.xml
+++ b/documentation/poky-ref-manual/ref-structure.xml
@@ -9,7 +9,7 @@
 <para>
     The <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink> consists of several components.
     Understanding them and knowing where they are located is key to using the Yocto Project well.
-    This chapter describes the Source Directory and gives information about the various 
+    This chapter describes the Source Directory and gives information about the various
     files and directories.
 </para>
 
@@ -35,26 +35,26 @@
         <para>
             The <ulink url='source-directory'>Source Directory</ulink>
             includes a copy of BitBake for ease of use.
-            The copy usually matches the current stable BitBake release from the BitBake project. 
-            BitBake, a metadata interpreter, reads the Yocto Project metadata and runs the tasks 
-            defined by that data. 
+            The copy usually matches the current stable BitBake release from the BitBake project.
+            BitBake, a metadata interpreter, reads the Yocto Project metadata and runs the tasks
+            defined by that data.
             Failures are usually from the metadata and not from BitBake itself.
             Consequently, most users do not need to worry about BitBake.
         </para>
 
         <para>
-            When you run the <filename>bitbake</filename> command, the wrapper script in 
-            <filename>scripts/</filename> is executed to run the main BitBake executable, 
+            When you run the <filename>bitbake</filename> command, the wrapper script in
+            <filename>scripts/</filename> is executed to run the main BitBake executable,
             which resides in the <filename>bitbake/bin/</filename> directory.
-            Sourcing the <link linkend="structure-core-script">&OE_INIT_FILE;</link> 
+            Sourcing the <link linkend="structure-core-script">&OE_INIT_FILE;</link>
             script places the <filename>scripts</filename> and <filename>bitbake/bin</filename>
-            directories (in that order) into the shell's <filename>PATH</filename> environment 
+            directories (in that order) into the shell's <filename>PATH</filename> environment
             variable.
         </para>
 
         <para>
-            For more information on BitBake, see the BitBake documentation 
-            inculded in the <filename>bitbake/doc/manual</filename> directory of the 
+            For more information on BitBake, see the BitBake documentation
+            inculded in the <filename>bitbake/doc/manual</filename> directory of the
             <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
         </para>
     </section>
@@ -63,21 +63,21 @@
         <title><filename>build/</filename></title>
 
         <para>
-            This directory contains user configuration files and the output 
-            generated by the OpenEmbedded build system in its standard configuration where 
+            This directory contains user configuration files and the output
+            generated by the OpenEmbedded build system in its standard configuration where
             the source tree is combined with the output.
             The <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
             is created initially when you <filename>source</filename>
             the OpenEmbedded build environment setup script <filename>&OE_INIT_FILE;</filename>.
         </para>
 
-        <para> 
-            It is also possible to place output and configuration 
-            files in a directory separate from the 
+        <para>
+            It is also possible to place output and configuration
+            files in a directory separate from the
             <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>
             by providing a directory name when you <filename>source</filename>
             the setup script.
-            For information on separating output from your local Source Directory files, see <link 
+            For information on separating output from your local Source Directory files, see <link
             linkend='structure-core-script'>&OE_INIT_FILE;</link>.
         </para>
     </section>
@@ -88,9 +88,9 @@
         <para>
             This directory holds the source for the Yocto Project documentation
             as well as templates and tools that allow you to generate PDF and HTML
-            versions of the manuals.  
-            Each manual is contained in a sub-folder.  
-            For example, the files for this manual reside in 
+            versions of the manuals.
+            Each manual is contained in a sub-folder.
+            For example, the files for this manual reside in
             <filename>poky-ref-manual</filename>.
         </para>
     </section>
@@ -99,7 +99,7 @@
         <title><filename>meta/</filename></title>
 
         <para>
-            This directory contains the OpenEmbedded Core metadata. 
+            This directory contains the OpenEmbedded Core metadata.
             The directory holds recipes, common classes, and machine
             configuration for emulated targets (qemux86, qemuarm,
             and so on.)
@@ -138,7 +138,7 @@
         <title><filename>meta-skeleton/</filename></title>
 
         <para>
-            This directory contains template recipes for BSP and kernel development. 
+            This directory contains template recipes for BSP and kernel development.
         </para>
     </section>
 
@@ -146,7 +146,7 @@
         <title><filename>scripts/</filename></title>
 
         <para>
-            This directory contains various integration scripts that implement 
+            This directory contains various integration scripts that implement
             extra functionality in the Yocto Project environment (e.g. QEMU scripts).
             The <link linkend="structure-core-script">&OE_INIT_FILE;</link> script appends this
             directory to the shell's <filename>PATH</filename> environment variable.
@@ -154,7 +154,7 @@
 
         <para>
             The <filename>scripts</filename> directory has useful scripts that assist contributing
-            back to the Yocto Project, such as <filename>create_pull_request</filename> and 
+            back to the Yocto Project, such as <filename>create_pull_request</filename> and
             <filename>send_pull_request</filename>.
         </para>
     </section>
@@ -163,23 +163,23 @@
         <title><filename>&OE_INIT_FILE;</filename></title>
 
         <para>
-            This script sets up the OpenEmbedded build environment. 
+            This script sets up the OpenEmbedded build environment.
             Running this script with the <filename>source</filename> command in
             a shell makes changes to <filename>PATH</filename> and sets other core BitBake variables based on the
-            current working directory. 
+            current working directory.
             You need to run this script before running BitBake commands.
-            The script uses other scripts within the <filename>scripts</filename> directory to do 
+            The script uses other scripts within the <filename>scripts</filename> directory to do
             the bulk of the work.
         </para>
 
         <para>
-            By default, running this script without a Build Directory argument creates the 
-            <filename>build</filename> directory. 
+            By default, running this script without a Build Directory argument creates the
+            <filename>build</filename> directory.
             If you provide a Build Directory argument when you <filename>source</filename>
-            the script, you direct OpenEmbedded build system to create a 
+            the script, you direct OpenEmbedded build system to create a
             <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> of your choice.
-            For example, the following command creates a Build Directory named 
-            <filename>mybuilds</filename> that is outside of the 
+            For example, the following command creates a Build Directory named
+            <filename>mybuilds</filename> that is outside of the
             <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>:
             <literallayout class='monospaced'>
      $ source &OE_INIT_FILE; ~/mybuilds
@@ -189,7 +189,7 @@
                 contain spaces.
                 If you attempt to run the <filename>&OE_INIT_FILE;</filename> script
                 from a Source Directory that contains spaces in either the filenames
-                or directory names, the script returns an error indicating no such 
+                or directory names, the script returns an error indicating no such
                 file or directory.
                 Be sure to use a Source Directory free of names containing spaces.
             </note>
@@ -200,7 +200,7 @@
         <title><filename>LICENSE, README, and README.hardware</filename></title>
 
         <para>
-            These files are standard top-level files. 
+            These files are standard top-level files.
         </para>
     </section>
 </section>
@@ -212,8 +212,8 @@
         <title><filename>build/pseudodone</filename></title>
 
         <para>
-            This tag file indicates that the initial pseudo binary was created. 
-            The file is built the first time BitBake is invoked. 
+            This tag file indicates that the initial pseudo binary was created.
+            The file is built the first time BitBake is invoked.
         </para>
     </section>
 
@@ -221,24 +221,24 @@
         <title><filename>build/conf/local.conf</filename></title>
 
         <para>
-            This file contains all the local user configuration for your build environment. 
-            If there is no <filename>local.conf</filename> present, it is created from 
-            <filename>local.conf.sample</filename>. 
-            The <filename>local.conf</filename> file contains documentation on the various configuration options.  
-            Any variable set here overrides any variable set elsewhere within the environment unless 
-            that variable is hard-coded within a file (e.g. by using '=' instead of '?='). 
-            Some variables are hard-coded for various reasons but these variables are 
+            This file contains all the local user configuration for your build environment.
+            If there is no <filename>local.conf</filename> present, it is created from
+            <filename>local.conf.sample</filename>.
+            The <filename>local.conf</filename> file contains documentation on the various configuration options.
+            Any variable set here overrides any variable set elsewhere within the environment unless
+            that variable is hard-coded within a file (e.g. by using '=' instead of '?=').
+            Some variables are hard-coded for various reasons but these variables are
             relatively rare.
         </para>
 
         <para>
-            Edit this file to set the <filename><link linkend='var-MACHINE'>MACHINE</link></filename> 
-            for which you want to build, which package types you wish to use 
-            (<link linkend='var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></link>), 
+            Edit this file to set the <filename><link linkend='var-MACHINE'>MACHINE</link></filename>
+            for which you want to build, which package types you wish to use
+            (<link linkend='var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></link>),
             where you want to downloaded files
-            (<filename><link linkend='var-DL_DIR'>DL_DIR</link></filename>), 
-            and how you want your host machine to use resources 
-            (<link linkend='var-BB_NUMBER_THREADS'><filename>BB_NUMBER_THREADS</filename></link> and 
+            (<filename><link linkend='var-DL_DIR'>DL_DIR</link></filename>),
+            and how you want your host machine to use resources
+            (<link linkend='var-BB_NUMBER_THREADS'><filename>BB_NUMBER_THREADS</filename></link> and
             <link linkend='var-PARALLEL_MAKE'><filename>PARALLEL_MAKE</filename></link>).
         </para>
     </section>
@@ -248,8 +248,8 @@
 
         <para>
             This file defines layers, which are directory trees, traversed (or walked) by BitBake.
-            If <filename>bblayers.conf</filename> 
-            is not present, it is created from <filename>bblayers.conf.sample</filename> when 
+            If <filename>bblayers.conf</filename>
+            is not present, it is created from <filename>bblayers.conf.sample</filename> when
             you <filename>source</filename> the environment setup script.
         </para>
 
@@ -276,7 +276,7 @@
 
         <para>
             This directory is used for the upstream source tarballs.
-            The directory can be reused by multiple builds or moved to another location. 
+            The directory can be reused by multiple builds or moved to another location.
             You can control the location of this directory through the
             <filename><link linkend='var-DL_DIR'>DL_DIR</link></filename> variable.
         </para>
@@ -287,7 +287,7 @@
 
         <para>
             This directory is used for the shared state cache.
-            The directory can be reused by multiple builds or moved to another location. 
+            The directory can be reused by multiple builds or moved to another location.
             You can control the location of this directory through the
             <filename><link linkend='var-SSTATE_DIR'>SSTATE_DIR</link></filename> variable.
         </para>
@@ -298,9 +298,9 @@
 
         <para>
             This directory receives all the OpenEmbedded build system's output.
-            BitBake creates this directory if it does not exist. 
-            As a last resort, to clean up a build and start it from scratch (other than the downloads), 
-            you can remove everything in the <filename>tmp</filename> directory or get rid of the 
+            BitBake creates this directory if it does not exist.
+            As a last resort, to clean up a build and start it from scratch (other than the downloads),
+            you can remove everything in the <filename>tmp</filename> directory or get rid of the
             directory completely.
             If you do, you should also completely remove the <filename>build/sstate-cache</filename>
             directory as well.
@@ -320,7 +320,7 @@
 
         <para>
             When BitBake parses the metadata, it creates a cache file of the result that can
-            be used when subsequently running commands. 
+            be used when subsequently running commands.
             These results are stored here on a per-machine basis.
         </para>
     </section>
@@ -337,7 +337,7 @@
         <title><filename>build/tmp/deploy/deb/</filename></title>
 
         <para>
-            This directory receives any <filename>.deb</filename> packages produced by 
+            This directory receives any <filename>.deb</filename> packages produced by
             the build process.
             The packages are sorted into feeds for different architecture types.
         </para>
@@ -347,8 +347,8 @@
         <title><filename>build/tmp/deploy/rpm/</filename></title>
 
         <para>
-            This directory receives any <filename>.rpm</filename> packages produced by 
-            the build process.  
+            This directory receives any <filename>.rpm</filename> packages produced by
+            the build process.
             The packages are sorted into feeds for different architecture types.
         </para>
     </section>
@@ -368,16 +368,16 @@
         <title><filename>build/tmp/deploy/images/</filename></title>
 
         <para>
-            This directory receives complete filesystem images. 
+            This directory receives complete filesystem images.
             If you want to flash the resulting image from a build onto a device, look here for the image.
         </para>
 
         <para>
-            Be careful when deleting files in this directory. 
-            You can safely delete old images from this directory (e.g. 
+            Be careful when deleting files in this directory.
+            You can safely delete old images from this directory (e.g.
             <filename>core-image-*</filename>, <filename>hob-image-*</filename>,
-            etc.). 
-            However, the kernel (<filename>*zImage*</filename>, <filename>*uImage*</filename>, etc.), 
+            etc.).
+            However, the kernel (<filename>*zImage*</filename>, <filename>*uImage*</filename>, etc.),
             bootloader and other supplementary files might be deployed here prior to building an
             image.
             Because these files, however, are not directly produced from the image, if you
@@ -385,8 +385,8 @@
         </para>
 
         <para>
-            If you do accidentally delete files here, you will need to force them to be 
-            re-created. 
+            If you do accidentally delete files here, you will need to force them to be
+            re-created.
             In order to do that, you will need to know the target that produced them.
             For example, these commands rebuild and re-create the kernel files:
             <literallayout class='monospaced'>
@@ -400,7 +400,7 @@
         <title><filename>build/tmp/deploy/ipk/</filename></title>
 
         <para>
-            This directory receives <filename>.ipk</filename> packages produced by 
+            This directory receives <filename>.ipk</filename> packages produced by
             the build process.</para>
     </section>
 
@@ -408,9 +408,9 @@
         <title><filename>build/tmp/sysroots/</filename></title>
 
         <para>
-            This directory contains shared header files and libraries as well as other shared 
-            data.  
-            Packages that need to share output with other packages do so within this directory. 
+            This directory contains shared header files and libraries as well as other shared
+            data.
+            Packages that need to share output with other packages do so within this directory.
             The directory is subdivided by architecture so multiple builds can run within
             the one Build Directory.
         </para>
@@ -420,9 +420,9 @@
         <title><filename>build/tmp/stamps/</filename></title>
 
         <para>
-            This directory holds information that that BitBake uses for accounting purposes 
+            This directory holds information that that BitBake uses for accounting purposes
             to track what tasks have run and when they have run.
-            The directory is sub-divided by architecture. 
+            The directory is sub-divided by architecture.
             The files in the directory are empty of data.
             However, BitBake uses the filenames and timestamps for tracking purposes.
         </para>
@@ -432,9 +432,9 @@
         <title><filename>build/tmp/log/</filename></title>
 
         <para>
-            This directory contains general logs that are not otherwise placed using the 
+            This directory contains general logs that are not otherwise placed using the
             package's <filename><link linkend='var-WORKDIR'>WORKDIR</link></filename>.
-            Examples of logs are the output from the <filename>check_pkg</filename> or 
+            Examples of logs are the output from the <filename>check_pkg</filename> or
             <filename>distro_check</filename> tasks.
             Running a build does not necessarily mean this directory is created.
         </para>
@@ -444,7 +444,7 @@
         <title><filename>build/tmp/pkgdata/</filename></title>
 
         <para>
-            This directory contains intermediate packaging data that is used later in the packaging process. 
+            This directory contains intermediate packaging data that is used later in the packaging process.
             For more information, see the "<link linkend='ref-classes-package'>Packaging - package*.bbclass</link>" section.
         </para>
     </section>
@@ -453,7 +453,7 @@
         <title><filename>build/tmp/work/</filename></title>
 
         <para>
-            This directory contains architecture-specific work sub-directories for packages built by BitBake. 
+            This directory contains architecture-specific work sub-directories for packages built by BitBake.
             All tasks execute from a work directory.
             For example, the source for a particular package is unpacked, patched, configured and compiled all
             within its own work directory.
@@ -462,31 +462,31 @@
         </para>
 
         <para>
-            It is worth considering the structure of a typical work directory. 
+            It is worth considering the structure of a typical work directory.
             As an example, consider the <filename>linux-yocto-kernel-3.0</filename>
-            on the machine <filename>qemux86</filename> 
-            built within the Yocto Project.  
-            For this package, a work directory of 
-            <filename>tmp/work/qemux86-poky-linux/linux-yocto-3.0+git1+&lt;.....&gt;</filename>, 
-            referred to as <filename><link linkend='var-WORKDIR'>WORKDIR</link></filename>, is created.  
-            Within this directory, the source is unpacked to 
-            <filename>linux-qemux86-standard-build</filename> and then patched by Quilt 
-            (see the 
-            "<ulink url='&YOCTO_DOCS_DEV_URL;#using-a-quilt-workflow'>Modifying Package 
-            Source Code with Quilt</ulink>" section in the Yocto Project Development Manual.   
-            Within the <filename>linux-qemux86-standard-build</filename> directory, 
+            on the machine <filename>qemux86</filename>
+            built within the Yocto Project.
+            For this package, a work directory of
+            <filename>tmp/work/qemux86-poky-linux/linux-yocto-3.0+git1+&lt;.....&gt;</filename>,
+            referred to as <filename><link linkend='var-WORKDIR'>WORKDIR</link></filename>, is created.
+            Within this directory, the source is unpacked to
+            <filename>linux-qemux86-standard-build</filename> and then patched by Quilt
+            (see the
+            "<ulink url='&YOCTO_DOCS_DEV_URL;#using-a-quilt-workflow'>Modifying Package
+            Source Code with Quilt</ulink>" section in the Yocto Project Development Manual.
+            Within the <filename>linux-qemux86-standard-build</filename> directory,
             standard Quilt directories <filename>linux-3.0/patches</filename>
             and <filename>linux-3.0/.pc</filename> are created,
             and standard Quilt commands can be used.
         </para>
 
         <para>
-            There are other directories generated within WORKDIR. 
-            The most important directory is WORKDIR<filename>/temp/</filename>, which has log files for each 
-            task (<filename>log.do_*.pid</filename>) and contains the scripts BitBake runs for 
-            each task (<filename>run.do_*.pid</filename>). 
-            The WORKDIR<filename>/image/</filename> directory is where "make 
-            install" places its output that is then split into sub-packages 
+            There are other directories generated within WORKDIR.
+            The most important directory is WORKDIR<filename>/temp/</filename>, which has log files for each
+            task (<filename>log.do_*.pid</filename>) and contains the scripts BitBake runs for
+            each task (<filename>run.do_*.pid</filename>).
+            The WORKDIR<filename>/image/</filename> directory is where "make
+            install" places its output that is then split into sub-packages
             within WORKDIR<filename>/packages-split/</filename>.
         </para>
     </section>
@@ -496,7 +496,7 @@
     <title>The Metadata - <filename>meta/</filename></title>
 
     <para>
-        As mentioned previously, metadata is the core of the Yocto Project. 
+        As mentioned previously, metadata is the core of the Yocto Project.
         Metadata has several important subdivisions:
     </para>
 
@@ -504,16 +504,16 @@
         <title><filename>meta/classes/</filename></title>
 
         <para>
-            This directory contains the <filename>*.bbclass</filename> files. 
-            Class files are used to abstract common code so it can be reused by multiple 
-            packages. 
+            This directory contains the <filename>*.bbclass</filename> files.
+            Class files are used to abstract common code so it can be reused by multiple
+            packages.
             Every package inherits the <filename>base.bbclass</filename> file.
-            Examples of other important classes are <filename>autotools.bbclass</filename>, which 
+            Examples of other important classes are <filename>autotools.bbclass</filename>, which
             in theory allows any Autotool-enabled package to work with the Yocto Project with minimal effort.
-            Another example is <filename>kernel.bbclass</filename> that contains common code and functions 
-            for working with the Linux kernel. 
-            Functions like image generation or packaging also have their specific class files 
-            such as <filename>image.bbclass</filename>, <filename>rootfs_*.bbclass</filename> and 
+            Another example is <filename>kernel.bbclass</filename> that contains common code and functions
+            for working with the Linux kernel.
+            Functions like image generation or packaging also have their specific class files
+            such as <filename>image.bbclass</filename>, <filename>rootfs_*.bbclass</filename> and
             <filename>package*.bbclass</filename>.
         </para>
     </section>
@@ -522,13 +522,13 @@
         <title><filename>meta/conf/</filename></title>
 
         <para>
-            This directory contains the core set of configuration files that start from 
-            <filename>bitbake.conf</filename> and from which all other configuration 
+            This directory contains the core set of configuration files that start from
+            <filename>bitbake.conf</filename> and from which all other configuration
             files are included.
-            See the include statements at the end of the file and you will note that even 
-            <filename>local.conf</filename> is loaded from there. 
-            While <filename>bitbake.conf</filename> sets up the defaults, you can often override 
-            these by using the (<filename>local.conf</filename>) file, machine file or 
+            See the include statements at the end of the file and you will note that even
+            <filename>local.conf</filename> is loaded from there.
+            While <filename>bitbake.conf</filename> sets up the defaults, you can often override
+            these by using the (<filename>local.conf</filename>) file, machine file or
             the distribution configuration file.
         </para>
     </section>
@@ -537,11 +537,11 @@
         <title><filename>meta/conf/machine/</filename></title>
 
         <para>
-            This directory contains all the machine configuration files. 
-            If you set <filename>MACHINE="qemux86"</filename>, 
-            the OpenEmbedded build system looks for a <filename>qemux86.conf</filename> file in this 
-            directory. 
-            The <filename>include</filename> directory contains various data common to multiple machines. 
+            This directory contains all the machine configuration files.
+            If you set <filename>MACHINE="qemux86"</filename>,
+            the OpenEmbedded build system looks for a <filename>qemux86.conf</filename> file in this
+            directory.
+            The <filename>include</filename> directory contains various data common to multiple machines.
             If you want to add support for a new machine to the Yocto Project, look in this directory.
         </para>
     </section>
@@ -550,10 +550,10 @@
         <title><filename>meta/conf/distro/</filename></title>
 
         <para>
-            Any distribution-specific configuration is controlled from this directory. 
-            For the Yocto Project, the <filename>defaultsetup.conf</filename> is the main file here.  
-            This directory includes the versions and the 
-            <filename>SRCDATE</filename> definitions for applications that are configured here. 
+            Any distribution-specific configuration is controlled from this directory.
+            For the Yocto Project, the <filename>defaultsetup.conf</filename> is the main file here.
+            This directory includes the versions and the
+            <filename>SRCDATE</filename> definitions for applications that are configured here.
             An example of an alternative configuration might be <filename>poky-bleeding.conf</filename>.
             Although this file mainly inherits its configuration from Poky.
         </para>
@@ -563,7 +563,7 @@
         <title><filename>meta/recipes-bsp/</filename></title>
 
         <para>
-            This directory contains anything linking to specific hardware or hardware 
+            This directory contains anything linking to specific hardware or hardware
             configuration information such as "u-boot" and "grub".
         </para>
     </section>
@@ -580,7 +580,7 @@
         <title><filename>meta/recipes-core/</filename></title>
 
         <para>
-            This directory contains what is needed to build a basic working Linux image 
+            This directory contains what is needed to build a basic working Linux image
             including commonly used dependencies.
         </para>
     </section>
@@ -598,8 +598,8 @@
         <title><filename>meta/recipes-extended/</filename></title>
 
         <para>
-            This directory contains non-essential applications that add features compared to the 
-            alternatives in core. 
+            This directory contains non-essential applications that add features compared to the
+            alternatives in core.
             You might need this directory for full tool functionality or for Linux Standard Base (LSB)
             compliance.
         </para>
@@ -625,7 +625,7 @@
         <title><filename>meta/recipes-kernel/</filename></title>
 
         <para>
-            This directory contains the kernel and generic applications and libraries that 
+            This directory contains the kernel and generic applications and libraries that
             have strong kernel dependencies.
         </para>
     </section>
@@ -651,7 +651,7 @@
 
         <para>
             This directory contains package and image recipes for using and testing
-            the <filename>PREEMPT_RT</filename> kernel. 
+            the <filename>PREEMPT_RT</filename> kernel.
         </para>
     </section>
 
@@ -668,7 +668,7 @@
         <title><filename>meta/recipes-support/</filename></title>
 
         <para>
-            This directory contains recipes that used by other recipes, but that are not directly 
+            This directory contains recipes that used by other recipes, but that are not directly
             included in images (i.e. dependencies of other recipes).
         </para>
     </section>
@@ -678,9 +678,9 @@
 
         <para>
             This directory contains a list of cached results for various architectures.
-            Because certain "autoconf" test results cannot be determined when cross-compiling due to 
-            the tests not able to run on a live system, the information in this directory is 
-            passed to "autoconf" for the various architectures. 
+            Because certain "autoconf" test results cannot be determined when cross-compiling due to
+            the tests not able to run on a live system, the information in this directory is
+            passed to "autoconf" for the various architectures.
         </para>
     </section>
 
@@ -694,6 +694,6 @@
 </section>
 
 </chapter>
-<!-- 
-vim: expandtab tw=80 ts=4 
+<!--
+vim: expandtab tw=80 ts=4
 -->