summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/start.rst
diff options
context:
space:
mode:
authorMichael Opdenacker <michael.opdenacker@bootlin.com>2022-05-04 14:57:51 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-05-10 12:52:34 +0100
commiteae7c2a0c277c764a72073cdce1cdb2eb1fd1b9a (patch)
treefc3b2691dece36a13abc2892aea921d1dc601466 /documentation/dev-manual/start.rst
parente3d64415eddb7c0a5c13a2a91611204c8abfbedb (diff)
downloadpoky-eae7c2a0c277c764a72073cdce1cdb2eb1fd1b9a.tar.gz
manuals: fix name capitalization issues
- Using "BitBake" instead of "Bitbake" or "bitbake", aligning with the title of the "BitBake User Manual". - Using "OpenEmbedded" instead of "Openembedded" - Using "Python" instead of "python" (From yocto-docs rev: 0b893e2a15aefedd7100445fc9d7eeed07b6afc6) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/start.rst')
-rw-r--r--documentation/dev-manual/start.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst
index 96fabac1aa..8cf3ebe316 100644
--- a/documentation/dev-manual/start.rst
+++ b/documentation/dev-manual/start.rst
@@ -496,7 +496,7 @@ your Yocto Project build host:
496 496
4976. *Optimize your WSLv2 storage often:* Due to the way storage is 4976. *Optimize your WSLv2 storage often:* Due to the way storage is
498 handled on WSLv2, the storage space used by the undelying Linux 498 handled on WSLv2, the storage space used by the undelying Linux
499 distribution is not reflected immedately, and since bitbake heavily 499 distribution is not reflected immedately, and since BitBake heavily
500 uses storage, after several builds, you may be unaware you are 500 uses storage, after several builds, you may be unaware you are
501 running out of space. WSLv2 uses a VHDX file for storage, this issue 501 running out of space. WSLv2 uses a VHDX file for storage, this issue
502 can be easily avoided by manually optimizing this file often, this 502 can be easily avoided by manually optimizing this file often, this