Editing and proofreading your manuscript with AI

Learn in your browser · Chapter 01 of 06

Writers hear 'run it through AI' as if that means one thing. It does not. Editing a manuscript is at least three separate jobs, and the tools built for each one are genuinely different products, not different settings on the same tool.

Professional editing has always split into stages. Developmental editing looks at structure, plot, pacing and character, done before anything else. Copy editing checks grammar, consistency and clarity sentence by sentence without changing the story. Proofreading is the final pass, catching typos, punctuation slips and formatting mistakes. AI tools map onto these stages unevenly. They are genuinely useful for parts of copy editing and proofreading. They do not replace developmental editing, because that job depends on judgement about what a story is trying to do, not pattern-matching against correct sentences.

Within copy editing and proofreading, there is a second split that matters just as much: three different kinds of AI tool exist, and 2026 tool-comparison guides consistently name a different product as the strongest example of each. A general grammar checker, such as Grammarly, was built for everyday writing of every kind and checks one sentence at a time. A manuscript-specific editing tool, such as ProWritingAid, was built specifically for book-length fiction and checks patterns across the whole manuscript, not just one sentence. A style-guide consistency tool, such as PerfectIt, was built for professional editors and checks a document against a fixed set of spelling and formatting choices, rather than checking grammar at all. None of the three is a smaller or larger version of the other two. Each one answers a different question about your text.

A worked example. Imagine a 90,000-word novel manuscript, ready for a first self-edit. Run only a general grammar checker over it, and it will catch missing commas and a handful of genuine typos, but it has no idea that the word 'suddenly' appears 340 times, that chapter 14 has almost no dialogue after three chapters that were dialogue-heavy, or that a minor character is called Mackenzie in chapter 3 and McKenzie in chapter 19. Those three problems each need a different tool, covered in the next three chapters, because none of them is a grammar mistake at all.

Learn in your browser · Chapter 02 of 06

A tool such as Grammarly is genuinely useful and genuinely limited. This chapter covers what it is actually built for, and the specific ways fiction breaks its assumptions.

A general grammar checker such as Grammarly was designed for everyday writing: emails, essays, reports, social posts. It is good at what most writing needs most of the time: spelling, subject-verb agreement, comma splices, run-on sentences, and flagging passive voice or wordiness as a suggestion. Used on a manuscript, it will genuinely catch real typos and slips that are easy to miss on your own tenth read-through.

Fiction, though, breaks several of the assumptions a general grammar checker is built on. Dialogue is deliberately full of sentence fragments, interruptions and grammatically 'incorrect' speech that represents how a specific character actually talks. Invented words, unusual character names and dialect spellings look like typos to a tool trained on standard prose. A grammar checker cannot tell the difference between a mistake and a deliberate stylistic choice, because it has no idea what your story or your character is trying to do.

Scroll sideways to see every column.

Learn in your browser · Chapter 03 of 06

A tool built specifically for fiction manuscripts checks something a sentence-by-sentence grammar checker structurally cannot: patterns that only show up once you look at the whole book together.

ProWritingAid is consistently named across 2026 tool-comparison guides as the manuscript-specific option, built for exactly this job rather than adapted from a general writing tool. Its reports work at the level of the whole manuscript rather than one sentence, including a repetition report that lists words and phrases used often across the entire book, and a pacing check that looks at dialogue density, sentence variation and the balance of action to description across chapters, flagging stretches that may be moving too slowly or too quickly for the surrounding text. These are genuinely different questions from 'is this sentence correct', and a general grammar checker has no equivalent feature, because it was never designed to hold an entire book in view at once.

This matters because the problems a manuscript-level tool catches are, by their nature, invisible from inside any single sentence. You cannot notice from reading page 40 alone that you have used the word 'suddenly' 340 times across the whole book, or that three consecutive chapters are almost entirely dialogue after a long stretch that was almost entirely description. Both are real patterns a reader will eventually feel, even if they cannot name what is causing the feeling, and both need a tool that reads the whole manuscript, not a person reading one page at a time.

Learn in your browser · Chapter 04 of 06

The third job is different again: not grammar, not pacing, but whether you made the same small choice the same way every time across a very long document.

PerfectIt is consistently named across independent editor-focused sources, including editors' professional association blogs, as a consistency and house-style checker built for exactly this job, used widely by professional copy editors and proofreaders rather than by casual writers running a quick check. It does not check grammar in the way Grammarly does, and it does not analyse pacing or repetition the way ProWritingAid does. Instead, it checks a document against a fixed set of choices: spelling variants, capitalisation, hyphenation, abbreviations and headings, flagging every place those choices were not made the same way twice. It supports built-in UK, US, Canadian and Australian English conventions, and integrates with recognised style guides such as the Chicago Manual of Style, so an editor can check a manuscript against a defined standard rather than only their own memory of earlier chapters.

This is a real and common problem in a long manuscript specifically because it is invisible to both grammar checkers and human memory at scale. A character's name spelled two ways, 'Mackenzie' in chapter 3 and 'McKenzie' in chapter 19, is not a grammar mistake, so a grammar checker will not flag it. It is also genuinely hard for a human editor to catch by memory alone across 90,000 words and several months of drafting. A consistency tool exists specifically to check exactly this kind of choice, at the scale a single read-through cannot reliably manage.

Scroll sideways to see every column.

A worked example. Say a manuscript introduces a fictional organisation called 'the Silver Guild' in chapter 2, always capitalised as a proper name. By chapter 20, after months of drafting, half the mentions read 'the silver guild', lower case, because the writer's own memory of the choice drifted. A grammar checker sees nothing wrong with either version on its own, since both are grammatically valid capitalisation choices in isolation. A consistency tool checking the document against its own earlier choices is built specifically to catch exactly this kind of drift.

Learn in your browser · Chapter 05 of 06

Knowing the three tool categories only helps if you run them in an order that actually makes sense, and know honestly where every one of them stops being useful.

Run these roughly in this order, because each stage assumes the one before it is reasonably settled. First, a developmental edit: structure, plot, pacing and character, done by you, a human editor, or beta readers, since no AI tool in this workbook does this job. Second, a manuscript-specific pass, using a tool such as ProWritingAid, once the structure is settled enough that repetition and pacing reports are checking the version you actually intend to publish, not a draft you are about to restructure anyway. Third, a general grammar pass, using a tool such as Grammarly, catching sentence-level slips, applied with judgement in dialogue and stylised narration. Fourth, a style-guide consistency pass, using a tool such as PerfectIt against your own style sheet, ideally near the very end, since consistency only means something once the text has stopped changing structurally.

1. Developmental edit first: structure, plot, pacing, character. Human judgement, not a tool in this workbook.
2. Manuscript-specific pass: repetition, pacing and whole-book patterns, once the structure is settled.
3. General grammar pass: sentence-level correctness, applied with judgement, especially in dialogue.
4. Style-guide consistency pass: your own style sheet, checked near the end when the text has stopped moving.
5. A final read-aloud pass, by you: this catches rhythm and awkward phrasing that no tool in this workbook checks for at all.

None of the three tool categories in this workbook, and no combination of them, replaces a developmental edit or an honest beta reader's reaction to your story. They are genuinely useful for the jobs described in this workbook: sentence-level correctness, whole-manuscript pattern-spotting, and fixed-choice consistency. Whether your plot works, whether a character is believable, and whether a reader will actually want to turn the page, are judgement calls a pattern-matching tool has no way to make, because none of those questions has a single correct answer to check against.

Learn in your browser · Chapter 06 of 06

Everything in this workbook comes down to picking the right tool for the actual question you are asking, in a sensible order, with your own judgement kept firmly in the loop.

What you can do now. You can tell the difference between a general grammar checker, a manuscript-specific editing tool and a style-guide consistency tool, and know which question each one is actually answering. You have a short style sheet started for your own manuscript, a sense of your own overused words, and a sensible order to run an editing pass in that does not waste a tool's time checking a draft that is still about to change structurally.

Keep this workbook. It is yours to keep, print and write in. Come back to the editing order in the previous chapter whenever you start a new manuscript, and update your style sheet the moment you invent a new name.

https://trust-agent.ai/exam/editing-your-manuscript-with-ai

This is free educational content published by Mickai LTD, not professional, legal or publishing advice, and Mickai accepts no liability for how it's used. Tool names, features and pricing in this workbook change quickly. Check a tool's own current features before relying on any detail here.

Trust Agent publishes workbooks like this one for free because Mickai believes a public that understands its own tools well enough to choose between them, rather than trusting a single one by default, gets more real benefit out of AI and fewer of its disappointments.