From d09132d13036444bb48caac78bc942e28104ee02 Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Wed, 19 Oct 2022 14:41:40 +0200 Subject: [PATCH] manuals: fix misc typos (From yocto-docs rev: 988efd0d1663e4369043c5b53d7e1dcd9e54d3cd) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/dev-manual/common-tasks.rst | 2 +- documentation/dev-manual/start.rst | 4 ++-- documentation/migration-guides/release-notes-4.0.4.rst | 2 +- documentation/overview-manual/concepts.rst | 2 +- documentation/ref-manual/classes.rst | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst index 0d4e814f66..53e7686633 100644 --- a/documentation/dev-manual/common-tasks.rst +++ b/documentation/dev-manual/common-tasks.rst @@ -2124,7 +2124,7 @@ removed later when a recipe is either modified or removed. Thus, the sysroot is able to remain free from stale files. A subset of the files installed by the :ref:`ref-tasks-install` task are -used by the :ref:`ref-tasks-populate_sysroot` task as defined by the the +used by the :ref:`ref-tasks-populate_sysroot` task as defined by the :term:`SYSROOT_DIRS` variable to automatically populate the sysroot. It is possible to modify the list of directories that populate the sysroot. The following example shows how you could add the ``/opt`` directory to diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst index 499c3f8394..6816ce5846 100644 --- a/documentation/dev-manual/start.rst +++ b/documentation/dev-manual/start.rst @@ -497,8 +497,8 @@ your Yocto Project build host: launch your WSL distribution just like any other application. 6. *Optimize your WSLv2 storage often:* Due to the way storage is - handled on WSLv2, the storage space used by the undelying Linux - distribution is not reflected immedately, and since BitBake heavily + handled on WSLv2, the storage space used by the underlying Linux + distribution is not reflected immediately, and since BitBake heavily uses storage, after several builds, you may be unaware you are running out of space. WSLv2 uses a VHDX file for storage, this issue can be easily avoided by manually optimizing this file often, this diff --git a/documentation/migration-guides/release-notes-4.0.4.rst b/documentation/migration-guides/release-notes-4.0.4.rst index c615b83186..43f92cae84 100644 --- a/documentation/migration-guides/release-notes-4.0.4.rst +++ b/documentation/migration-guides/release-notes-4.0.4.rst @@ -95,7 +95,7 @@ Fixes in Yocto-4.0.4 - linux-yocto/5.15: update genericx86* machines to v5.15.59 - linux-yocto/5.15: update to v5.15.62 - linux-yocto: Fix COMPATIBLE_MACHINE regex match -- linux-yocto: prepend the the value with a space when append to KERNEL_EXTRA_ARGS +- linux-yocto: prepend the value with a space when append to KERNEL_EXTRA_ARGS - lttng-modules: fix 5.19+ build - lttng-modules: fix build against mips and v5.19 kernel - lttng-modules: fix build for kernel 5.10.137 diff --git a/documentation/overview-manual/concepts.rst b/documentation/overview-manual/concepts.rst index a978e2cd7d..75eb872b32 100644 --- a/documentation/overview-manual/concepts.rst +++ b/documentation/overview-manual/concepts.rst @@ -1431,7 +1431,7 @@ toolchain construction and use. :width: 100% Most of the work occurs on the Build Host. This is the machine used to -build images and generally work within the the Yocto Project +build images and generally work within the Yocto Project environment. When you run :term:`BitBake` to create an image, the OpenEmbedded build system uses the host ``gcc`` compiler to bootstrap a diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst index 21b50f94bd..cd5a51695b 100644 --- a/documentation/ref-manual/classes.rst +++ b/documentation/ref-manual/classes.rst @@ -1335,7 +1335,7 @@ device trees, a U-boot script, a Initramfs bundle and a RAM disk into a single FIT image. In theory, a FIT image can support any number of kernels, U-boot scripts, Initramfs bundles, RAM disks and device-trees. However, ``kernel-fitimage`` currently only supports -limited usescases: just one kernel image, an optional U-boot script, +limited usecases: just one kernel image, an optional U-boot script, an optional Initramfs bundle, an optional RAM disk, and any number of device tree.