Style guide explorer
What Google, Microsoft, GitLab, Red Hat, GOV.UK, and others tell their writers to do, read out of the rules each one publishes. Browse a guide by topic, or look up a word and see what every guide says about it.
Each square is a guide’s rules on one topic, darker for more. Read across to see what a guide cares about, and down to see which guides bother with a topic at all.
| Guide | Word choice | Concision | Voice and tone | Inclusive language | Punctuation | Headings | Numbers and dates | Abbreviations | Source hygiene | Rules |
|---|---|---|---|---|---|---|---|---|---|---|
| 5 | 8 | 2 | 11 | 2 | 5 | 3 | 36 | |||
| Microsoft | 8 | 3 | 5 | 5 | 11 | 4 | 9 | 2 | 47 | |
| Red Hat | 8 | 5 | 5 | 1 | 8 | 3 | 2 | 5 | 37 | |
| IBM | 2 | 1 | 3 | 1 | 3 | 10 | ||||
| GitLab | 52 | 1 | 2 | 8 | 3 | 1 | 1 | 1 | 69 | |
| Grafana | 42 | 8 | 6 | 2 | 11 | 3 | 4 | 3 | 79 | |
| Elastic | 19 | 1 | 1 | 3 | 5 | 1 | 2 | 32 | ||
| Datadog | 26 | 26 | ||||||||
| Splunk | 45 | 2 | 1 | 10 | 2 | 2 | 4 | 66 | ||
| Salesforce | 28 | 28 | ||||||||
| Docker | 10 | 1 | 4 | 1 | 1 | 17 | ||||
| Canonical | 21 | 1 | 1 | 3 | 26 | |||||
| Apify | 75 | 1 | 2 | 4 | 3 | 5 | 90 | |||
| Spectro Cloud | 20 | 20 | ||||||||
| 18F | 4 | 1 | 3 | 1 | 2 | 11 | ||||
| GOV.UK | 3 | 1 | 4 |
Google developer documentation style guide
Microsoft Writing Style Guide
Red Hat supplementary style guide
IBM Developer editorial style guide
Elastic docs style guide
Datadog documentation style guide
Splunk style guide
Salesforce writing style guide
Docker documentation style guide
Apify writing style guide
Spectro Cloud style guide
GitLab documentation style guide
Grafana Writers’ Toolkit
Canonical documentation style guide
The terms the most guides have a rule about, with the replacement when at least half of them give the same one. Select a term to see each guide’s answer, or browse all 666 terms.
Cases where one guide’s fix is another guide’s error: the same two wordings, preferred in opposite directions. These are the largest; see every disagreement.
Each of these organizations publishes its style guide as rules for Vale, an open-source linter for prose. A rule is small and exact: flag this word, suggest that one, at this severity, for this reason. Read together, a guide’s rules are a picture of what the guide asks for, and that is what this explorer draws. Nothing here was summarized by hand.
That also sets its limits. A guide’s advice that nobody wrote a rule for isn’t here, and “terms” counts only rules that name plain words, so a guide written mostly as patterns looks smaller than it is. Each guide’s page names the repository, the commit it was read at, and its license.
“Public configs” is how many of 355 sampled open-source Vale configurations use that guide’s rules. See who uses Vale.