Signed-off-by: Robert P. J. Day <[email protected]>

---

diff --git a/documentation/dev-manual/dev-manual-newbie.xml 
b/documentation/dev-manual/dev-manual-newbie.xml
index 600c789..58343dc 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -430,7 +430,7 @@
         <note>
             The recommended method for setting up the Yocto Project
             <link linkend='source-directory'>Source Directory</link> and the
-            files for supported BSPs (<filename>meta-intel</filename>) is to
+            files for supported BSPs (eg., <filename>meta-intel</filename>) is 
to
             use <link linkend='git'>Git</link> to create a local copy of the
             upstream repositories.
         </note>
@@ -810,7 +810,8 @@
     <title>Git</title>

     <para>
-        The Yocto Project uses Git, which is a free, open source distributed 
version control system.
+        The Yocto Project makes extensive use of Git,
+        which is a free, open source distributed version control system.
         Git supports distributed development, non-linear development, and can 
handle large projects.
         It is best that you have some fundamental understanding of how Git 
tracks projects and
         how to work with Git if you are going to use the Yocto Project for 
development.
@@ -914,7 +915,7 @@
             local working branch based on a branch name,
             your local environment matches the "tip" of that development branch
             at the time you created your local branch, which could be
-            different than the files at the time of a similarly named release.
+            different from the files at the time of a similarly named release.
             In other words, creating and checking out a local branch based on 
the
             <filename>&DISTRO_NAME;</filename> branch name is not the same as
             cloning and checking out the <filename>master</filename> branch.
@@ -1007,7 +1008,7 @@
                     will allow the change, and for ultimately pushing the 
change from your local Git repository
                     into the project’s upstream (or master) 
repository.</para></listitem>
                 <listitem><para><emphasis><filename>git 
status</filename>:</emphasis> Reports any modified files that
-                    possibly need staged and committed.</para></listitem>
+                    possibly need to be staged and committed.</para></listitem>
                 <listitem><para><emphasis><filename>git checkout 
&lt;branch-name&gt;</filename>:</emphasis> Changes
                     your working branch.
                     This command is analogous to "cd".</para></listitem>
@@ -1284,10 +1285,9 @@
             <listitem><para><emphasis>Board Support Package (BSP) README 
Files:</emphasis>
                 For BSP maintainers of supported BSPs, you can examine
                 individual BSP <filename>README</filename> files.
-                Alternatively, you can examine the
-                <filename>MAINTAINERS</filename> file, which is found in the
-                <filename>meta-intel</filename>, for a list of all supported
-                BSP maintainers.
+                In addition, some layers (such as the 
<filename>meta-intel</filename> layer),
+                include a <filename>MAINTAINERS</filename> file which contains
+                a list of all supported BSP maintainers for that layer.
                 </para></listitem>
             <listitem><para><emphasis>Search by File:</emphasis>
                 Using <link linkend='git'>Git</link>, you can enter the

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to