From 1c4a535dd83bf145c6487cd3fb545f6a9717ed14 Mon Sep 17 00:00:00 2001 From: "Robert P. J. Day" Date: Sat, 9 May 2026 14:44:05 -0400 Subject: [PATCH] What I Wish I'd KNown: Various pedantic cleanups Tweaks: - Update "Software Overview" link to go to "Technical Overview" - use proper capitalization for "Git" when referring to the product - numerous grammar adjustments to basic skills list (From yocto-docs rev: 9b440c5116828f131a304b77f5da8c98c0d27c62) Signed-off-by: Robert P. J. Day Signed-off-by: Antonin Godard (cherry picked from commit ffd69f11172c2b0d8f52bd967c7983220d133e0d) Signed-off-by: Antonin Godard Signed-off-by: Paul Barker --- documentation/what-i-wish-id-known.rst | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/documentation/what-i-wish-id-known.rst b/documentation/what-i-wish-id-known.rst index 60ed999b63..bc95663fa3 100644 --- a/documentation/what-i-wish-id-known.rst +++ b/documentation/what-i-wish-id-known.rst @@ -9,7 +9,7 @@ What I wish I'd known about Yocto Project .. note:: Before reading further, make sure you've taken a look at the - :yocto_home:`Software Overview` page which presents the + :yocto_home:`Technical Overview` page which presents the definitions for many of the terms referenced here. Also, know that some of the information here won't make sense now, but as you start developing, it is the information you'll want to keep close at hand. These are best known methods for @@ -22,8 +22,8 @@ known before embarking on their first build with Yocto Project. Feel free to contact us with other suggestions. #. **Use Git, not the tarball download:** - If you use git the software will be automatically updated with bug updates - because of how git works. If you download the tarball instead, you will need + If you use Git, the software will be automatically updated with bug updates + because of how Git works. If you download the tarball instead, you will need to be responsible for your own updates. #. **Get to know the layer index:** @@ -165,19 +165,19 @@ contact us with other suggestions. * deal with corporate proxies * add a package to an image - * understand the difference between a recipe and package - * build a package by itself and why that's useful + * understand the difference between a recipe and a package + * build a package by itself and understand why that's useful * find out what packages are created by a recipe * find out what files are in a package * find out what files are in an image - * add an ssh server to an image (enable transferring of files to target) + * add an SSH server to an image (enable transferring of files to target) * know the anatomy of a recipe * know how to create and use layers * find recipes (with the :oe_layerindex:`OpenEmbedded Layer index <>`) - * understand difference between machine and distro settings + * understand the difference between MACHINE and DISTRO settings * find and use the right BSP (machine) for your hardware - * find examples of distro features and know where to set them - * understanding the task pipeline and executing individual tasks + * find examples of DISTRO features and know where to set them + * understand the task pipeline and how to execute individual tasks * understand devtool and how it simplifies your workflow * improve build speeds with shared downloads and shared state cache * generate and understand a dependency graph