proofread

To check Markdown files for typos and notation inconsistencies, load your game setting documents into the scanner to automatically detect spelling errors, punctuation variations, and mixed full-width or half-width symbols. It reports findings per file with quoted excerpts and suggested corrections.

Yes, you can detect mixed full-width and half-width punctuation in game setting documents. The scanner highlights symbol variants and proposes standardization to ensure your world information, character profiles, and time schedules maintain consistent notation.

Proofreading Markdown files does not modify your original content. The scanner operates strictly in read-only mode to identify typos and notation variations, reporting all findings with quoted offending excerpts and suggested fixes without altering any target files.

The best way to unify inconsistent terminology across multiple Markdown files is to run an editorial review scanner that identifies notation variations for the same concept. It suggests unified wording for each file, ensuring clean and consistent final handoff documents.

To get a per-file list of editorial issues in your Markdown folder, run the scanner command to analyze all target documents. It outputs a detailed report of spelling errors and punctuation inconsistencies, quoting the offending excerpts for each file.

You need to proofread Markdown files for a murder mystery game after generating your setting materials like world, characters, and timelines. Running this check ensures the final handoff documents are clean, readable, and free of typos or notation inconsistencies.