Spell-check and grammar tools are useful, but they still miss a lot: the wrong word spelled correctly, a missing word, a name that drifts halfway through a page. Today you use human proofing methods on a short practice piece, then on the newsletter you have been building for your Something Real project — the one-page update about your club, group or work placement that you started earlier in this unit. The aim is that the version you keep is one a work supervisor, club coach, or examiner could trust.
Think of the last time you sent a message and only spotted a mistake after you hit send. What kind of mistake was it: a wrong word that still looked right, a missing word, or something else?
Manual proofing is a set of deliberate human checks you run after the software has done its pass. Spell-check and grammar tools only flag what their rules recognise, so homophones, real words in the wrong place, and missing little words often sail through. Use more than one human method: each catches a different kind of slip.
| Concept | Why it matters | Example |
|---|---|---|
| Read aloud — read the full text out loud at a steady pace, as if presenting it to someone else | Your ear catches missing words and clumsy sentences | Reading a Work Experience newsletter aloud reveals "Please bring clean kits the hall" is missing the word "to" |
| Reverse reading — start at the last sentence and work back up, reading each sentence slowly word by word | Stops your brain filling in what it expects | Reading bottom-up flags "form 10am" when you meant "from 10am" on a drop-off notice |
| Paper or zoomed PDF markup — print a page, or export a PDF and zoom it large, then mark errors with a pen or sticky notes | A slower second view catches layout and name slips | A zoomed PDF of a club fundraiser page shows two different spellings of the project name on the same sheet |
Later you may also use fresh eyes (a short partner swap) if your teacher runs a pair pass. That is optional practice, not a fourth method you must master today.
Practice paragraph (errors left in on purpose):
Welcome too our March update. Their are now four drop-off points across Cork city. We except clean boots and jerseys. Its free too drop kit off any Saturday morning form 10am. Thank you for you're support of the Northside Kit Swap.
After a class hunt using read aloud and reverse reading, you might catch slips such as:
Your teacher will confirm the full set of fixes after you have tried the methods yourself. That is the standard you will apply to your own newsletter next.
When someone marks up a page for you, they use the same short symbols an editor or a printer would. Learn to read them, not just to write your own: the whole point is that a marked page can be handed to anyone.
| Mark | What it asks for |
|---|---|
np | start a new paragraph here |
run on | no new paragraph, join this to the line above |
# | insert a space |
| a word struck through | delete it |
a word circled, marked bold | set it in bold |
| a word struck through with another written above | replace it with the one written above |
Swap your marked page with a partner and carry out their marks exactly, without asking them what they meant. If they cannot make your change from your mark alone, the mark was not clear enough.
Create a short manual-proofing practice document, paste the sample paragraph, run read aloud and reverse reading, then fix every error you catch. Your teacher will demonstrate PDF or zoom markup on the board. This is rehearsal before you touch your real newsletter.
Everyone does the same six things today, in this order. First you create the file and rename it, then you paste in the sample paragraph. Next you whisper-read the paragraph so your ear can catch the gaps, and then you read it again in reverse so your eye stops filling in what it expects. After that you apply every fix you caught, and you finish with one more quiet read to check the sentences now sound right. Skip the software pass and the pair pass unless your teacher starts them, and leave the PDF export to your teacher's demo on this practice file.
| Issue | Solution |
|---|---|
| Spell-check already said the document was fine, so I cannot find three errors | Look for homophones (to/too/two, their/there, your/you're), missing little words (to, of, the), repeated words, and project names spelled two ways. Those often pass software checks. Keep this list on your desk while you work on your own newsletter. |
| I have no printer for paper markup | Use whisper-read and reverse reading as your two required methods. Paper or zoomed PDF is optional only if your teacher already demoed export or a printer is available. The goal is a slower second view, not the printer itself. |
| Reverse reading feels slow and pointless | Use it on one dense paragraph only (about 4–6 sentences). You are training your eye to stop auto-correcting, not rewriting the whole newsletter backwards. |
| Reading aloud is awkward in a quiet room | Use a low voice at your desk, or mouth the words clearly while tracking with a finger. Whispered read-aloud still catches missing words. Follow your teacher's direction for whisper or partner read. |
If you catch a wrong-but-real word a spell-check ignored, that is the whole skill — note it on your fix list and take the win before you save version 7.
Portfolio evidence for this lesson: {{code:sm1_manual_proofing_practice}} (methods practice + fix list) and {{code:sm1_doc2_newsletter_v7}} (three human fixes applied).
You're previewing this lesson. Get full access to this lesson and hundreds more — each one ready to teach, with interactive activities, printable resources and pupil progress tracking built in.