What the style guides say
“could not”
6 of 16 open style guides have a rule about “could not.” 5 of them say to write “couldn't” instead.
Write this instead
- couldn't 5 guides
Google, Microsoft, Grafana, Apify, 18F
Guide by guide
- Google Write couldn't Contractions · suggestion
- Microsoft Write couldn't Contractions · error
- Grafana Write couldn't Google contractions · suggestion
- Splunk Avoid it Subjunctive mood · warning
- Apify Write Couldn't Contractions · suggestion
- 18F Write couldn't Contractions · error
No rule names it in Red Hat, IBM, GitLab, Elastic, Datadog, Salesforce, Docker, Canonical, Spectro Cloud, GOV.UK. That doesn’t mean those guides approve of it, only that no rule lists it.
Guides that ask for it
One guide’s fix can be another guide’s error. These rules tell writers to use “could not”.
- Red Hat says to write it instead of couldn't
Catch it in every draft
Each line above is a rule one of these organizations publishes for Vale, an open-source linter for prose. Install a guide’s rules and Vale flags the term wherever it appears, in your editor and on every pull request.