summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
diff options
context:
space:
mode:
authorMichael Opdenacker <michael.opdenacker@bootlin.com>2021-05-06 19:17:57 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-05-13 11:28:34 +0100
commitd4a82b30b7d3622d5e3101aeb333bbdb31622176 (patch)
treead8ebb64f0363ad685ad6d6163cc4bf2ce4f535f /documentation/dev-manual
parentf3540fc691c12aca637ddea71bd0090ddcc40e19 (diff)
downloadpoky-d4a82b30b7d3622d5e3101aeb333bbdb31622176.tar.gz
manuals: reduce verbosity related to "the following" expression
(From yocto-docs rev: da9d1cfb5c084d172eff3cb10ec3631dd8266260) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r--documentation/dev-manual/common-tasks.rst10
-rw-r--r--documentation/dev-manual/qemu.rst6
2 files changed, 8 insertions, 8 deletions
diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst
index 4200b8dd61..5c3fc41772 100644
--- a/documentation/dev-manual/common-tasks.rst
+++ b/documentation/dev-manual/common-tasks.rst
@@ -2513,7 +2513,7 @@ chapter of the BitBake User Manual.
2513 syntax, although access to OpenEmbedded variables and internal 2513 syntax, although access to OpenEmbedded variables and internal
2514 methods are also available. 2514 methods are also available.
2515 2515
2516 The following is an example function from the ``sed`` recipe:: 2516 Here is an example function from the ``sed`` recipe::
2517 2517
2518 do_install () { 2518 do_install () {
2519 autotools_do_install 2519 autotools_do_install
@@ -7413,7 +7413,7 @@ The variable can contain multiple [one-line] metadata fields separated
7413by the literal sequence '\\n'. The separator can be redefined using the 7413by the literal sequence '\\n'. The separator can be redefined using the
7414variable flag ``separator``. 7414variable flag ``separator``.
7415 7415
7416The following is an example that adds two custom fields for ipk 7416Here is an example that adds two custom fields for ipk
7417packages:: 7417packages::
7418 7418
7419 PACKAGE_ADD_METADATA_IPK = "Vendor: CustomIpk\nGroup:Applications/Spreadsheets" 7419 PACKAGE_ADD_METADATA_IPK = "Vendor: CustomIpk\nGroup:Applications/Spreadsheets"
@@ -7844,7 +7844,7 @@ Build history information is kept in
7844``${``\ :term:`TOPDIR`\ ``}/buildhistory`` 7844``${``\ :term:`TOPDIR`\ ``}/buildhistory``
7845in the Build Directory as defined by the 7845in the Build Directory as defined by the
7846:term:`BUILDHISTORY_DIR` 7846:term:`BUILDHISTORY_DIR`
7847variable. The following is an example abbreviated listing: 7847variable. Here is an example abbreviated listing:
7848 7848
7849.. image:: figures/buildhistory.png 7849.. image:: figures/buildhistory.png
7850 :align: center 7850 :align: center
@@ -11058,7 +11058,7 @@ this function, you have to follow the following steps:
110583. Meta-spdxscanner provides several methods within the bbclass to create spdx files. 110583. Meta-spdxscanner provides several methods within the bbclass to create spdx files.
11059 Please choose one that you want to use and enable the spdx task. You have to 11059 Please choose one that you want to use and enable the spdx task. You have to
11060 add some config options in ``local.conf`` file in your :term:`Build 11060 add some config options in ``local.conf`` file in your :term:`Build
11061 Directory`. The following is an example showing how to generate spdx files 11061 Directory`. Here is an example showing how to generate spdx files
11062 during bitbake using the fossology-python.bbclass:: 11062 during bitbake using the fossology-python.bbclass::
11063 11063
11064 # Select fossology-python.bbclass. 11064 # Select fossology-python.bbclass.
@@ -11088,7 +11088,7 @@ package, by using the
11088variable. Using this variable also avoids QA errors when you use a 11088variable. Using this variable also avoids QA errors when you use a
11089non-common, non-CLOSED license in a recipe. 11089non-common, non-CLOSED license in a recipe.
11090 11090
11091The following is an example that uses the ``LICENSE.Abilis.txt`` file as 11091Here is an example that uses the ``LICENSE.Abilis.txt`` file as
11092the license from the fetched source:: 11092the license from the fetched source::
11093 11093
11094 NO_GENERIC_LICENSE[Firmware-Abilis] = "LICENSE.Abilis.txt" 11094 NO_GENERIC_LICENSE[Firmware-Abilis] = "LICENSE.Abilis.txt"
diff --git a/documentation/dev-manual/qemu.rst b/documentation/dev-manual/qemu.rst
index 2b6d3d76c7..f7366938dd 100644
--- a/documentation/dev-manual/qemu.rst
+++ b/documentation/dev-manual/qemu.rst
@@ -219,15 +219,15 @@ using an NFS server.
219 Should you need to start, stop, or restart the NFS share, you can use 219 Should you need to start, stop, or restart the NFS share, you can use
220 the following commands: 220 the following commands:
221 221
222 - The following command starts the NFS share:: 222 - To start the NFS share::
223 223
224 runqemu-export-rootfs start file-system-location 224 runqemu-export-rootfs start file-system-location
225 225
226 - The following command stops the NFS share:: 226 - To stop the NFS share::
227 227
228 runqemu-export-rootfs stop file-system-location 228 runqemu-export-rootfs stop file-system-location
229 229
230 - The following command restarts the NFS share:: 230 - To restart the NFS share::
231 231
232 runqemu-export-rootfs restart file-system-location 232 runqemu-export-rootfs restart file-system-location
233 233