docs/ spelling fixes

Just a few things in the documentation I noticed while reading up on OE. I don't understand why 'git diff' included "\ No newline at end of file" for some of these, or how I could instruct it not to, but I also didn't want to pick apart my patch outside of git.

Signed-off-by: Michael Jones <michael.jones@matrix-vision.de>

5 files changed, 9 insertions, 9 deletions

diff --git a/docs/usermanual/reference/class_autotools.xml b/docs/usermanual/reference/class_autotools.xml
index a9e1a5721a..248b66a116 100644
--- a/docs/usermanual/reference/class_autotools.xml
+++ b/docs/usermanual/reference/class_autotools.xml
@@ -12,7 +12,7 @@
   <para>The autotools class takes care of all of the details for you. It
   defines appropriate tasks for <emphasis>configure</emphasis>,
   <emphasis>compile</emphasis>, <emphasis>stage</emphasis> and
-  <emphasis>install</emphasis>. At it's simplest adding an inherit for the
+  <emphasis>install</emphasis>. At its simplest adding an inherit for the
   autotools class is all that is required. The netcat recipe for example
   is:<screen>DESCRIPTION = "GNU Netcat"
 HOMEPAGE = "http://netcat.sourceforge.net"
@@ -150,4 +150,4 @@ do_configure() {
     oe_runconf
 }</screen></para>
   </section>
-</section>
\ No newline at end of file
+</section>
diff --git a/docs/usermanual/reference/class_binconfig.xml b/docs/usermanual/reference/class_binconfig.xml
index 049f85e1f0..4c60e671f0 100644
--- a/docs/usermanual/reference/class_binconfig.xml
+++ b/docs/usermanual/reference/class_binconfig.xml
@@ -37,10 +37,10 @@
   class.</para>
 
   <para>The class will search in source directory, <command>${S}</command>,
-  and all it's subdirectories, for files that end in
+  and all its subdirectories, for files that end in
   <command>-config</command> and process them as described above. All that is
   required to use the class is the addition of binconfig in an inherit
   statement:</para>
 
   <para><screen>inherit autotools binconfig</screen></para>
-</section>
\ No newline at end of file
+</section>
diff --git a/docs/usermanual/reference/class_image.xml b/docs/usermanual/reference/class_image.xml
index b591e9aae2..227f7e1cd0 100644
--- a/docs/usermanual/reference/class_image.xml
+++ b/docs/usermanual/reference/class_image.xml
@@ -349,10 +349,10 @@ Alias /bogofeed ${DEPLOY_DIR}
 	<command>deploy/ipk</command>).</para>
         <para>Now, every image built will automatically contain feed configs
 	for the deploy directory (as of time of writing, deploy directory is internally structured with
-	per-arch subdirectories; so, there several feed configs are being generated, one for each subdirectory).
+	per-arch subdirectories; so, there are several feed configs being generated, one for each subdirectory).
         </para>
 
     </section>
 
   </section>
-</section>
\ No newline at end of file
+</section>
diff --git a/docs/usermanual/reference/dirs_install.xml b/docs/usermanual/reference/dirs_install.xml
index 75f85ac930..14f3fc645e 100644
--- a/docs/usermanual/reference/dirs_install.xml
+++ b/docs/usermanual/reference/dirs_install.xml
@@ -6,7 +6,7 @@
   control the directories into which files are installed.</para>
 
   <para>These variables can be used directly by the recipe to refer to paths
-  that will be used after the package is installed. For example, when specify
+  that will be used after the package is installed. For example, when specifying
   the location of configuration files you need to specify the location on the
   target as show in the following example from quagga:<screen># Indicate that the default files are configuration files
 CONFFILES_${PN} = "${sysconfdir}/default/quagga"
diff --git a/docs/usermanual/reference/fakeroot.xml b/docs/usermanual/reference/fakeroot.xml
index 5eb6a48eb0..845756551b 100644
--- a/docs/usermanual/reference/fakeroot.xml
+++ b/docs/usermanual/reference/fakeroot.xml
@@ -45,7 +45,7 @@ brw-------  1 root root 22, 0 Aug 18 13:20 hdc
     device node, even though we did not have to give a password for the root
     user. In reality this device node still doesn't exist, it just looks like
     it exits. Fakeroot is lying to the shell process and telling it that
-    <emphasis>"yes, this file exists and these are it's
+    <emphasis>"yes, this file exists and these are its
     properties"</emphasis>. We'll talk more about how fakeroot actually works
     in a minute.</para>
 
@@ -183,4 +183,4 @@ crw-r----- root/root    204,10 2006-08-16 13:07:12 ./dev/ttySC2
     oe_runmake install-man DESTDIR=${D}
     ...</screen></para>
   </section>
-</section>
\ No newline at end of file
+</section>