Docwright
An AI markdown editor built for technical writers, developer-advocates, and documentation teams — catches typos, jargon overuse, ambiguous phrasing, broken links, and outdated API references, and ships as a GitHub PR review bot for docs-as-code workflows.
Technical writers and developer-advocates producing documentation in markdown
- Spell/grammar/style checker tuned for technical writing (not generic English) — flags passive voice in tutorials, jargon overload, and inconsistent terminology
- Link-rot and API-reference drift detector that flags docs referencing deprecated endpoints
- Tone dial: 'more pedagogical' vs. 'more concise' with a side-by-side diff preview
- GitHub PR bot that posts a 'doc-readability report' on every documentation pull request
Tools like harper (which Toast just integrated) prove spell-check for markdown is a real pain point; technical writing is a fast-growing professional segment and current tools like Grammarly are tuned for prose, not code-adjacent documentation.
HN trend was weak at 5 points, but the underlying pain (markdown spell-check) is confirmed by Toast shipping it themselves
Grammarly and ProWritingAid optimize for prose; no incumbent owns technical-writing-specific markdown editing
Technical writers and dev-tool teams have documented budgets; $20–50/mo per seat is plausible
Documentation is a permanent need in software — outlives any individual tool or framework
LLM markdown handling is mature; GitHub bot integration is well-trodden engineering