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
committerSteve Sakoman <steve@sakoman.com>2024-03-25 04:11:26 -1000
commit5b75b5cbcf48845d4c4f740ac53ec50db20285db (patch)
tree2211b4008728f19e0fcdc33c0d31cd8c765b9c33 /documentation/kernel-dev/concepts-appx.rst
parent3b7e3267042bf4e2355fde2821c9b6452a07990c (diff)
downloadpoky-5b75b5cbcf48845d4c4f740ac53ec50db20285db.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: a0d93ea1ddfdfbcde8dac3aa328307be778f9e3c) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Steve Sakoman <steve@sakoman.com>
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 910318e0f9..7b734a2a39 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.