What the style guides say
“simple”
5 of 16 open style guides have a rule about “simple.” They don’t agree on what to write instead: 1 say “efficient, basic,” and the rest give a different answer.
What to write instead, by guide
- efficient, basic 1 guide
Elastic
- 'straightforward', 'uncomplicated', or 'clear' 1 guide
18F
Guide by guide
- GitLab Avoid it Simplicity · warning
- Grafana Avoid it Simple · warning
- Elastic Write efficient, basic Word choice · suggestion
- Spectro Cloud Avoid it condescending · error
- 18F Write 'straightforward', 'uncomplicated', or 'clear' Terms · warning
No rule names it in Google, Microsoft, Red Hat, IBM, Datadog, Splunk, Salesforce, Docker, Canonical, Apify, 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 “simple”.
- Apify says to write it instead of pretty simple
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.