ref-manual: Edits to a few variables in the glossary.

I updated the following variables with minor changes:

  TARGET_CC_ARCH
  BUILD_CPPFLAGS
  BUILDSDK_CPPFLAGS
  CPPFLAGS
  TARGET_CPPFLAGS

(From yocto-docs rev: f7d48ed379778a8568c7e5f812cdb1cbc5339f39)

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

1 files changed, 5 insertions, 5 deletions

diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index cd235e633e..bd1441196b 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -894,8 +894,8 @@
         <glossentry id='var-BUILD_CPPFLAGS'><glossterm>BUILD_CPPFLAGS</glossterm>
             <glossdef>
                 <para>
-                    Specifies the flags to pass to the C pre-processor and
-                    eventually to both the C and C++ compilers when building
+                    Specifies the flags to pass to the C pre-processor
+                    (i.e. to both the C and the C++ compilers) when building
                     for the build host.
                     When building in the <filename>native</filename> context,
                     <link linkend='var-CPPFLAGS'><filename>CPPFLAGS</filename></link>
@@ -7774,9 +7774,9 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
                     <note>
                         It is a common workaround to append
                         <link linkend='var-LDFLAGS'><filename>LDFLAGS</filename></link>
-                        to <filename>TUNE_CC_ARCH</filename> in recipes
-                        that build software for the target that would not
-                        otherwise respect the exported
+                        to <filename>TARGET_CC_ARCH</filename>
+                        in recipes that build software for the target that
+                        would not otherwise respect the exported
                         <filename>LDFLAGS</filename> variable.
                     </note>
                 </para>