[gnome-continuous-yocto/gnomeostree-3.28-rocko: 8067/8267] ref-manual: Fixed two internal links.

[Emmanuele Bassi <ebassi src gnome org>]

commit a6db326292457283b97a806708fe6f8c6fd2283c
Author: Scott Rifenbark <srifenbark gmail com>
Date:   Mon Oct 16 13:33:31 2017 -0700

    ref-manual: Fixed two internal links.
    
    Links were using the <ulink> style tag when they should have been
    using the <link> style.
    
    (From yocto-docs rev: 6c4a39537211ccb322f4ac1c8009ebabcd7b209d)
    
    Signed-off-by: Scott Rifenbark <srifenbark gmail com>
    Signed-off-by: Richard Purdie <richard purdie linuxfoundation org>

 documentation/ref-manual/ref-bitbake.xml |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/documentation/ref-manual/ref-bitbake.xml b/documentation/ref-manual/ref-bitbake.xml
index 9a94991..3a80770 100644
--- a/documentation/ref-manual/ref-bitbake.xml
+++ b/documentation/ref-manual/ref-bitbake.xml
@@ -8,7 +8,7 @@
 
     <para>
         BitBake is a program written in Python that interprets the
-        <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink> used by
+        <link linkend='metadata'>Metadata</link> used by
         the OpenEmbedded build system.
         At some point, developers wonder what actually happens when you enter:
         <literallayout class='monospaced'>
@@ -24,7 +24,7 @@
         BitBake strives to be a generic "task" executor that is capable of handling complex dependency 
relationships.
         As such, it has no real knowledge of what the tasks being executed actually do.
         BitBake just considers a list of tasks with dependencies and handles
-        <ulink url='&YOCTO_DOCS_REF_URL;#metadata'>Metadata</ulink>
+        <link linkend='metadata'>Metadata</link>
         consisting of variables in a certain format that get passed to the tasks.
     </note>