documentation/dev-manual/dev-manual-common-tasks.xml: Spell check.

(From yocto-docs rev: 3bc8b3a4fc0adcfcda3026e7c209e4f57e750737)

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

1 files changed, 3 insertions, 3 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index cd90c10a0b..e72e8f6f5f 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -948,7 +948,7 @@
                 <para>
                     Furthermore, you must use <filename>_append</filename> instead of the <filename>+=</filename> 
                     operator if you want to avoid ordering issues. 
-                    The reason for this is because doing so uncondtionally appends to the variable and 
+                    The reason for this is because doing so unconditionally appends to the variable and 
                     avoids ordering problems due to the variable being set in image recipes and 
                     <filename>.bbclass</filename> files with operators like <filename>?=</filename>.
                     Using <filename>_append</filename> ensures the operation takes affect.
@@ -1676,7 +1676,7 @@ so that there are some definite steps on how to do this.  I need more detail her
             You can use the <filename>menuconfig</filename> tool and configuration fragments to 
             make sure your <filename>.config</filename> file is just how you need it. 
             This section describes how to use <filename>menuconfig</filename>, create and use 
-            configuration fragments, and how to interatively tweak your <filename>.config</filename>
+            configuration fragments, and how to interactively tweak your <filename>.config</filename>
             file to create the leanest kernel configuration file possible.
         </para>
 
@@ -1791,7 +1791,7 @@ so that there are some definite steps on how to do this.  I need more detail her
                 For each output warning, a message points to the file
                 that contains a list of the options and a pointer to the config
                 fragment that defines them.
-                Collectively, the files are the key to streamlining the configiguration.
+                Collectively, the files are the key to streamlining the configuration.
             </para>
 
             <para>