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

Robert ear-marked some links to point to downloads.yoctoproject.org.
He also made several wording changes that resulted in better language
and in a couple of cases fixed incorrect subject/verb usage.

(From yocto-docs rev: 9106619c4264c2669be041c1e6d6124e022ab2d1)

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

1 files changed, 15 insertions, 15 deletions

diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index c85667c..3eef746 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -7,8 +7,8 @@
 
 <para>
     This chapter helps you understand the Yocto Project as an open source development project.
-    In general, working in an open source environment is very different as compared to working in a 
-    proprietary environment.  
+    In general, working in an open source environment is very different from working in a 
+    closed, proprietary environment.  
     Additionally, the Yocto Project uses specific tools and constructs as part of its development 
     environment.  
     The chapter specifically addresses open source philosophy, licensing issues, code repositories, 
@@ -20,10 +20,10 @@
 
     <para>
         Open source philosophy is characterized by software development directed by peer production 
-        and collaboration through a concerned community of developers.  
+        and collaboration through an active community of developers.
         Contrast this to the more standard centralized development models used by commercial software 
         companies where a finite set of developers produce a product for sale using a defined set 
-        of procedures that ultimately result in an end-product whose architecture and source material 
+        of procedures that ultimately result in an end product whose architecture and source material
         are closed to the public.
     </para>
 
@@ -33,7 +33,7 @@
         stake in the software project.  
         The open source environment contains new copyright, licensing, domain, and consumer issues 
         that differ from the more traditional development environment.  
-        In an open source environment, the end-product, source material, and documentation are 
+        In an open source environment, the end product, source material, and documentation are
         all available to the public at no cost.
     </para>
 
@@ -101,7 +101,7 @@
                 <para>
                 <imagedata fileref="figures/source-repos.png" align="center" width="6in" depth="4in" />
                 </para></listitem>
-            <listitem><para><anchor id='index-downloads' /><emphasis><ulink url='http://www.yoctoproject.org/downloads/'>Index of /downloads:</ulink></emphasis>
+            <listitem><para><anchor id='index-downloads' /><emphasis><ulink url='http://downloads.yoctoproject.org/releases/'>Index of /releases:</ulink></emphasis>
                 This area contains an index of downloads such as 
                 the <trademark class='trade'>Eclipse</trademark>
                 Yocto Plug-in, miscellaneous support, Poky, pseudo, cross-development toolchains,
@@ -115,7 +115,7 @@
                 This page on the Yocto Project website allows you to download any Yocto Project
                 release or Board Support Package (BSP) in tarball form.
                 The tarballs are similar to those found in the 
-                <ulink url='http://www.yoctoproject.org/downloads/'>Index of /downloads:</ulink> area.</para>
+                <ulink url='http://downloads.yoctoproject.org/releases/'>Index of /releases:</ulink> area.</para>
                 <para>
                 <imagedata fileref="figures/yp-download.png" align="center" width="6in" depth="4in" />
             </para></listitem>
@@ -133,7 +133,7 @@
     <itemizedlist>
         <listitem><para><emphasis>Append Files:</emphasis> Files that append build information to 
             a recipe file.  
-            Information in append files override the information in the similarly-named recipe file.
+            Information in append files overrides the information in the similarly-named recipe file.
             Append files use the <filename>.bbappend</filename> filename suffix.</para></listitem>
         <listitem><para><emphasis>BitBake:</emphasis> The task executor and scheduler used by 
             the Yocto Project to build images. 
@@ -143,12 +143,12 @@
             and inheritance allowing commonly used patterns to be defined once and easily used 
             in multiple recipes.  
             Class files end with the <filename>.bbclass</filename> filename extension.</para></listitem>
-        <listitem><para><emphasis>Configuration File:</emphasis>  Configuration information in the 
-            <filename>.conf</filename> files provides global definitions of variables.  
-            The <filename>conf/local.conf</filename> configuration file in the Yocto Project 
-            build directory defines user-defined variables that affect each build.  
-            The <filename>distro/poky.conf</filename> configuration file also in the 
-            build directory defines Yocto ‘distro’ configuration 
+        <listitem><para><emphasis>Configuration File:</emphasis>  Configuration information in various
+            <filename>.conf</filename> files provides global definitions of variables.
+            The <filename>conf/local.conf</filename> configuration file in the Yocto Project
+            build directory contains user-defined variables that affect each build.
+            The <filename>meta-yocto/conf/distro/poky.conf</filename> configuration file
+            defines Yocto ‘distro’ configuration
             variables used only when building with this policy.  
             Machine configuration files, which 
             are located throughout the Yocto Project file structure, define
@@ -159,7 +159,7 @@
         <listitem><para><emphasis>Cross-Development Toolchain:</emphasis> A collection of software development
             tools and utilities that allow you to develop software for targeted architectures.
             This toolchain contains cross-compilers, linkers, and debuggers that are specific to 
-            an architecure.
+            an architecture.
             You can use the Yocto Project to build cross-development toolchains in tarball form that when 
             unpacked contain the development tools you need to cross-compile and test your software.
             The Yocto Project ships with images that contain toolchains for supported architectures