A grammar checker is software that scans text and suggests fixes for possible errors in grammar, spelling, and punctuation. A human proofreader reviews a near-final or formatted version for remaining errors, including mistakes that appeared when the text was laid out. For routine writing, a quick scan and a careful reread may be enough. If a piece still has unclear wording, inconsistent style, or claims that need evidence, work through those before the final proof.
What grammar checkers can help you find
Run a checker when you want a fast pass for typos, verb agreement, or missing punctuation. Some checkers also offer style suggestions, such as tightening a sentence. Treat each flag as a prompt to reread the sentence in context. Check the surrounding text before changing a pronoun, a technical term, or a phrase that sounds like the person who wrote it.
Set the language variety if the tool offers that choice. If a draft uses US English and the checker prefers UK spellings, you may spend time reviewing perfectly good words. For patterns you keep seeing, use the guide to common grammar mistakes.
What a proofread covers
- Proofreading catches remaining typos, missing words, stray punctuation, and layout problems. A proofreader can also check that agreed corrections made it into the final version.
- Copyediting deals with clarity, grammar, usage, and consistency while the text can still change. A copyeditor can query an ambiguous pronoun or record decisions about capitalization and spelling in a style sheet.
- Fact verification checks claims against reliable sources. For an event, that could mean comparing the public announcement with the organizer’s current schedule. Agree on who will verify which facts before work starts.
Ask what the service includes, what format the reviewer needs, and when you’ll get the marked copy back. When a change depends on what you intended or on information only you can supply, expect a question. Editorial Freelancers Association definitions.
What happened when we checked the same passage
On November 12, 2026, we used the free web checkers for LanguageTool and QuillBot with English (US) selected. We entered the same short fictional passage in each.
The list of workshop supplies are on the desk. We recieved the labels yesterday. Maya told Nina that she had booked the room. The workshop starts on Friday, May 15, at 6 p.m. Not this time.
Both tools showed two corrections for this passage. The table records the suggestions visible in the free web interfaces during this test. Results can vary with the text, settings, and version.
| Passage feature | LanguageTool | QuillBot |
|---|---|---|
| Subject–verb agreement | Suggested is for are | Suggested is for are |
| Misspelling | Suggested received for recieved | Suggested received for recieved |
| Ambiguous she | No flag | No flag |
| Workshop date and time | No flag | No flag |
| Not this time. | No flag | No flag |
How an editor would handle the five sentences
- Correct the verb. Write The list of workshop supplies is on the desk. The head of the subject is the singular noun list.
- Correct the spelling. Change recieved to received.
- Ask who booked the room. Either Maya or Nina could be she. Once the author confirms who booked it, name that person or recast the sentence. Purdue OWL guidance on unclear pronoun references.
- Verify the event details. Ask which year the announcement refers to and check whether May 15 falls on a Friday that year. A matching weekday and date only establish that the combination is possible. Confirm the actual date, start time, and time zone if relevant against the organizer’s schedule.
- Read the fragment in context. Not this time. could be an intentional beat in fiction or a natural reply in dialogue. If it appears alone in an announcement, ask what it refers to and spell out the meaning readers need.
Choose a level of review that fits the text
| What you’re working on | Review to use |
|---|---|
| A routine message with low stakes | Use a checker if your policy allows it, then reread for meaning and tone. |
| A blog post, report, or story that still needs sentence-level work | Get a copyedit for clarity and consistency. Share the intended audience, style guide, and any deliberate choices, such as dialect in dialogue. |
| A laid-out report, book, or web page ready to go live | Get a proofread of the actual file or preview. Check headings, captions, page breaks, and any details the layout may have changed. |
| An announcement, instruction, or report readers will act on | Assign someone to verify dates, figures, and other consequential details against their sources. Use a copyedit or proofread as the stage requires. |
If you’re hiring help, share a short sample and ask for a quote and turnaround for the specific work. For school or journal submissions, check what outside editing and automated assistance the institution permits.
Check the rules before sharing private copy
Follow your workplace, client, or school’s rules before pasting text into a web checker or sending it to a freelance editor. For a permitted tool, check the policy for your plan and feature. Look for what text leaves your device, how long the provider keeps it, and whether it can be used for product improvement or training. If the policy bars uploading the draft, use an approved tool or review it manually. Agree on confidentiality and file handling before sharing it with an editor. LanguageTool privacy policy and QuillBot privacy and security information.
Work through the draft in four passes
- Scan for obvious errors. Use an approved checker or work through the draft manually. Review changes one at a time and keep the original handy.
- Read for meaning and consistency. Read paragraphs in order and check that readers can tell who did what. Resolve questions about intent with the author and record decisions that apply across the piece.
- Verify details readers will rely on. Compare names, dates, figures, and quotations with the relevant sources. If sources disagree, ask the person responsible for the information before you finalize it.
- Proof the version readers will see. After edits and formatting, open the actual page, PDF, or message. Check headings, captions, links, and any passages changed during the final review.
For a longer checklist, see The Art of Proofreading in Three Passes. For work on voice and readability, see How to Edit a Blog Post for Clarity.
Try six editing decisions
- Correct The box of name tags are by the door. Which word governs the verb?
- A checker flags recieved in We recieved the proof on Tuesday. Which change can you make immediately?
- In Rosa told Emma that she had sent the invitation, what should you ask the author?
- The flyer says Saturday, May 15 and gives no year. What would you check before it goes to print?
- A character replies, Not today. A checker suggests adding a subject and verb. What would guide your decision?
- The approved manuscript says Registration closes Thursday. The laid-out PDF says Registration closes Friday. What should happen next?
Show answers and explanations
- The box of name tags is by the door. The singular head of the subject, box, takes is.
- Change recieved to received. The misspelling is clear from the sentence. If the day matters to readers, verify it against the delivery record.
- Ask whether Rosa or Emma sent the invitation. Either person could be she. Use the confirmed name or revise the sentence so the sender is clear.
- Confirm the year and check the date with the organizer. The calendar tells you whether May 15 is a Saturday in that year. The organizer’s schedule tells you whether the event is actually planned for then.
- Keep the short reply if it fits the scene. The preceding dialogue can supply the missing context, and the brevity may be part of the character’s voice.
- Flag the discrepancy and check the official deadline. Comparing the two versions reveals the change. The owner of the registration schedule can confirm which day to publish. Check the corrected PDF before sending it out.
