pw_build: Use inclusive language
Bug: 386
Change-Id: I952de804bc2f70319669646900be90430bcf4da6
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/46681
Commit-Queue: Auto-Submit <auto-submit@pigweed.google.com.iam.gserviceaccount.com>
Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com>
Reviewed-by: Ewout van Bekkum <ewout@google.com>
diff --git a/pw_build/docs.rst b/pw_build/docs.rst
index c2fe2f5..db3725d 100644
--- a/pw_build/docs.rst
+++ b/pw_build/docs.rst
@@ -146,7 +146,7 @@
any outputs. Sometimes scripts run in a build do not directly produce output
files, but GN requires that all actions have an output. ``pw_python_action``
solves this by accepting a boolean ``stamp`` argument which tells it to create a
-dummy output file for the action.
+placeholder output file for the action.
**Arguments**
@@ -158,7 +158,7 @@
* ``capture_output``: Optional boolean. If true, script output is hidden unless
the script fails with an error. Defaults to true.
* ``stamp``: Optional variable indicating whether to automatically create a
- dummy output file for the script. This allows running scripts without
+ placeholder output file for the script. This allows running scripts without
specifying ``outputs``. If ``stamp`` is true, a generic output file is
used. If ``stamp`` is a file path, that file is used as a stamp file. Like any
output file, ``stamp`` must be in the build directory. Defaults to false.