1 files changed, 11 insertions, 11 deletions

diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 121519bcb2..cdb799d915 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -108,7 +108,7 @@
             <orderedlist>
                 <listitem><para><emphasis>Set up your host development system to support
                     development using the Yocto Project</emphasis>:  See the
-                    "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distributions</ulink>"
+                    "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distribution</ulink>"
                     and the
                     "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both
                     in the Yocto Project Quick Start for requirements.</para></listitem>
@@ -119,7 +119,7 @@
                     process and to the tools you need.
                     For information on how to set up the
                     <link linkend='source-directory'>Source Directory</link>, see the
-                    "<link linkend='getting-setup'>Getting Setup</link>" section.</para></listitem>
+                    "<link linkend='getting-setup'>Getting Set up</link>" section.</para></listitem>
                 <listitem><para><emphasis>Establish the <filename>meta-intel</filename>
                     repository on your system</emphasis>:  Having local copies
                     of these supported BSP layers on your system gives you
@@ -255,7 +255,7 @@
             <para>
                 Traditionally, when one thinks of a patched kernel, they think of a base kernel
                 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
+                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>
@@ -338,7 +338,7 @@
                 Conceptually, you can think of the kernel source repositories as all the
                 source files necessary for all the supported kernels.
                 As a developer, you are just interested in the source files for the kernel on
-                on which you are working.
+                which you are working.
                 And, furthermore, you need them available on your host system.
             </para>
 
@@ -401,7 +401,7 @@
                 <orderedlist>
                     <listitem><para><emphasis>Set up your host development system to support
                         development using the Yocto Project</emphasis>:  See
-                        "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distributions</ulink>" and
+                        "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distribution</ulink>" and
                         "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both
                         in the Yocto Project Quick Start for requirements.</para></listitem>
                     <listitem><para><emphasis>Establish a local copy of project files on your
@@ -455,7 +455,7 @@
                         Doing so, can produce unexpected results when the OpenEmbedded build system
                         regenerates the configuration file.</para>
                         <para>Once you are satisfied with the configuration changes made using
-                        <filename>menuconfig</filename>, you can directly examine the
+                        <filename>menuconfig</filename>, you can directly compare the
                         <filename>.config</filename> file against a saved original and gather those
                         changes into a config fragment to be referenced from within the kernel's
                         <filename>.bbappend</filename> file.</para></listitem>
@@ -513,11 +513,11 @@
             <orderedlist>
                 <listitem><para><emphasis>Prepare the Host System for the Yocto Project</emphasis>:
                     See
-                    "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distributions</ulink>" and
+                    "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distribution</ulink>" and
                     "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both
                     in the Yocto Project Quick Start for requirements.</para></listitem>
                 <listitem><para><emphasis>Secure the Yocto Project Kernel Target Image</emphasis>:
-                    You must have a target kernel image that has been built using the OpenEmbeded
+                    You must have a target kernel image that has been built using the OpenEmbedded
                     build system.</para>
                     <para>Depending on whether the Yocto Project has a pre-built image that matches your target
                     architecture and where you are going to run the image while you develop your application
@@ -527,7 +527,7 @@
                                 <ulink url='&YOCTO_MACHINES_DL_URL;'><filename>machines</filename></ulink>
                                 if your target architecture is supported and you are going to develop
                                 and test your application on actual hardware.</para></listitem>
-                            <listitem><para>Download the image from the
+                            <listitem><para>Download the image from
                                 <ulink url='&YOCTO_QEMU_DL_URL;'>
                                 <filename>machines/qemu</filename></ulink> if your target architecture is supported
                                 and you are going to develop and test your application using the QEMU
@@ -1485,7 +1485,7 @@ directory.</para></listitem>
                 <listitem><para><emphasis>Develop and Test your Application:</emphasis>  At this point,
                     you have the tools to develop your application.
                     If you need to separately install and use the QEMU emulator, you can go to
-                    <ulink url='http://www.qemu.org'>QEMU Home Page</ulink> to download and learn about the
+                    <ulink url='http://wiki.qemu.org/Main_Page'>QEMU Home Page</ulink> to download and learn about the
                     emulator.</para></listitem>
             </orderedlist>
         </para>
@@ -1844,7 +1844,7 @@ directory.</para></listitem>
                 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
                 for which you are building the image.</para></listitem>
             <listitem><para>You can modify various policy settings such as the package format used to build with,
-                the parrallelism BitBake uses, whether or not to build an external toolchain, and which host
+                the parallelism BitBake uses, whether or not to build an external toolchain, and which host
                 to build against.</para></listitem>
             <listitem><para>You can manage
                 <link linkend='understanding-and-creating-layers'>layers</link>.</para></listitem>