diff options
author | Quentin Schulz <foss@0leil.net> | 2020-09-17 01:59:02 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-09-17 10:09:36 +0100 |
commit | 177aee09fec494e8827a03cc98ba989f4acd459d (patch) | |
tree | 8cd19e638c3e5ed11b17a17b7da9a98d54c2b898 /documentation/what-i-wish-id-known.rst | |
parent | 528cdb7cd55184422b0b5361a7b6ab81314c1ba2 (diff) | |
download | poky-177aee09fec494e8827a03cc98ba989f4acd459d.tar.gz |
sphinx: fix a few typos or missing/too many words
(From yocto-docs rev: 744b74b3420ae475a566307e03e0b098986773e4)
Signed-off-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/what-i-wish-id-known.rst')
-rw-r--r-- | documentation/what-i-wish-id-known.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/what-i-wish-id-known.rst b/documentation/what-i-wish-id-known.rst index 67bf84e07f..1afc2eff97 100644 --- a/documentation/what-i-wish-id-known.rst +++ b/documentation/what-i-wish-id-known.rst | |||
@@ -85,7 +85,7 @@ contact us with other suggestions. | |||
85 | pinpoint where trouble is occurring and how the build is breaking. The | 85 | pinpoint where trouble is occurring and how the build is breaking. The |
86 | workflow breaks down into the following steps: | 86 | workflow breaks down into the following steps: |
87 | 87 | ||
88 | #. Fetch – get the sourcecode | 88 | #. Fetch – get the source code |
89 | #. Extract – unpack the sources | 89 | #. Extract – unpack the sources |
90 | #. Patch – apply patches for bug fixes and new capability | 90 | #. Patch – apply patches for bug fixes and new capability |
91 | #. Configure – set up your environment specifications | 91 | #. Configure – set up your environment specifications |
@@ -105,7 +105,7 @@ contact us with other suggestions. | |||
105 | You can use the "-g" option with BitBake to generate this graph. When you | 105 | You can use the "-g" option with BitBake to generate this graph. When you |
106 | start a build and the build breaks, you could see packages you have no clue | 106 | start a build and the build breaks, you could see packages you have no clue |
107 | about or have any idea why the build system has included them. The | 107 | about or have any idea why the build system has included them. The |
108 | dependency graph can clarify that confustion. You can learn more about | 108 | dependency graph can clarify that confusion. You can learn more about |
109 | dependency graphs and how to generate them in the | 109 | dependency graphs and how to generate them in the |
110 | :ref:`bitbake-user-manual/bitbake-user-manual-intro:generating dependency | 110 | :ref:`bitbake-user-manual/bitbake-user-manual-intro:generating dependency |
111 | graphs` section in the BitBake User Manual. | 111 | graphs` section in the BitBake User Manual. |