What the style guides say
“was not”
5 of 16 open style guides have a rule about “was not.” All 5 say to write “wasn't” instead.
Write this instead
- wasn't 5 guides
Google, Microsoft, Grafana, Apify, 18F
Guide by guide
- Google Write wasn't Contractions · suggestion
- Microsoft Write wasn't Contractions · error
- Grafana Write wasn't Google contractions · suggestion
- Apify Write wasn't Contractions · suggestion
- 18F Write wasn'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 “was not”.
- Red Hat says to write it instead of wasn'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.