summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-dev/concepts-appx.rst
diff options
context:
space:
mode:
authorMichael Opdenacker <michael.opdenacker@bootlin.com>2022-03-29 08:46:15 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-06-27 14:55:08 +0100
commitd9adf28c10d4a28538e2f90b97dd8949f28815a6 (patch)
tree7f1958f696697e52fc848cd398fb53f3c650b3a9 /documentation/kernel-dev/concepts-appx.rst
parent0d1d3afa8a09e08b65db8eaa2813bc5621d34806 (diff)
downloadpoky-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.rst2
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
117team's Yocto Linux kernel development strategy. It is the Yocto Project 117team's Yocto Linux kernel development strategy. It is the Yocto Project
118team's policy to not back-port minor features to the released Yocto 118team's policy to not back-port minor features to the released Yocto
119Linux kernel. They only consider back-porting significant technological 119Linux kernel. They only consider back-porting significant technological
120jumps - and, that is done after a complete gap analysis. The reason 120jumps --- and, that is done after a complete gap analysis. The reason
121for this policy is that back-porting any small to medium sized change 121for this policy is that back-porting any small to medium sized change
122from an evolving Linux kernel can easily create mismatches, 122from an evolving Linux kernel can easily create mismatches,
123incompatibilities and very subtle errors. 123incompatibilities and very subtle errors.