Line Editing with AI: A Step-by-Step Checklist
What Line Editing Actually Does
Line editing works at the sentence and paragraph level. It does not touch chapter architecture, and it has nothing to say about spacing. It asks one question over and over: is this sentence carrying its own weight?
What it catches: uneven rhythm, ambiguity, repetition, verbs that do no work, sentences that all run the same length, pronouns whose referent is anyone's guess.
What this pass cannot fix
Line editing will not rescue a wrong chapter. A chapter with no reason to exist gets worse when its sentences are polished, because the reader is now led more confidently to nowhere. If you start thinking a chapter should be merged or cut, go back to structure.
Why You Lock the Structure First
The professional order is structural editing, then line editing, then copyediting, then proofreading; each layer assumes the previous one is finished. Run the order backwards and you get polished prose whose structure you now have to tear apart.
A locked structure means four things: the chapter list is fixed, the order is fixed, each chapter's job fits in one sentence, and you know which chapter each one hands off to. Until all four are true, line editing is spending you cannot get back.
The one-sentence test
Summarize each chapter in one declarative sentence. If you cannot, that chapter is not ready for sentence work; its problem is structural. Structural Editing with AI covers finding the spine of the argument and merging or cutting chapters; the complete map of smart editing places all four levels.
Three Prompt Patterns That Work
Three patterns are enough if you keep the scope small: one paragraph at a time, never a chapter. A language model is strong on language patterns and weak on judgment, so the narrower the scope, the safer the output.
Pattern one: diagnose, do not rewrite
Do not rewrite this paragraph. Tell me which sentences are weak and why. One line of explanation per item, and cite the sentence number. If the problem is structural rather than sentence-level, say so and do not offer a rewrite.
Pattern two: rewrite with a ceiling
Rewrite only sentences three and four. Keep my vocabulary. Add no new claims. Make them shorter without changing the meaning. If you need information that is not in the text to make the meaning clear, write "unknown" and do not rewrite.
The ceiling matters more than the instruction. Without one, the model smooths the paragraph and swaps your voice for its average. The "write unknown" clause blocks a common form of damage: a new sentence that reads well while asserting something you never said.
Pattern three: questions instead of answers
Read this paragraph and tell me which sentences a reader with no background would find unclear. Ask questions, do not answer them. Give me the list of questions and I will decide.
Use this when you know something is off but cannot place it.
The Line-by-Line Checklist
Read the whole list, but run one row per pass. Doing all of them at once makes every decision arbitrary.
- Sentence length: long runs broken up, short runs joined? Monotony comes from both directions.
- Sentence openings: two consecutive sentences starting the same way? Change one.
- Verbs: find the real verb. If you keep meeting "was carried out" and "was reviewed," restore the acting verb.
- Repetition: a deliberate key-word echo stays; a lazy one goes. You know the difference, the model does not.
- Pronouns: pin every "it" and "this" to a named noun. If you cannot, the sentence is suspect even when it sounds smooth.
- Transitions: does the first sentence of each paragraph show where it came from? Add the missing one, cut the repeated one.
- Adjectives and adverbs: cut any adjective that adds nothing to its noun, and any adverb that only insists.
- Claims and evidence: does every load-bearing factual sentence have visible support? If not, add support or soften the claim.
- Paragraph endings: does the last sentence close the paragraph, or merely stop it?
- Read aloud: read every accepted paragraph out loud. Anywhere you run out of breath is your next edit.
An Accept/Reject Discipline
Model output is a proposal, not a draft. Four rules keep the work manageable.
Rule one: accept the smallest unit, not the paragraph. If a six-line suggestion contains one better ordering, take that and drop the rest.
Rule two: never accept a suggestion you cannot explain. If you cannot say why the new sentence is better, you will not defend it next week either.
Rule three: separate the day you generate from the day you accept. Generate, leave it, decide tomorrow; overnight distance deletes most worthless suggestions.
Rule four: keep a decision log: what you accepted and rejected in each chapter. By chapter ten it stops you relitigating the same argument.
Five Common Mistakes
- Handing over the whole book in one prompt. You get generalities you cannot use. Break the text into paragraph-sized units.
- Accepting output wholesale. A model imitates tone; it does not build your voice. Bulk acceptance is where that costs you.
- Outsourcing judgment about meaning. A smoother sentence is not evidence that it carries the intended point.
- Mixing the levels. Fixing spacing during a line edit means doing two jobs halfway. Run copyediting Persian text with AI when its turn comes.
- Counting changes instead of reading. The test is whether the prose moves, not how many sentences you altered.
None of these is solved by a better tool; they are solved by a working order. The person judging the suggestion is you.
