From b7b64ae73fdcf741d0d0fa6cb06d999975ae02c2 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Tue, 9 Apr 2013 11:27:10 -0700
Subject: dev-manual: Edits to "Policies and Change Flow" section.

(From yocto-docs rev: 9d4c4fdaec73a0bba3e19872cad24a8c2463da58)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/dev-manual/dev-manual-newbie.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'documentation/dev-manual/dev-manual-newbie.xml')

diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 759871a2b3..2f6805625b 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -316,14 +316,14 @@
         <title>Policies and Change Flow</title>
 
         <para>
-            The Yocto Project itself uses a hierarchy structure and a
+            The Yocto Project itself uses a hierarchical structure and a
             pull model.
             Scripts exist to create and send pull requests
             (i.e. <filename>create-pull-request</filename> and
             <filename>send-pull-request</filename>).
             This model is in line with other open source projects where
             maintainers are responsible for specific areas of the project
-            and a single maintainer handles the final top-of-tree merges.
+            and a single maintainer handles the final "top-of-tree" merges.
         </para>
 
         <note>
-- 
cgit v1.2.3-54-g00ecf