1
0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 12:29:55 +00:00

sphinx: fix a few typos or missing/too many words

(From yocto-docs rev: 744b74b3420ae475a566307e03e0b098986773e4)

Signed-off-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Quentin Schulz
2020-09-17 01:59:02 +02:00
committed by Richard Purdie
parent 528cdb7cd5
commit 177aee09fe
5 changed files with 16 additions and 18 deletions
@@ -787,7 +787,7 @@ Build Directory's hierarchy:
- :term:`PN`: The name of the recipe used
to build the package. This variable can have multiple meanings.
However, when used in the context of input files, ``PN`` represents
the the name of the recipe.
the name of the recipe.
- :term:`WORKDIR`: The location
where the OpenEmbedded build system builds a recipe (i.e. does the
@@ -1125,8 +1125,7 @@ build system has created the final image output files.
.. note::
The entire image generation process is run under
Pseudo
. Running under Pseudo ensures that the files in the root filesystem
Pseudo. Running under Pseudo ensures that the files in the root filesystem
have correct ownership.
.. _sdk-generation-dev-environment:
@@ -1736,8 +1735,7 @@ objective of making native or cross packages relocatable.
.. note::
Both native and cross packages run on the
build host
. However, cross packages generate output for the target
build host. However, cross packages generate output for the target
architecture.
The checksum therefore needs to exclude ``WORKDIR``. The simplistic
@@ -134,7 +134,7 @@ Project:
- *License Manifest:* The Yocto Project provides a :ref:`license
manifest <dev-manual/dev-manual-common-tasks:maintaining open source license compliance during your product's lifecycle>`
for review by people who need to track the use of open source
licenses (e.g.legal teams).
licenses (e.g. legal teams).
.. _gs-challenges:
@@ -540,7 +540,7 @@ targets:
You can find the Matchbox source in the Yocto Project
:yocto_git:`Source Repositories <>`.
- *Opkg* Open PacKaGe management (opkg) is a lightweight package
- *Opkg:* Open PacKaGe management (opkg) is a lightweight package
management system based on the itsy package (ipkg) management system.
Opkg is written in C and resembles Advanced Package Tool (APT) and
Debian Package (dpkg) in operation.
@@ -655,7 +655,7 @@ Project.
virtualization technology.
For information on how to set up a Build Host with WSLv2, see the
":ref:dev-manual/dev-manual-start:setting up to use windows subsystem for linux (wslv2)`"
":ref:`dev-manual/dev-manual-start:setting up to use windows subsystem for linux (wslv2)`"
section in the Yocto Project Development Tasks Manual.
- *Toaster:* Regardless of what your Build Host is running, you can use
@@ -743,7 +743,7 @@ and Fall. For more information on the Yocto Project release schedule and
cadence, see the ":doc:`../ref-manual/ref-release-process`" chapter in the
Yocto Project Reference Manual.
Much has been said about Poky being a "default configuration." A default
Much has been said about Poky being a "default configuration". A default
configuration provides a starting image footprint. You can use Poky out
of the box to create an image ranging from a shell-accessible minimal
image all the way up to a Linux Standard Base-compliant image that uses