summaryrefslogtreecommitdiff
path: root/poky/documentation/ref-manual/terms.rst
diff options
context:
space:
mode:
Diffstat (limited to 'poky/documentation/ref-manual/terms.rst')
-rw-r--r--poky/documentation/ref-manual/terms.rst14
1 files changed, 7 insertions, 7 deletions
diff --git a/poky/documentation/ref-manual/terms.rst b/poky/documentation/ref-manual/terms.rst
index 3f18d3404e..cba514c345 100644
--- a/poky/documentation/ref-manual/terms.rst
+++ b/poky/documentation/ref-manual/terms.rst
@@ -88,11 +88,11 @@ universal, the list includes them just in case:
- Provide a directory path and specifically name the Build
Directory. Any intermediate folders in the pathname must exist.
This next example creates a Build Directory named
- ``YP-&POKYVERSION;`` within the existing directory ``mybuilds``:
+ ``YP-&DISTRO;`` within the existing directory ``mybuilds``:
.. code-block:: shell
- $ source poky/oe-init-build-env mybuilds/YP-&POKYVERSION;
+ $ source poky/oe-init-build-env mybuilds/YP-&DISTRO;
.. note::
@@ -357,13 +357,13 @@ universal, the list includes them just in case:
repository results in a local Git repository whose top-level folder
is also named "poky".
- While it is not recommended that you use tarball expansion to set up
+ While it is not recommended that you use tarball extraction to set up
the Source Directory, if you do, the top-level directory name of the
Source Directory is derived from the Yocto Project release tarball.
- For example, downloading and unpacking
- :yocto_dl:`/releases/yocto/&DISTRO_REL_TAG;/&YOCTO_POKY;.tar.bz2`
- results in a Source Directory whose root folder is named
- ``&YOCTO_POKY;``.
+ For example, downloading and unpacking poky tarballs from
+ :yocto_dl:`/releases/yocto/&DISTRO_REL_TAG;/`
+ results in a Source Directory whose root folder is named poky.
+
It is important to understand the differences between the Source
Directory created by unpacking a released tarball as compared to