Corrections and exceptions to pass woke check #421
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lvoytek
approved these changes
Dec 5, 2025
Member
lvoytek
left a comment
lvoytek
left a comment
There was a problem hiding this comment.
LGTM! Similar to the process I went through for cleaning up the docs several years ago
s-makin
commented
Dec 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Although we didn't have many, this PR changes words that trigger the woke check, and adds individual spellexceptions where I can't reasonably change the word itself because we're reflecting the upstream choices in language. This avoids putting these terms on the exception list where they'd be blanket-ignored.
In the case of multipath, I've selectively changed "blacklist" to "blocklist" in the body text, and "whitelist" to "allowlist". This does create a conflict with the terminology used in the code examples, which I haven't changed. However, I think in this case any reasonable person would understand what I've done here.
Let me know if you disagree - I'm not going to directly merge this PR as I'm happy to be contradicted on any of my choices here if you'd like me to go in a different direction.
Checklist
Additional Notes (Optional)
Add any extra information or context that reviewers may need to know. This could include testing instructions,
screenshots, or links to related discussions.
Thank you for contributing to the Ubuntu Server documentation!