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/concepts-appx.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/concepts-appx.rst')
-rw-r--r-- | documentation/kernel-dev/concepts-appx.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/kernel-dev/concepts-appx.rst b/documentation/kernel-dev/concepts-appx.rst index b3a2f3abbf..63c5124a57 100644 --- a/documentation/kernel-dev/concepts-appx.rst +++ b/documentation/kernel-dev/concepts-appx.rst | |||
@@ -117,7 +117,7 @@ upstream Linux kernel development and are managed by the Yocto Project | |||
117 | team's Yocto Linux kernel development strategy. It is the Yocto Project | 117 | team's Yocto Linux kernel development strategy. It is the Yocto Project |
118 | team's policy to not back-port minor features to the released Yocto | 118 | team's policy to not back-port minor features to the released Yocto |
119 | Linux kernel. They only consider back-porting significant technological | 119 | Linux kernel. They only consider back-porting significant technological |
120 | jumps - and, that is done after a complete gap analysis. The reason | 120 | jumps --- and, that is done after a complete gap analysis. The reason |
121 | for this policy is that back-porting any small to medium sized change | 121 | for this policy is that back-porting any small to medium sized change |
122 | from an evolving Linux kernel can easily create mismatches, | 122 | from an evolving Linux kernel can easily create mismatches, |
123 | incompatibilities and very subtle errors. | 123 | incompatibilities and very subtle errors. |