1 files changed, 9 insertions, 4 deletions

diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml
index 8c3ceb7210..7e8d528897 100644
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -106,7 +106,11 @@
             configuration files.
             These example files are used as a basis for creating actual
             configuration files when you source the build environment
-            script <filename>oe-init-build-env</filename>.
+            script 
+            (i.e.
+            <link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link>
+            or
+            <link linkend='structure-memres-core-script'><filename>oe-init-build-env-memres</filename></link>).
         </para>
 
         <para>
@@ -119,14 +123,15 @@
             and <filename>bblayers.conf</filename> configuration files.
             These default configuration files are created only if versions
             do not already exist in the Build Directory at the time you
-            source the <filename>oe-init-build-env</filename> script.
+            source the build environment setup script.
         </para>
 
         <para>
             Because the Poky repository is fundamentally an aggregation of
             existing repositories, some users might be familiar with running
-            the <filename>oe-init-build-env</filename> script in the context of
-            separate OpenEmbedded-Core and BitBake repositories rather than a
+            the <filename>&OE_INIT_FILE;</filename> or 
+            <filename>oe-init-build-env-memres</filename> script in the context 
+            of separate OpenEmbedded-Core and BitBake repositories rather than a
             single Poky repository.
             This discussion assumes the script is executed from within a cloned
             or unpacked version of Poky.