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