ref-manual: Various spellings corrected.

(From yocto-docs rev: f05f6a972d68ae9f1acc6e91a69bc9d98242ff5d)

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

1 files changed, 7 insertions, 7 deletions

diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index df0b8e7459..49e1fcd8bd 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -311,7 +311,7 @@
                     of free inodes further reduces by 5 Kbytes in the
                     <filename>${SSTATE_DIR}</filename> directory.
                     Subsequent warnings based on the interval occur each time
-                    a respective interval is reached beyond the intial warning
+                    a respective interval is reached beyond the initial warning
                     (i.e. 1 Gbytes and 100 Kbytes).
                 </para>
             </glossdef>
@@ -1760,7 +1760,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
                     The second statement is a good example of why the <filename>KMACHINE</filename> variable
                     is needed.
                     In this example, the OpenEmbedded build system uses the <filename>cedartrail-nopvr</filename>
-                    machine name to refer to the Cedar Trail BSP that does not support the propriatory
+                    machine name to refer to the Cedar Trail BSP that does not support the proprietary
                     PowerVR driver.
                     The kernel, however, uses the machine name <filename>cedartrail</filename>.
                     Thus, the append file must map the <filename>cedartrail-nopvr</filename> machine name to
@@ -1948,7 +1948,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
                 <para>The Linux version from <filename>kernel.org</filename>
                     on which the Linux kernel image being built using the
                     OpenEmbedded build system is based.
-                    You define this varible in the kernel recipe.
+                    You define this variable in the kernel recipe.
                     For example, the <filename>linux-yocto-3.4.bb</filename>
                     kernel recipe found in
                     <filename>meta/recipes-kernel/linux</filename>
@@ -2621,7 +2621,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
                     <literallayout class='monospaced'>
      PRINC := "${@int(PRINC) + 2}"
                     </literallayout>
-                    It is adviseable not to use strings such as ".= '.1'" with the variable because
+                    It is advisable not to use strings such as ".= '.1'" with the variable because
                     this usage is very sensitive to layer ordering.
                     You should avoid explicit assignments as they cannot
                     adequately represent multiple
@@ -2935,7 +2935,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
                     This variable tells the OpenEmbedded build system which bits to pull
                     in for the build and how to pull them in.
                     For example, if the recipe only needs to fetch a tarball from the
-                    internet, the recipe uses a single <filename>SRC_URI</filename> entry.
+                    Internet, the recipe uses a single <filename>SRC_URI</filename> entry.
                     On the other hand, if the recipe needs to fetch a tarball, apply
                     two patches, and include a custom file, the recipe would include four
                     instances of the variable.</para>
@@ -3054,7 +3054,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
                     <itemizedlist>
                         <listitem><para><emphasis><filename>unpack</filename> -</emphasis> Controls
                             whether or not to unpack the file if it is an archive.
-                            The default action is to upack the file.</para></listitem>
+                            The default action is to unpack the file.</para></listitem>
                         <listitem><para><emphasis><filename>subdir</filename> -</emphasis> Places the file
                             (or extracts its contents) into the specified
                             subdirectory of <link linkend='var-WORKDIR'><filename>WORKDIR</filename></link>.
@@ -3176,7 +3176,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
                     <link linkend='var-SSTATE_DIR'><filename>SSTATE_DIR</filename></link>,
                     you need to add
                     "PATH" at the end as shown in the examples below.
-                    The build system substitues the correct path within the
+                    The build system substitutes the correct path within the
                     directory structure.
                     <literallayout class='monospaced'>
      SSTATE_MIRRORS ?= "\