Turns raw, unstructured text into a publish-ready document. This is not editing — the words stay as close to original as possible. This is structure surgery.
\nBefore adding structure, classify what type of document this is. Structure follows intent.
\n| Document Type | Primary Structure Element |\n|--------------|--------------------------|\n| How-to guide | Numbered steps with H3 per step |\n| Listicle | H2 per item, supporting text below |\n| Explainer | Definition first, then H2 sections |\n| Case study | Problem → Solution → Result flow |\n| Reference doc | H2 categories with table or list under each |\n| Opinion piece | H2 per main argument, no numbered lists |
\nH1 — One per document. The topic. Matches the primary keyword.
\nH2 — Major sections. Each H2 should answer a distinct question or cover a distinct subtopic. If you have 10+ H2s, most should be H3s.
\nH3 — Sub-sections under H2. Use when an H2 section has 3+ distinct sub-points.
\nH4 — Rarely needed. Use only for deep technical documentation with nested categories.
\nTest: Can a reader get the full outline of the document by reading only H1, H2, and H3? If yes — structure is correct.
\nUse numbered lists when:
\nUse bulleted lists when:
\nNever use lists when:
\nAdd tables when content compares 3+ items across 2+ attributes.
\nRequired table elements:
\nWhen NOT to use tables:
\nUse callout boxes (blockquotes or styled divs) to highlight:
\nOne callout per major section maximum. Too many callouts = nothing stands out.
\nBefore delivery:
\nWhen formatting SOP documentation specifically:
\n#content-sop #formatting #structure #readability
\n"}