Proofreading catches prose. It cannot catch the
@fig: pointing at a label that no longer exists, the
reference that's in your .bib but never cited, or the figure whose
data changed after the PNG was made. Those only surface in the
rendered PDF — or in a reviewer's report. Check Manuscript finds them
first.
One sweep over the whole project, off the main thread, reporting in
a panel. The findings, by family: cross-references — a
@fig:/@tbl:/@eq: that points
nowhere, a label defined but never referenced, the same label used
twice. Citations — keys missing from the bibliography, entries
in the bibliography never cited, duplicate entries, entries missing
required fields. Structure — skipped heading levels (a ### under
a #), sections with no text in them. Consistency — the same term
spelled two ways across chapters. And the quiet killer:
figures older than the script that draws them — the plot you
regenerated everywhere except in the manuscript.
Check Manuscript rewrites nothing. Every finding carries the document and the exact passage; click it and the caret lands on the problem, highlighted — you decide what the fix is. A tool that silently "corrected" a manuscript would be worse than none.
The same philosophy extends to errors: when LaTeX dies, Folio Writer names the document and line the error came from — not the temporary stitched file you've never seen. The difference between a five-second fix and twenty minutes of bisecting.
Check Manuscript is in the free tier. Submitting something whose cross-references resolve shouldn't be a paid feature — it makes every manuscript that leaves Folio Writer a better advertisement than any screenshot. Pair it with per-compile snapshots and the submission you uploaded is both checked and preserved.