From 5c6753735f8a786c510208a6361bd2a8e392d0cf Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Fri, 22 Jul 2011 10:19:18 -0700
Subject: documentation/dev-manual/dev-manual-newbie.xml: edits to tracking
 bugs section.

(From yocto-docs rev: 7a4487394f14214c287247020b3abda3c3b6cfde)

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 | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'documentation')

diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index f1557aa396..ffcbe8b537 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -475,7 +475,8 @@
             So, for example, a valid way to refer to a defect when creating a commit comment 
             would be <filename>[YOCTO 1011]</filename>.   
             This convention becomes important if you are submitting patches against the Yocto Project 
-            code itself (see the next section “How to Submit a Change”).</para></listitem>
+            code itself.
+            See the following section for more information.</para></listitem>
         <listitem><para>Defects for Yocto Project fall into one of four classifications:  Yocto Projects, 
             Infrastructure, Poky, and Yocto Metadata Layers.</para></listitem>
     </itemizedlist>
-- 
cgit v1.2.3-54-g00ecf