1 files changed, 9 insertions, 7 deletions

diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 1ff1ed7559..b1dd97a138 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -320,8 +320,8 @@
 
                 <para>
                     You can change the default behavior by setting this
-                    variable to "1", "yes", or "true" 
-                    in your <filename>local.conf</filename> file, which is 
+                    variable to "1", "yes", or "true"
+                    in your <filename>local.conf</filename> file, which is
                     located in the
                     <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>:
                     Here is an example:
@@ -829,7 +829,7 @@
         <glossentry id='var-BUGTRACKER'><glossterm>BUGTRACKER</glossterm>
             <glossdef>
                 <para>
-                    Specifies a URL for an upstream bug tracking website for 
+                    Specifies a URL for an upstream bug tracking website for
                     a recipe.
                     The OpenEmbedded build system does not use this variable.
                     Rather, the variable is a useful pointer in case a bug
@@ -893,19 +893,21 @@
             <glossdef>
                 <para>
                     An internal variable specifying the special class override
-                    that should currently apply (e.g. "class-target", 
+                    that should currently apply (e.g. "class-target",
                     "class-native", and so forth).
-                    The classes that use this variable set it to 
+                    The classes that use this variable set it to
                     appropriate values.
                 </para>
 
                 <para>
                     You do not normally directly interact with this variable.
                     The value for the <filename>CLASSOVERRIDE</filename>
-                    variable goes into 
+                    variable goes into
                     <link linkend='var-OVERRIDES'><filename>OVERRIDES</filename></link>
                     and then can be used as an override.
-                    Here is an example:
+                    Here is an example where "python-native" is added to
+                    <link linkend='var-DEPENDS'><filename>DEPENDS</filename></link>
+                    only when building for the native case:
                     <literallayout class='monospaced'>
      DEPENDS_append_class-native = " python-native"
                     </literallayout>