documentation/dev-manual/dev-manual-model.xml: Robert P. J. Day Edits

Two small corrections for better wording.  A mis-spelling also
fixed.

(From yocto-docs rev: 915ec9f9adbde86008ffb086ac81a435d5910733)

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

diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 93406eb6007ae3c2a5db91bb11eea5abbaff5ddc..1d45a036c84c2d99d0936e0c016f4672f57c701e 100644 (file)
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -35,8 +35,8 @@
         System development involves modification or creation of an image that you want to run on 
         a specific hardware target.  
         Usually, when you want to create an image that runs on embedded hardware, the image does 
-        not require the same amount of features that a full-fledged Linux distribution provides.  
-        Thus, you can create a much smaller image that is designed to just use the hardware 
+        not require the same number of features that a full-fledged Linux distribution provides.
+        Thus, you can create a much smaller image that is designed to use only the hardware
         features for your particular hardware.
     </para>
 
@@ -213,8 +213,8 @@
 
             <para>
                 Traditionally, when one thinks of a patched kernel, they think of a base kernel
-                source tree and a fixed structure that conains kernel patches.
-                The Yocto Project, however, employs mechanisims, that in a sense, result in a kernel source
+                source tree and a fixed structure that contains kernel patches.
+                The Yocto Project, however, employs mechanisms, that in a sense, result in a kernel source
                 generator.
                 By the end of this section, this analogy will become clearer.
             </para>