Book editing, from the big picture to the last comma

Editing isn't one job. It's a sequence of passes, each looking at the book from a different distance. Doing them out of order wastes effort: there's little point polishing the commas in a chapter you're about to cut.

Developmental editing looks at the whole book. Does the structure work? Is the pacing right? Do the characters change, and do their choices make sense? In non-fiction: is the promise clear, is the argument in the right order, and does each chapter earn its place? The result is usually a letter describing the biggest problems and possible fixes, not changes to individual sentences. It's also where the hardest decisions get made, such as cutting a subplot or merging two characters.

Line editing works paragraph by paragraph. It's about the prose: rhythm, clarity, word choice, tone and voice. A line editor might point out that three paragraphs in a row open the same way, or that a tense scene is slowed down by long sentences.

Copyediting is about correctness and consistency: grammar, spelling, punctuation and usage, along with the facts of the book itself. Does a character's eye color stay the same? Is the town spelled the same way throughout? Do the dates line up?

Proofreading is the final check, ideally on the formatted book. It catches typos, missing words and layout problems such as stray blank pages or a heading stranded at the bottom of a page.

You can combine passes, handle some yourself, or hire an editor for one stage and do the rest. Whatever you choose, keep the order: the big picture first, sentences next, details last.

AI helps with editing for the same reason a second reader does: it sees the manuscript fresh. It can read the whole book at once and notice that the middle sags, that a character vanishes for long stretches, or that a claim in chapter nine contradicts chapter two. It's quick at spotting repeated words, tangled sentences and grammar slips.

It's less reliable on judgment calls that depend on your intentions. A deliberately fragmented sentence, an unreliable narrator or a character's dialect isn't an error, and a suggestion that “fixes” it would damage the book. That's why every change in AIBookWriter stays a suggestion until you accept it.

The whole-book review is built around that idea. It reads every written chapter, scores the book against criteria suited to its type, such as pacing, character arcs and dialogue for fiction, or clarity, evidence and actionability for non-fiction, and writes an editorial letter that puts the most important revisions first. Line edits quote your text exactly and give a reason. You accept or reject them one by one, and an edit is refused if the passage has changed since the review.

The review costs 15 credits per 1,000 words, charged once per book; after that, run it again whenever you revise, at no cost. It's available on the Plus plan and above. When the book changes after a review, you're told, so you know when a fresh read is worthwhile.

None of this makes a human editor unnecessary for every book. A sensible approach is to fix what you can with AI passes first, so that an editor you hire spends their time on the problems that need a person. Either way, proofread the formatted files yourself before you publish.