dev-manual: Various fixes for links, typos, and grammar

1. Added "Debian" as a distribution for best results.
2. Fixed a link to the Hob page and two links for the
   Build Appliance.
3. Three typos fixed and a few grammar items fixed.

(From yocto-docs rev: 0b381094ed9cc2d66895d4ad7c63005c8a918eb1)

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

1 files changed, 6 insertions, 6 deletions

diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index e09c373da2..65e17e24a0 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -97,7 +97,7 @@
     <para>
         Most teams have many pieces of software undergoing active development at any given time.
         You can derive large benefits by putting these pieces under the control of a source
-        control system that is compatible (i.e. Git or Subversion (SVN)) with the OpenEmbeded
+        control system that is compatible (i.e. Git or Subversion (SVN)) with the OpenEmbedded
         build system that the Yocto Project uses.
         You can then set the autobuilder to pull the latest revisions of the packages
         and test the latest commits by the builds.
@@ -131,7 +131,7 @@
             <listitem><para>Maintain your metadata in layers that make sense
                 for your situation.
                 See the "<link linkend='understanding-and-creating-layers'>Understanding
-                and Creating Layeres</link>" section for more information on
+                and Creating Layers</link>" section for more information on
                 layers.</para></listitem>
             <listitem><para>Separate the project's metadata and code by using
                 separate Git repositories.
@@ -187,7 +187,7 @@
     </para>
 
     <para>
-        Once you are set up through either tarball extraction or creation of Git repositories,
+        Once you are set up through either tarball extraction or a checkout of Git repositories,
         you are ready to develop.
     </para>
 
@@ -362,7 +362,7 @@
                 In its most general sense, it is an open-source project that was initially developed
                 by OpenedHand.  With OpenedHand, poky was developed off of the existing OpenEmbedded
                 build system becoming a build system for embedded images.
-                After Intel Corporation aquired OpenedHand, the project poky became the basis for
+                After Intel Corporation acquired OpenedHand, the project poky became the basis for
                 the Yocto Project's build system.
                 Within the Yocto Project source repositories, poky exists as a separate Git repository
                 that can be cloned to yield a local copy on the host system.
@@ -380,7 +380,7 @@
                 and unpacking a Yocto Project release tarball or creating a local copy of
                 the <filename>poky</filename> Git repository
                 <filename>git://git.yoctoproject.org/poky</filename>.
-                Sometimes you might here the term "poky directory" used to refer to this
+                Sometimes you might hear the term "poky directory" used to refer to this
                 directory structure.
                 <note>
                     The OpenEmbedded build system does not support file or directory names that
@@ -422,7 +422,7 @@
                 reflects the exact copy of the files at the time of their release.
                 You do this by using Git tags that are part of the repository.</para>
 
-                <para>For more information on concepts around Git repositories, branches, and tags,
+                <para>For more information on concepts related to Git repositories, branches, and tags,
                 see the
                 "<link linkend='repositories-tags-and-branches'>Repositories, Tags, and Branches</link>"
                 section.</para></listitem>