docs: use alex
to ensure we're using inclusive language
#469
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🧰 Changes
This PR brings
alex
into our docs build process to ensure we're using inclusive language in our writing. This now is included in ourpretest
script and will fail CI if there is any potentially insensitive/inconsiderate language in this repo's Markdown files.In terms of config, it's pretty light:
profanitySureness
setting ever-so-slightly (it was flagging the words "execute" and "period" as profanity, for example)CHANGELOG.md
since that's auto-generatedWhen I finally get around to adding shared community files for our org, we should definitely include this.
🧬 QA & Testing
Do the language tweaks make sense? And is the build process setup sound?