diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2022-03-29 08:46:15 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-06-27 14:55:08 +0100 |
commit | d9adf28c10d4a28538e2f90b97dd8949f28815a6 (patch) | |
tree | 7f1958f696697e52fc848cd398fb53f3c650b3a9 /documentation/sdk-manual/extensible.rst | |
parent | 0d1d3afa8a09e08b65db8eaa2813bc5621d34806 (diff) | |
download | poky-d9adf28c10d4a28538e2f90b97dd8949f28815a6.tar.gz |
manuals: replace hyphens with em dashes
Fix some hyphens being improperly used as em dashes.
See https://www.grammarly.com/blog/hyphens-and-dashes/
Using em dashes may also allow Sphinx to hyphenate
and break lines in the best way.
Note that the first character after an em dash not
supposed to be capitalized, unless a specific
rule applies, typically when what follows is a proper noun.
Fix a few misuses of parentheses in following text.
(From yocto-docs rev: 5918f019f63f6e820b1168f4cc001faa1d1cdc6f)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/sdk-manual/extensible.rst')
-rw-r--r-- | documentation/sdk-manual/extensible.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/sdk-manual/extensible.rst b/documentation/sdk-manual/extensible.rst index 6bb262273d..ed9e43a2d8 100644 --- a/documentation/sdk-manual/extensible.rst +++ b/documentation/sdk-manual/extensible.rst | |||
@@ -252,7 +252,7 @@ command: | |||
252 | - *Left*: The left scenario in the figure represents a common | 252 | - *Left*: The left scenario in the figure represents a common |
253 | situation where the source code does not exist locally and needs | 253 | situation where the source code does not exist locally and needs |
254 | to be extracted. In this situation, the source code is extracted | 254 | to be extracted. In this situation, the source code is extracted |
255 | to the default workspace - you do not want the files in some | 255 | to the default workspace --- you do not want the files in some |
256 | specific location outside of the workspace. Thus, everything you | 256 | specific location outside of the workspace. Thus, everything you |
257 | need will be located in the workspace:: | 257 | need will be located in the workspace:: |
258 | 258 | ||
@@ -267,7 +267,7 @@ command: | |||
267 | - *Middle*: The middle scenario in the figure also represents a | 267 | - *Middle*: The middle scenario in the figure also represents a |
268 | situation where the source code does not exist locally. In this | 268 | situation where the source code does not exist locally. In this |
269 | case, the code is again upstream and needs to be extracted to some | 269 | case, the code is again upstream and needs to be extracted to some |
270 | local area - this time outside of the default workspace. | 270 | local area --- this time outside of the default workspace. |
271 | 271 | ||
272 | .. note:: | 272 | .. note:: |
273 | 273 | ||
@@ -302,7 +302,7 @@ command: | |||
302 | recipe for the code and places the recipe into the workspace. | 302 | recipe for the code and places the recipe into the workspace. |
303 | 303 | ||
304 | Because the extracted source code already exists, ``devtool`` does | 304 | Because the extracted source code already exists, ``devtool`` does |
305 | not try to relocate the source code into the workspace - only the | 305 | not try to relocate the source code into the workspace --- only the |
306 | new recipe is placed in the workspace. | 306 | new recipe is placed in the workspace. |
307 | 307 | ||
308 | Aside from a recipe folder, the command also creates an associated | 308 | Aside from a recipe folder, the command also creates an associated |