docs: remove 'thus', fix some phrasing #16559
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
|
|
Conduitry
approved these changes
Aug 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#16550 made various 'corrections', some of which made sense ('server-side rendering' should always be hyphenated), others less so. Our docs strive for a conversational tone, in which colloquialisms (such as 'as such' for 'therefore') are preferable to stilted words like 'thus' which just don't occur in spoken English and make everything sound clunky. Nevertheless this PR tries to find a balance between them, while fixing some of the awkward phrasing.
Some usages of 'as such' were, I would argue, perfectly fine. For example in the context of
'as such' expands to
unless you take the overly prescriptive and not-universally-agreed upon view that 'such' in this context can only refer to a noun.
In a programming context, 'deprecated' is most commonly used as a status rather than an action, so 'are deprecated' doesn't need to be changed to 'have been deprecated' which makes things less consistent.