Vale CMS Need more than a rule playground? Explore

What the style guides say

“were not”

5 of 16 open style guides have a rule about “were not.” All 5 say to write “weren't” instead.

Write this instead

  • weren't 5 guides

    Google, Microsoft, Grafana, Apify, 18F

Guide by guide

  • Google Write weren't Contractions · suggestion
  • Microsoft Write weren't Contractions · error
  • Grafana Write weren't Google contractions · suggestion
  • Apify Write weren't Contractions · suggestion
  • 18F Write weren't Contractions · error

No rule names it in Red Hat, IBM, GitLab, Elastic, Datadog, Splunk, 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 “were not”.

  • Red Hat says to write it instead of weren'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.