documentation: adt-manual - Removed all trailing whitespace.

(From yocto-docs rev: c1c271c0404dff9ed49597a4582a56def8237dd7)

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

1 files changed, 27 insertions, 27 deletions

diff --git a/documentation/adt-manual/adt-package.xml b/documentation/adt-manual/adt-package.xml
index da8d10fa4b..9e68c3131e 100644
--- a/documentation/adt-manual/adt-package.xml
+++ b/documentation/adt-manual/adt-package.xml
@@ -6,10 +6,10 @@
 <title>Optionally Customizing the Development Packages Installation</title>
 
     <para>
-        Because the Yocto Project is suited for embedded Linux development, it is 
-        likely that you will need to customize your development packages installation.  
-        For example, if you are developing a minimal image, then you might not need 
-        certain packages (e.g. graphics support packages).  
+        Because the Yocto Project is suited for embedded Linux development, it is
+        likely that you will need to customize your development packages installation.
+        For example, if you are developing a minimal image, then you might not need
+        certain packages (e.g. graphics support packages).
         Thus, you would like to be able to remove those packages from your target sysroot.
     </para>
 
@@ -17,24 +17,24 @@
     <title>Package Management Systems</title>
 
     <para>
-        The OpenEmbedded build system supports the generation of sysroot files using 
+        The OpenEmbedded build system supports the generation of sysroot files using
         three different Package Management Systems (PMS):
         <itemizedlist>
-            <listitem><para><emphasis>OPKG:</emphasis> A less well known PMS whose use 
-                originated in the OpenEmbedded and OpenWrt embedded Linux projects.  
+            <listitem><para><emphasis>OPKG:</emphasis> A less well known PMS whose use
+                originated in the OpenEmbedded and OpenWrt embedded Linux projects.
                 This PMS works with files packaged in an <filename>.ipk</filename> format.
-                See <ulink url='http://en.wikipedia.org/wiki/Opkg'></ulink> for more 
+                See <ulink url='http://en.wikipedia.org/wiki/Opkg'></ulink> for more
                 information about OPKG.</para></listitem>
-            <listitem><para><emphasis>RPM:</emphasis> A more widely known PMS intended for GNU/Linux 
-                distributions.  
+            <listitem><para><emphasis>RPM:</emphasis> A more widely known PMS intended for GNU/Linux
+                distributions.
                 This PMS works with files packaged in an <filename>.rms</filename> format.
-                The build system currently installs through this PMS by default.  
+                The build system currently installs through this PMS by default.
                 See <ulink url='http://en.wikipedia.org/wiki/RPM_Package_Manager'></ulink>
                 for more information about RPM.</para></listitem>
-            <listitem><para><emphasis>Debian:</emphasis> The PMS for Debian-based systems 
-                is built on many PMS tools.  
-                The lower-level PMS tool <filename>dpkg</filename> forms the base of the Debian PMS.  
-                For information on dpkg see 
+            <listitem><para><emphasis>Debian:</emphasis> The PMS for Debian-based systems
+                is built on many PMS tools.
+                The lower-level PMS tool <filename>dpkg</filename> forms the base of the Debian PMS.
+                For information on dpkg see
                 <ulink url='http://en.wikipedia.org/wiki/Dpkg'></ulink>.</para></listitem>
         </itemizedlist>
     </para>
@@ -44,13 +44,13 @@
     <title>Configuring the PMS</title>
 
     <para>
-        Whichever PMS you are using, you need to be sure that the 
+        Whichever PMS you are using, you need to be sure that the
         <ulink url='&YOCTO_DOCS_REF_URL;#var-PACKAGE_CLASSES'><filename>PACKAGE_CLASSES</filename></ulink>
         variable in the <filename>conf/local.conf</filename>
-        file is set to reflect that system.  
+        file is set to reflect that system.
         The first value you choose for the variable specifies the package file format for the root
         filesystem at sysroot.
-        Additional values specify additional formats for convenience or testing.  
+        Additional values specify additional formats for convenience or testing.
         See the configuration file for details.
     </para>
 
@@ -61,14 +61,14 @@
     </note>
 
     <para>
-        As an example, consider a scenario where you are using OPKG and you want to add 
+        As an example, consider a scenario where you are using OPKG and you want to add
         the <filename>libglade</filename> package to the target sysroot.
     </para>
 
     <para>
-        First, you should generate the <filename>ipk</filename> file for the 
-        <filename>libglade</filename> package and add it 
-        into a working <filename>opkg</filename> repository.  
+        First, you should generate the <filename>ipk</filename> file for the
+        <filename>libglade</filename> package and add it
+        into a working <filename>opkg</filename> repository.
         Use these commands:
         <literallayout class='monospaced'>
      $ bitbake libglade
@@ -77,12 +77,12 @@
     </para>
 
     <para>
-        Next, source the environment setup script found in the 
-        <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.  
-        Follow that by setting up the installation destination to point to your 
-        sysroot as <filename>&lt;sysroot_dir&gt;</filename>.  
+        Next, source the environment setup script found in the
+        <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
+        Follow that by setting up the installation destination to point to your
+        sysroot as <filename>&lt;sysroot_dir&gt;</filename>.
         Finally, have an OPKG configuration file <filename>&lt;conf_file&gt;</filename>
-        that corresponds to the <filename>opkg</filename> repository you have just created. 
+        that corresponds to the <filename>opkg</filename> repository you have just created.
         The following command forms should now work:
         <literallayout class='monospaced'>
      $ opkg-cl –f &lt;conf_file&gt; -o &lt;sysroot_dir&gt; update