diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2024-02-09 17:48:06 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2024-02-24 16:13:28 +0000 |
commit | 025386d53ceef681d7e829ad184b6850af55619c (patch) | |
tree | 720a253731442d2b84ed443c8b143fdc23dfc493 /documentation/dev-manual/new-recipe.rst | |
parent | 67efdd63c2b1d94bdc4a8da2895b3f7186e7a7c4 (diff) | |
download | poky-025386d53ceef681d7e829ad184b6850af55619c.tar.gz |
manuals: suppress excess use of "following" word
To simplify the style, replace "Following is" and "Following are"
by "here is" and "here are", sounding more natural.
In some cases, also go further by simplifying "Here are/is xxx"
by "xxx are/is" when the "are" or "is" are not two far at
the end of the sentence.
In some cases too, completely remove the sentence, when
it's redundant with the preceding title.
(From yocto-docs rev: 52ba6bb16c73cbc2c0e77496d5226c49bce786f5)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
CC: Daniel Ammann <daniel.ammann@bytesatwork.ch>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/new-recipe.rst')
-rw-r--r-- | documentation/dev-manual/new-recipe.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/dev-manual/new-recipe.rst b/documentation/dev-manual/new-recipe.rst index 2c1033eb35..61fc2eb122 100644 --- a/documentation/dev-manual/new-recipe.rst +++ b/documentation/dev-manual/new-recipe.rst | |||
@@ -100,7 +100,7 @@ command:: | |||
100 | 100 | ||
101 | Running ``recipetool create -o OUTFILE`` creates the base recipe and | 101 | Running ``recipetool create -o OUTFILE`` creates the base recipe and |
102 | locates it properly in the layer that contains your source files. | 102 | locates it properly in the layer that contains your source files. |
103 | Following are some syntax examples: | 103 | Here are some syntax examples: |
104 | 104 | ||
105 | - Use this syntax to generate a recipe based on source. Once generated, | 105 | - Use this syntax to generate a recipe based on source. Once generated, |
106 | the recipe resides in the existing source code layer:: | 106 | the recipe resides in the existing source code layer:: |
@@ -1232,7 +1232,7 @@ inherit the :ref:`ref-classes-autotools` class, which contains the definitions | |||
1232 | of all the steps needed to build an Autotool-based application. The result of | 1232 | of all the steps needed to build an Autotool-based application. The result of |
1233 | the build is automatically packaged. And, if the application uses NLS for | 1233 | the build is automatically packaged. And, if the application uses NLS for |
1234 | localization, packages with local information are generated (one package per | 1234 | localization, packages with local information are generated (one package per |
1235 | language). Following is one example: (``hello_2.3.bb``):: | 1235 | language). Here is one example: (``hello_2.3.bb``):: |
1236 | 1236 | ||
1237 | SUMMARY = "GNU Helloworld application" | 1237 | SUMMARY = "GNU Helloworld application" |
1238 | SECTION = "examples" | 1238 | SECTION = "examples" |
@@ -1285,7 +1285,7 @@ Splitting an Application into Multiple Packages | |||
1285 | You can use the variables :term:`PACKAGES` and :term:`FILES` to split an | 1285 | You can use the variables :term:`PACKAGES` and :term:`FILES` to split an |
1286 | application into multiple packages. | 1286 | application into multiple packages. |
1287 | 1287 | ||
1288 | Following is an example that uses the ``libxpm`` recipe. By default, | 1288 | Here is an example that uses the ``libxpm`` recipe. By default, |
1289 | this recipe generates a single package that contains the library along | 1289 | this recipe generates a single package that contains the library along |
1290 | with a few binaries. You can modify the recipe to split the binaries | 1290 | with a few binaries. You can modify the recipe to split the binaries |
1291 | into separate packages:: | 1291 | into separate packages:: |
@@ -1510,7 +1510,7 @@ in the BitBake User Manual. | |||
1510 | when you make the assignment, but this is not generally needed. | 1510 | when you make the assignment, but this is not generally needed. |
1511 | 1511 | ||
1512 | - *Quote All Assignments ("value"):* Use double quotes around values in | 1512 | - *Quote All Assignments ("value"):* Use double quotes around values in |
1513 | all variable assignments (e.g. ``"value"``). Following is an example:: | 1513 | all variable assignments (e.g. ``"value"``). Here is an example:: |
1514 | 1514 | ||
1515 | VAR1 = "${OTHERVAR}" | 1515 | VAR1 = "${OTHERVAR}" |
1516 | VAR2 = "The version is ${PV}" | 1516 | VAR2 = "The version is ${PV}" |