Thanks to visit codestin.com
Credit goes to github.com

Skip to content

docs: add style-guide rule against "whose" for non-person antecedents #27866

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nickvigilante merged 1 commit into from
Aug 6, 2026
Merged

docs: add style-guide rule against "whose" for non-person antecedents #27866

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions docs/.style/style-guide/word-choice.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,6 +150,30 @@ Treat them consistently across the docs.

*Enforced by `Coder.PhrasalVerbs` (planned).*

## Whose for people, not things

"Whose" is the possessive of "who", so it implies the antecedent is a person.
When the antecedent is an inanimate object or an abstract concept, prefer "with", "where", or "that has".

**Do**:

> A chat with pruned gateway records reports no cost.
>
> A template that has conflicting variables fails validation.
>
> A region where every proxy is unhealthy drops workspace connections.

**Don't**:

> A chat whose gateway records have been pruned reports no cost.
>
> A template whose variables conflict fails validation.
>
> A region whose proxies are all unhealthy drops workspace connections.

*Documentation-only.
No Vale rule.*

## Refer to, check out, visit, not see

When the prose points the reader at another page, section, or external resource, choose the verb that matches the register:
Expand Down
Loading