Vale CMS Need more than a rule playground? Explore

What the style guides say

“couldn't”

2 of 16 open style guides have a rule about “couldn't.” 1 of them say to write “could not” instead.

Write this instead

  • could not 1 guide

    Red Hat

Guide by guide

  • Red Hat Write could not Contractions · suggestion
  • Splunk Avoid it Subjunctive mood · warning

No rule names it in Google, Microsoft, IBM, GitLab, Grafana, Elastic, Datadog, Salesforce, Docker, Canonical, Apify, Spectro Cloud, 18F, 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 “couldn't”.

  • Google says to write it instead of could not
  • Microsoft says to write it instead of could not
  • Grafana says to write it instead of could not
  • Apify says to write it instead of Could not
  • 18F says to write it instead of could not

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.