Edit My Draft

A professional editing pass at the level you choose (line edit, copyedit, or proofread) with every change shown and your voice preserved.

Edit the text below at exactly ONE level. Do not drift upward into heavier editing than I asked for.

Level: [PICK ONE]
- LINE EDIT: improve flow, rhythm, clarity, and word choice at the sentence level. You may rewrite sentences; you may not restructure sections or change my argument.
- COPYEDIT: fix grammar, punctuation, spelling, capitalization, and consistency. You may not restyle sentences that are correct but plain; correctness only.
- PROOFREAD: final surface pass: typos, doubled words, missing words, spacing, formatting slips. Touch nothing else, even errors of style.

Style guide: [CHICAGO (books, general prose (serial comma, spell out numbers under 101) / AP (journalism, web) no serial comma, numerals from 10) / HOUSE: paste your rules / "you pick and tell me"]
What this text is + audience: [e.g. "newsletter for developers" / "novel chapter" / "grant application"]
My voice, protected: [e.g. "casual, fragments allowed, em-dash heavy": the edit must sound like me on a good day, not like you]

Text:
"""
[PASTE DRAFT]
"""

Deliver:
1. **The edited text**: clean version.
2. **The change log**: every change as: [location] "original" → "revision", one-line reason. For proofreads, every fix; for line edits on long texts, every substantive change plus a count of mechanical ones. I need to SEE what you did: a silent rewrite is a failed edit.
3. **Queries to author**: anywhere meaning is ambiguous, a fact looks wrong, or a fix would change what I'm saying: ask, don't guess. Format: [QUERY: location, the question].
4. **Style sheet**: the recurring decisions you made (hyphenation choices, number treatment, capitalization calls) so future edits stay consistent.

Rules: preserve voice over polish. If a sentence is unconventional on purpose (fragment, repetition for effect), leave it and note it as a query if unsure. Never add content, soften claims, or "improve" facts. Flag but don't fix anything above your assigned level.

How to use

Two-thirds of real-world AI writing requests are edits, not drafts, and the #1 failure is the silent rewrite that flattens your voice while claiming to proofread. The level-lock and mandatory change log are the fix, mirroring how professional editing actually works (line → copy → proof, in order, never mixed). Run long documents in chunks of 1,000-2,000 words; edit quality drifts on very long inputs.

More writing prompts

Rewrite the text below in plain language for [AUDIENCE, e.g. "patients with no medical background" / "customers reading a policy update" / "new hires on day one"].

Target reading level: [e.g. "8th grade" / "as simple as the content allows"].

How to rewrite:
- Lead with what the reader must DO or what happens to them. Background comes af

Plain Language Rewrite

Rewrite dense policy, legal, medical, or technical text at a target reading level without losing a single obligation or number.

Writingbeginner

Write a comparison article for the query: [e.g. "Notion vs Obsidian" / "best Mailchimp alternatives"].

Options to compare: [LIST 2-8 OPTIONS]
Who is searching this: [READER + WHAT THEY ARE TRYING TO DECIDE]
My relationship to these products: [e.g. "I make one of them" / "I use two of them daily" / "none, I am researching"]
Facts I can su

Comparison Article

Write an honest X vs Y or best alternatives article: real differentiators, a decision table, and a clear pick for each type of reader.

Writingintermediate

Build an FAQ page for [PRODUCT/SERVICE/TOPIC].

Real questions people ask me:
"""
[PASTE SUPPORT TICKETS, SALES CALL NOTES, SEARCH QUERIES, OR COMMENTS. RAW IS FINE.]
"""

Facts I can state as true: [PRICING, POLICIES, LIMITS, TIMELINES]

Do this:
1. **Cluster** the raw questions into distinct questions people actually ask. Merge duplicat

FAQ Page From Real Questions

Turn support tickets and sales objections into an FAQ page that answers in the first sentence and is structured for AI search engines.