summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml3
1 files changed, 2 insertions, 1 deletions
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 @@
475 So, for example, a valid way to refer to a defect when creating a commit comment 475 So, for example, a valid way to refer to a defect when creating a commit comment
476 would be <filename>[YOCTO 1011]</filename>. 476 would be <filename>[YOCTO 1011]</filename>.
477 This convention becomes important if you are submitting patches against the Yocto Project 477 This convention becomes important if you are submitting patches against the Yocto Project
478 code itself (see the next section “How to Submit a Change”).</para></listitem> 478 code itself.
479 See the following section for more information.</para></listitem>
479 <listitem><para>Defects for Yocto Project fall into one of four classifications: Yocto Projects, 480 <listitem><para>Defects for Yocto Project fall into one of four classifications: Yocto Projects,
480 Infrastructure, Poky, and Yocto Metadata Layers.</para></listitem> 481 Infrastructure, Poky, and Yocto Metadata Layers.</para></listitem>
481 </itemizedlist> 482 </itemizedlist>