Computer Skills
Beginner
60 mins
Teacher/Student led
Learning Goals
Learning Outcomes
+80 XP
What you need:
Chromebook/Laptop/PC or iPad/Tablet

Proofing: Spell-check & Grammar Tools

Learn to use spell-check and grammar tools effectively, then recognise where they fall short. You'll proof a sample text, then apply your judgment to your own proposal draft before submission.

Teacher Class Feed

Load previous activity

    1 - Introduction

    Welcome

    Your proposal draft already says what you want to say. This lesson is about making sure a reader (a manager at your Work Experience placement, an Intreo case officer, a landlord, a college admissions tutor) takes you seriously when they read it. Spell-check and grammar tools are fast, but they miss things only a human can catch, and today you learn exactly where that line is.

    By the end of this lesson, you will be able to:

    • Run spell-check and grammar check and evaluate each suggestion on its merits
    • Recognise where spell-check misses homophones and context
    • Use re-reading aloud as a final human check

    Warm-up

    Think for a moment: before you send an important message (a text to a future employer, an email to Citizens Information, a form for an apprenticeship), what do you normally do to check it? Do you trust the phone's autocorrect, or do you re-read? What's the difference?

    👇 Mark your steps as done as you complete them.

    +5 XP

    2 - Key Concepts

    ConceptWhy it mattersExample
    Spell-check — the built-in checker that underlines words it does not recognise, usually in redTypos tell a reader 'I did not proofread' before they reach your content; fixing them takes secondsYour application for a Centra stocktake role says 'experence'; spell-check underlines it, you right-click and fix to 'experience'
    Grammar check — the checker that flags sentence-level issues (wrong verb form, missing words, wrong agreement), usually with a blue underlineGrammar errors make writing sound off even when every word is spelled correctly'I done my work experience' reads wrong; grammar check may suggest 'I did my work experience'
    Homophone — words that sound the same but are spelled differently (their / there, your / you're, to / too / two)Spell-check cannot catch homophones because each one is a real word, so the computer sees no error at all'Their was a lot to learn' — 'Their' is spelled correctly, so spell-check stays silent, but the right word is 'There'
    Context error — a real, grammatical word that is simply wrong for what you meantThe tools check spelling and grammar on the surface of the language; only you know what you actually meant to sayYou meant 'from' but typed 'form' — both real words, both grammatical in a sentence, but only one fits
    Re-reading aloud — saying your writing out loud, one sentence at a time, slowlyYour ear catches awkward phrasing and missing words that your eye skips over; it is the only reliable human check that catches what the tools missReading 'My placement last week in the' aloud, you hear the sentence does not finish; silent reading had skipped the gap

    Worked sample paragraph

    You will use this paragraph in the exploration activity. It contains eight real errors, some that spell-check catches, some that only a human reader catches.

    Last week I done my work experience at Murphy's Garage in Galway. Their was alot too learn. The staff where really helpfull and showed me how two change a tyre. I think this placement will help me descide what apprenticeship to apply for next year.

    👇 Mark your steps as done as you complete them.

    +10 XP

    3 - Explore and Evaluate

    Proof the sample paragraph from the Key Concepts step using both spell-check and grammar check, then see what the tools missed. The goal is to notice which kinds of errors the tools catch and which they do not, not to tick boxes. Keep count as you go.

    +15 XP

    4 - Common Issues

    Common Issues

    IssueSolution
    The tool underlines a word that is actually spelled correctly (a place name, an Irish word, a technical term)Right-click the word and choose 'Add to dictionary' or 'Ignore'. Words like 'Gaeltacht', 'Centra', 'Intreo', and personal names are often flagged but are not wrong
    A grammar suggestion changes the meaning of your sentenceReject it. The tool does not understand your meaning; it is pattern-matching. Only accept a change if it still says what you meant to say
    Spell-check reports 'no issues' but you can see an obvious mistakeIt is probably a homophone (their/there, your/you're, to/too) or a real word used in the wrong place (form/from). Read aloud and fix by hand
    The proofing panel will not open or says the language is wrongCheck the document language: in Word Online, {{menu:Review -> Editor -> Set Proofing Language}}; in Docs, {{menu:File -> Language}}. Set it to English (Ireland) or English (United Kingdom)
    +10 XP

    5 - Portfolio Build: Proof Your Proposal Draft

    Independent Practice

    Your goal: Use the proofing judgment you just practised on your own proposal, so the version an adult actually reads is free of typos AND free of the sneakier homophone and context errors the tools miss.
    Time: ~20 minutes
    Task: Open {{code:03_proposal_draft}} from your {{code:Digital_Portfolio}} folder and run both the spell-check and the grammar-check panel. Work through every suggestion, accepting or rejecting each one based on whether it fits your meaning. Then re-read the whole document ALOUD, slowly, and fix anything your ear notices that the tools missed. At the end of the document, add a small heading called 'Proofing notes' with a 2-3 line list of what you changed that the tools did not catch, OR if the tools caught everything, a short note explaining which homophones and context errors you specifically looked for.
    Success criteria:
    • Your proposal has no red-underlined spelling errors left
    • At least one suggestion was accepted and at least one was rejected with a reason you could explain aloud
    • Your 'Proofing notes' section either lists a homophone or context error that neither tool flagged, OR, if your draft had none, one sentence explaining what you specifically checked for (e.g. 'checked every their/there, to/too, your/you're') and why
    • The whole proposal reads cleanly when spoken aloud: no missing words, no awkward half-sentences
    +15 XP

    Unlock the Full Learning Experience

    Get ready to embark on an incredible learning journey! Get access to this lesson and hundreds more on our learning platform.

    Get started
    Copyright Notice
    This lesson is copyright of Coding Ireland 2017 - 2025. Unauthorised use, copying or distribution is not allowed.
    🍪 Our website uses cookies to make your browsing experience better. By using our website you agree to our use of cookies. Learn more