Tool

Technical Writing Linter

Paste a technical article, tutorial, or blog post. Get an honest report. Flags the patterns that make technical readers close the tab.

article.txt
⌘↩ to run
0 words
results.log
{ }

Results appear here after you run the linter.

Rules

What gets flagged

error
  • Paragraph length — Never more than two sentences in a prose paragraph.
  • Personal voice — Full articles need first-person experience, observation, or judgment. Anonymous reference copy belongs in product docs.
  • Em dashes — No em dashes (—) in prose. Rewrite with a comma, period, or parentheses.
  • Contrastive parallelism — No "unlike X, Y…", "whereas", or "on the other hand". Use evidence instead of contrast.
  • Horizontal lines — No --- section dividers. Use a heading or white space.
  • Banned jargon — "leverage", "synergy", "unlock". Say what you mean.
  • Banned sentence openers — No sentence starting with "In", "This", "By", "Finally", "Most", or "Ever".
  • Condescension words — "simply", "just", "easy", "obviously", "of course". They assume the reader already knows what you're about to explain.
  • AI writing signals — "delve", "in conclusion", "it's worth noting", "rapidly evolving", "harness the power". Dead giveaways of LLM-generated content.
  • Filler openers — Starting with "In this article…" or "Today we will learn…". The weakest possible first line.
warning
  • Hedge words — "very", "really", "quite", "basically". They make every statement weaker.
  • Buzzwords — "leverage", "seamless", "robust", "cutting-edge", "utilize". Say what you mean.
  • Filler phrases — "in order to", "note that", "please note", "as you can see". Zero information content.
  • Tutorial "we" — "we will", "let's". You're teaching someone. Address them directly.
info
  • Passive voice — Detected by pattern. Not always wrong, but worth reviewing.
  • Long sentences — Over 35 words. Technical readers scan. Long sentences fight that.
  • High adverb density — More than 5% of words ending in -ly. A sign of over-modified prose.
  • Low readability — Flesch-Kincaid below 30. A score used in plain-language standards worldwide.

Need writing that passes its own linter?

Technical content for DevTools and B2B SaaS — accurate, minimal-revision, no fluff.

Book a Call → Read the Writing