A clean spelling report means the tool found no remaining issues within the text and rules it checked. It does not prove that every word is appropriate, every name is correct, or every part of the publication file was scanned. Review meaning, terminology, and coverage separately before approving the manuscript.
Establish what the tool actually scanned
Record the file and text areas included in the spelling check. A manuscript may contain main text, footnotes, captions, headers, text boxes, and words embedded in images. Do not assume that a tool covers every area simply because it reports that the document is complete.
Use a controlled copy to investigate uncertain coverage when necessary. A known test error placed in a sample caption can reveal whether that area is included. Remove the test material afterward and preserve the result as evidence about the workflow, not as a claim about every other application or export format.
Distinguish recognized words from intended words
A spelling checker can accept a word that belongs to the dictionary but does not belong in the sentence. Replacing form with from changes meaning while leaving two ordinary words. Similar errors can survive in headings, instructions, and short labels where readers have little context to repair the sentence themselves.
Read important instructions for meaning after the spelling pass. Check what action the sentence actually asks the reader to take. A clean result is useful evidence about recognized spelling, but it cannot establish that the selected word expresses the author's intended instruction.
Review names against an authoritative project record
Character names, place names, contributor names, and specialized terms may appear unfamiliar to a general dictionary. Verify them against the appropriate project source before accepting a suggested replacement or adding them to a custom dictionary. A tool's unfamiliarity does not make the original spelling wrong.
Keep intentional variants distinguishable from accidental inconsistency. A historical source may use a different form of a name, while the author's narrative uses a standardized form. Record the reason when both are retained so a later editor does not normalize a meaningful distinction without reviewing its context.
Inspect ignored items and custom dictionary entries
A report can become clean because the user dismissed findings. Review the relevant ignored items, especially those dismissed in bulk. Determine whether each decision still applies after revisions or whether an earlier exception has concealed a later error with a similar appearance.
Custom dictionaries deserve the same attention. An incorrectly added name may stop generating warnings without becoming correct. Keep important terminology in a project record that can be reviewed independently of the tool's settings, particularly when several editors use different applications or local dictionaries.
Check consistency that spelling alone cannot resolve
A book may alternate between two acceptable spellings, capitalization patterns, or compound forms. The checker may accept both even when the variation distracts readers or obscures whether two terms refer to the same concept. Compare the manuscript with the chosen editorial conventions.
Handle exceptions through contextual review rather than an indiscriminate replacement. Dialogue, quotations, and source titles may require forms that differ from the surrounding prose. The objective is an intentional and understandable text, not a report made clean by forcing every occurrence into one automated rule.
Recheck the publication output where text can change
After export, inspect the areas most vulnerable to conversion and late editing. A correct source document does not prove that every label or caption in the release file matches it. Compare any separately maintained cover or image text with the approved wording as part of the handoff.
Use the relevant KDP formatting guidance for the output checks and retain the spelling report with its limited scope clearly stated. It is one useful part of copy review. Approval of the finished book requires evidence that the language, names, conventions, and delivered text are correct for the manuscript, including issues a spelling tool was never designed to decide.
Frequently asked questions
Clear answers for this publishing decision.
Does a clean spelling report mean the book is ready?
No. It addresses the tool’s findings within a particular scope. Meaning, names, terminology, consistency, and the actual exported text still need appropriate review.
Should unfamiliar names be replaced with suggestions?
Check them against the project’s reliable source first. A suggested dictionary word may be inappropriate, while an unfamiliar name may be exactly what the manuscript requires.
Why inspect ignored findings?
Dismissed findings can explain why a report is clean. Confirm that those decisions were intentional and remain valid after revisions, especially when earlier items were ignored in bulk.
What must I check, disclose, and verify myself when AI helped produce the book?
Review facts, rights, and source material yourself, record which parts were AI-assisted or AI-generated so you can answer Amazon’s disclosure question accurately, and treat every automated check as a starting point rather than a verdict.
See what the compliance checks cover