[gnome-continuous-yocto/gnomeostree-3.28-rocko: 119/218] dev-manual: Fixed variable link to DEFAULTTUNE variable

[Emmanuele Bassi <ebassi src gnome org>]

commit 0fa8ccad9a992b8cf9c0dad2d7322fb7afad2fc4
Author: Kristi Rifenbark <kristi buzzcollectivemarketing com>
Date:   Mon Feb 12 16:44:18 2018 -0800

    dev-manual: Fixed variable link to DEFAULTTUNE variable
    
    Fixed [YOCTO #12458]
    
    (From yocto-docs rev: 85f2705115039429057ea35d2230693b71dd85ae)
    
    Signed-off-by: Kristi Rifenbark <kristi buzzcollectivemarketing com>
    Signed-off-by: Richard Purdie <richard purdie linuxfoundation org>

 .../dev-manual/dev-manual-common-tasks.xml         |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml 
b/documentation/dev-manual/dev-manual-common-tasks.xml
index 4e703c1..0081738 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -6752,7 +6752,7 @@ Some notes from Cal:
             you much of a performance difference across the other systems
             as compared to using a more general tuning across all the builds
             (e.g. setting
-            <ulink url='var-DEFAULTTUNE'><filename>DEFAULTTUNE</filename></ulink>
+            <ulink url='&YOCTO_DOCS_REF_URL;#var-DEFAULTTUNE'><filename>DEFAULTTUNE</filename></ulink>
             specifically for each machine's build).
             Rather than "max out" each build's tunings, you can take steps that
             cause the OpenEmbedded build system to reuse software across the