summaryrefslogtreecommitdiffstats
path: root/documentation/bsp-guide
diff options
context:
space:
mode:
authorQuentin Schulz <foss@0leil.net>2021-12-06 16:04:01 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-12-13 23:31:34 +0000
commite71983bc7dba65df6273faaad92c5a43afded0ff (patch)
treeb5882d468d58514fdf0e93a24c03fb916be63958 /documentation/bsp-guide
parent99474e0d681cc9beb3604f214884054b3aec38a1 (diff)
downloadpoky-e71983bc7dba65df6273faaad92c5a43afded0ff.tar.gz
make the documentation a bit more inclusive
Except the name of variables which can't be changed only in the documentation for obvious reasons and workflow or developement explanations around the use of the "master" branch which cannot be replaced with "development" branch instead, most of the non-inclusive words that appear in https://inclusivenaming.org/word-lists/tier-1/ should have been replaced in this patch. (From yocto-docs rev: 2755f35060084f7af356091de9dc144f85530fe2) Signed-off-by: Quentin Schulz <foss+yocto@0leil.net> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/bsp-guide')
-rw-r--r--documentation/bsp-guide/bsp.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/documentation/bsp-guide/bsp.rst b/documentation/bsp-guide/bsp.rst
index 65652ff898..f8d38ca484 100644
--- a/documentation/bsp-guide/bsp.rst
+++ b/documentation/bsp-guide/bsp.rst
@@ -1121,12 +1121,12 @@ list describes them in order of preference:
1121 how to use these variables. 1121 how to use these variables.
1122 1122
1123 If you build as you normally would, without specifying any recipes in 1123 If you build as you normally would, without specifying any recipes in
1124 the :term:`LICENSE_FLAGS_WHITELIST`, the build stops and provides you 1124 the :term:`LICENSE_FLAGS_WHITELIST` variable, the build stops and provides
1125 with the list of recipes that you have tried to include in the image 1125 you with the list of recipes that you have tried to include in the image
1126 that need entries in the :term:`LICENSE_FLAGS_WHITELIST`. Once you enter 1126 that need entries in the :term:`LICENSE_FLAGS_WHITELIST` variable. Once you
1127 the appropriate license flags into the whitelist, restart the build 1127 enter the appropriate license flags into it, restart the build to continue
1128 to continue where it left off. During the build, the prompt will not 1128 where it left off. During the build, the prompt will not appear again since
1129 appear again since you have satisfied the requirement. 1129 you have satisfied the requirement.
1130 1130
1131 Once the appropriate license flags are on the white list in the 1131 Once the appropriate license flags are on the white list in the
1132 :term:`LICENSE_FLAGS_WHITELIST` variable, you can build the encumbered 1132 :term:`LICENSE_FLAGS_WHITELIST` variable, you can build the encumbered