dev-manual: Some edits early in Chapter 3.

(From yocto-docs rev: 566af2c28413eeb89b69a59fab087e0145a9493e)

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

1 files changed, 8 insertions, 3 deletions

diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index ce88b3473e..826dcd73f6 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -12,8 +12,10 @@
     closed, proprietary environment.
     Additionally, the Yocto Project uses specific tools and constructs as part of its development
     environment.
-    This chapter specifically addresses open source philosophy, licensing issues, code repositories,
-    the open source distributed version control system Git, and best practices using the Yocto Project.
+    This chapter specifically addresses open source philosophy, using the 
+    Yocto Project in a team environment, source repositories, Yocto Project
+    terms, licensing, the open source distributed version control system Git, 
+    workflows, bug tracking, and how to submit changes.
 </para>
 
 <section id='open-source-philosophy'>
@@ -66,6 +68,9 @@
         Thus, you can adapt it to many different use cases and scenarios.
         However, these characteristics can cause a struggle if you are trying
         to create a working setup that scales across a large team.
+    </para>
+
+    <para>
         To help with these types of situations, this section presents
         some of the project's most successful experiences,
         practices, solutions, and available technologies that work well.
@@ -110,7 +115,7 @@
                         </para></listitem>
                     <listitem><para>Keep your cross-development toolchains
                         updated.
-                        You can do this by provisioning either as new
+                        You can do this through provisioning either as new
                         toolchain downloads or as updates through a package
                         update mechanism using <filename>opkg</filename>
                         to provide updates to an existing toolchain.