documentation/adt-manual/adt-package.xml: Edits to packaging chapter

Some minor edits to create some links to some terms used.

(From yocto-docs rev: 1559b8caca07cce8630de9ddf8c84f0b24fa35e7)

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

diff --git a/documentation/adt-manual/adt-package.xml b/documentation/adt-manual/adt-package.xml
index 0da301b123965b286aea45de8ec81c6e1431288d..c55c10d1cd112f7ccdab697aed59cafa3becda90 100644 (file)
--- a/documentation/adt-manual/adt-package.xml
+++ b/documentation/adt-manual/adt-package.xml
@@ -45,7 +45,8 @@
 
     <para>
         Whichever PMS you are using, you need to be sure that the 
-        <filename>PACKAGE_CLASSES</filename> variable in the <filename>conf/local.conf</filename>
+        <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.  
         The first value you choose for the variable specifies the package file format for the root
         filesystem at sysroot.
@@ -55,7 +56,8 @@
 
     <note>
         For build performance information related to the PMS, see
-        <ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-package'>Packaging - <filename>package*.bbclass</filename></ulink> in The Yocto Project Reference Manual.
+        <ulink url='&YOCTO_DOCS_REF_URL;#ref-classes-package'>Packaging - <filename>package*.bbclass</filename></ulink>
+        in the Yocto Project Reference Manual.
     </note>
 
     <para>
@@ -75,7 +77,8 @@
     </para>
 
     <para>
-        Next, source the environment setup script found in the source directory.  
+        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>