documentation/poky-ref-manual: PN scrub

Checked and fixed all text surrounding the description and use
of the PN variable.  This variable can mean a recipe or a resulting
package depending on context.

(From yocto-docs rev: 7ac52f6b184670db9cdab7c205126b62c60b0d29)

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

1 files changed, 2 insertions, 2 deletions

diff --git a/documentation/poky-ref-manual/technical-details.xml b/documentation/poky-ref-manual/technical-details.xml
index aef1c2792d..ab41a06269 100644
--- a/documentation/poky-ref-manual/technical-details.xml
+++ b/documentation/poky-ref-manual/technical-details.xml
@@ -809,7 +809,7 @@
      LICENSE_FLAGS = "commercial"
             </literallayout>
             Here is a slightly more complicated example that contains both an
-            explicit package name and version (after variable expansion):
+            explicit recipe name and version (after variable expansion):
             <literallayout class='monospaced'>
      LICENSE_FLAGS = "license_${PN}_${PV}"
             </literallayout>
@@ -830,7 +830,7 @@
             <literallayout class='monospaced'>
      LICENSE_FLAGS_WHITELIST = "commercial_gst-plugins-ugly"
             </literallayout>
-                Likewise, to additionally enable the package containing
+                Likewise, to additionally enable the package built from the recipe containing
                 <filename>LICENSE_FLAGS = "license_${PN}_${PV}"</filename>, and assuming
                 that the actual recipe name was <filename>emgd_1.10.bb</filename>,
                 the following string would enable that package as well as