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/kernel-dev/advanced.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/kernel-dev/advanced.rst')
-rw-r--r-- | documentation/kernel-dev/advanced.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/kernel-dev/advanced.rst b/documentation/kernel-dev/advanced.rst index b5290b61b3..b16b3e0517 100644 --- a/documentation/kernel-dev/advanced.rst +++ b/documentation/kernel-dev/advanced.rst | |||
@@ -183,7 +183,7 @@ the structure: | |||
183 | order to define a base kernel policy or major kernel type to be | 183 | order to define a base kernel policy or major kernel type to be |
184 | reused across multiple BSPs, place the file in ``ktypes`` directory. | 184 | reused across multiple BSPs, place the file in ``ktypes`` directory. |
185 | 185 | ||
186 | These distinctions can easily become blurred - especially as out-of-tree | 186 | These distinctions can easily become blurred --- especially as out-of-tree |
187 | features slowly merge upstream over time. Also, remember that how the | 187 | features slowly merge upstream over time. Also, remember that how the |
188 | description files are placed is a purely logical organization and has no | 188 | description files are placed is a purely logical organization and has no |
189 | impact on the functionality of the kernel Metadata. There is no impact | 189 | impact on the functionality of the kernel Metadata. There is no impact |