Style guide linter
Checks your text against the Microsoft Writing Style Guide and the Google developer documentation style guide, and cites the exact section for every finding.
Your text never leaves your browser.
Paste text above to check it against the selected style guide.
Your text, annotated
Needs attention Worth a look — select a highlight for details.
Findings
Code samples are never linted
Every fenced code block (```), indented code block, and inline `code span` is stripped before any rule runs — flagging "utilize" or "click on" inside a code sample would make this tool actively wrong, not just annoying. If a finding looks like it's inside code, that's a bug; the text above should show the highlight sitting outside any code formatting.
Why every finding cites a section
A linter that just says "wrong" asks you to trust it. This one links to the actual guide section it's applying, so you can check the reasoning yourself, or point a teammate at the source instead of just your opinion of it. Each rule was verified against the live guide before shipping — see the "Why this matters" expander on any finding.
This is a smaller rule set than a full linter like Vale — around a dozen of the highest-value checks, not the full 30-40 rule catalog either guide covers. It'll grow over time.