ref-manual: Edits to the introduction section.

(From yocto-docs rev: c01105ad507deaa1cdc21588ab8c6f4ec8455a51)

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-features.xml b/documentation/ref-manual/ref-features.xml
index 77c31275ae21ea9643b4f840f0b47f0f90dad6b0..1d9cd5172eaee873f6ed5105df97880e24f6aa47 100644 (file)
--- a/documentation/ref-manual/ref-features.xml
+++ b/documentation/ref-manual/ref-features.xml
@@ -5,6 +5,12 @@
 <chapter id='ref-features'>
     <title>Reference: Features</title>
 
+    <para>
+        This chapter provides a reference of shipped machine and distro features
+        you can include as part of the image, a reference on image types you can
+        build, and a reference on feature backfilling.
+    </para>
+
     <para>
         Features provide a mechanism for working out which packages
         should be included in the generated images.
@@ -27,7 +33,8 @@
     <para>
         One method you can use to determine which recipes are checking to see if a
         particular feature is contained or not is to <filename>grep</filename> through
-        the metadata for the feature.
+        the <ulink url='&YOCTO_DOCS_DEV_URL;#metadata'>Metadata</ulink>
+        for the feature.
         Here is an example that discovers the recipes whose build is potentially
         changed based on a given feature:
         <literallayout class='monospaced'>
@@ -36,13 +43,6 @@
         </literallayout>
     </para>
 
-    <para>
-        This chapter provides a reference of shipped machine and distro features
-        you can include as part of the image, a reference on image types you can
-        build, and a reference on feature backfilling.
-    </para>
-
-
     <section id='ref-features-distro'>
         <title>Distro</title>