From d02e56fd14026e2f51665631a50901fc568c731a Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Wed, 24 Aug 2011 07:58:32 -0700
Subject: documentation: Changes to Paul Eggleton's edits for various manuals.

Paul sent me a bunch of minor edits and technical corrections
for the ADT, BSP, Development, and YP reference manual.
Most changes were taken as he submitted them.  However, some
formatting conventions were not followed in the commits he made
to yocto-docs/paule/docs2.  After merging them to my yocto-docs/master
branch I fixed some issues.

(From yocto-docs rev: 93f4ea2dee976448f623953e801a80d59736450a)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/poky-ref-manual/extendpoky.xml | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

(limited to 'documentation/poky-ref-manual/extendpoky.xml')

diff --git a/documentation/poky-ref-manual/extendpoky.xml b/documentation/poky-ref-manual/extendpoky.xml
index fdccbacd68..db15fc6178 100644
--- a/documentation/poky-ref-manual/extendpoky.xml
+++ b/documentation/poky-ref-manual/extendpoky.xml
@@ -1004,7 +1004,7 @@
 
         <para>
             Finally, don't forget to 'bump' the 
-            <glossterm><link linkend='var-PR'>PR</link></glossterm> value in the same recipe since 
+            <filename><link linkend='var-PR'>PR</link></filename> value in the same recipe since 
             the resulting packages have changed.
         </para>
     </section>
@@ -1015,7 +1015,7 @@
         <para>
             The license of an upstream project might change in the future. In order to prevent these changes
             going unnoticed, the Yocto Project provides a 
-            <glossterm><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link></glossterm>
+            <filename><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link></filename>
             variable to track changes to the license text. The checksums are validated at the end of the
             configure step, and if the checksums do not match, the build will fail.
         </para>
@@ -1060,8 +1060,8 @@
                 of <filename>S</filename>.
             </para>
             <para>
-                Note that this variable is mandatory for all recipes, unless the LICENSE variable is set to
-                "CLOSED".
+                Note that this variable is mandatory for all recipes, unless the 
+                <filename>LICENSE</filename> variable is set to "CLOSED".
             </para>
         </section>
 
@@ -1073,12 +1073,13 @@
                 important files that contain the license text for the source code. 
                 It is possible to specify a checksum for an entire file, or a specific section of a
                 file (specified by beginning and ending line numbers with the "beginline" and "endline"
-                parameters respectively). The latter is useful for source files with license notice header,
-                README documents, etc.
+                parameters respectively). 
+                The latter is useful for source files with a license notice header,
+                README documents, and so forth.
                 If you do not use the "beginline" parameter, then it is assumed that the text begins on the 
                 first line of the file. 
                 Similarly, if you do not use the "endline" parameter, it is assumed that the license text 
-                ends as the last line of the file. 
+                ends with the last line of the file. 
             </para>
 
             <para>
-- 
cgit v1.2.3-54-g00ecf