documentation: dev-manual - wording change to remove ambiguity.

(From yocto-docs rev: 01fc1959efa85fdba17beec4a5c565108c6ab68a)

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

diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index ebae72e820124e5f9036b60fcccebc21b2630498..6beffc2f9459d433ac3f350a0658c7bed6f92511 100644 (file)
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -992,7 +992,8 @@
         should almost always provide a more detailed description of what you did (i.e.
         the body of the commit message).
         The only exceptions for not providing a detailed description would be if your 
-        change is a simple, self-explanatory change that needs no description.
+        change is a simple, self-explanatory change that needs no further description 
+        beyond the summary.
         Here are the guidelines for composing a commit message:
         <itemizedlist>
             <listitem><para>Provide a single-line, short summary of the change.