ref-manual: Minor edits to "bitbake/" section.

(From yocto-docs rev: 9d697cde9a1c5367e4529465b7c5a1443657b31b)

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

diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml
index 2fa3341e6177e2e9265da928400c8a42494063b3..e14c6b426dac64bdad61968c4f0ea5341b18e3d5 100644 (file)
--- a/documentation/ref-manual/ref-structure.xml
+++ b/documentation/ref-manual/ref-structure.xml
@@ -33,10 +33,12 @@
         <title><filename>bitbake/</filename></title>
 
         <para>
-            The <ulink url='source-directory'>Source Directory</ulink>
+            The <ulink url='&YOCTO_DOCS_DEV_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
+            BitBake, a
+            <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>
+            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.
@@ -46,7 +48,7 @@
             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"><filename>&OE_INIT_FILE;</filename></link>
             script places the <filename>scripts</filename> and <filename>bitbake/bin</filename>
             directories (in that order) into the shell's <filename>PATH</filename> environment
             variable.