1 files changed, 22 insertions, 11 deletions

diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml
index 1edc9ea238..49166e15bf 100644
--- a/documentation/ref-manual/usingpoky.xml
+++ b/documentation/ref-manual/usingpoky.xml
@@ -271,12 +271,18 @@
     <section id='usingpoky-debugging-buildfile'>
         <title>Building with No Dependencies</title>
         <para>
-            If you really want to build a specific <filename>.bb</filename> file, you can use
-            the command form <filename>bitbake -b &lt;somepath/somefile.bb&gt;</filename>.
-            This command form does not check for dependencies so you should use it
-            only when you know its dependencies already exist.
-            You can also specify fragments of the filename.
-            In this case, BitBake checks for a unique match.
+            To build a specific recipe (<filename>.bb</filename> file),
+            you can use the following command form:
+            <literallayout class='monospaced'>
+     $ bitbake -b &lt;somepath/somerecipe.bb&gt;
+            </literallayout>
+            This command form does not check for dependencies.
+            Consequently, you should use it
+            only when you know dependencies already exist.
+            <note>
+                You can also specify fragments of the filename.
+                In this case, BitBake checks for a unique match.
+            </note>
         </para>
     </section>
 
@@ -284,11 +290,16 @@
         <title>Variables</title>
         <para>
             You can use the <filename>-e</filename> BitBake option to
-            display the resulting environment for a configuration
-            when you do not specify a package or for a specific package when
-            you do specify the package.
-            If you want to show the environment resulting from parsing a single
-            recipe, use the <filename>-b recipename</filename> form.
+            display the parsing environment for a configuration.
+            The following displays the general parsing environment:
+            <literallayout class='monospaced'>
+     $ bitbake -e
+            </literallayout>
+            This next example shows the parsing environment for a specific
+            recipe:
+            <literallayout class='monospaced'>
+     $ bitbake -e &lt;recipename&gt;
+            </literallayout>
         </para>
     </section>