1 - Introduction ~5 mins
Welcome
You already know how to mark section titles as Heading 1 and Heading 2, and body text as Normal. That makes a file easier to scan. Today you go one step further: you change those styles so the whole document picks up your look in one move, instead of re-formatting every heading by hand.
That is how real reports, CVs, and enterprise project write-ups stay consistent when someone else opens them, or when you add three more pages next week.
By the end of this lesson, you will be able to:
- Update Heading styles from a formatted sample so the document has a clear visual identity
- Verify a global style update and fix fake headings that use direct formatting only
- Keep body text readable on Normal after heading changes, and apply consistent Heading 1 and Heading 2 on a project document
Warm-up
Start with the class sample. Your teacher has the sample link or path on the board (and usually in chat). Open that first if you are not sure you already have a styled project file.
- Open the link or path your teacher shared, or
- In cloud storage open {{code:Project_Portfolio}}
- Then {{code:09_specialism}}
- Then {{code:sm1}}
- Open the class sample document from there
You will open your own project file later in Independent Practice. Guided work stays on the shared sample so everyone sees the same fake heading.
If you already have a multi-section project file in {{code:sm1}} with Heading 1, Heading 2, and Normal applied (sometimes named like {{code:sm1_doc1_from_template_v4}}), you can leave that closed for now and use it in Independent Practice.
Look at two main section titles on the sample. If one heading is a different size or colour from the other, what would you rather do: fix that one heading by hand, or change the Heading style once so every matching heading updates together?
2 - Key Concepts ~6 mins
Watch the screen demo first, then use this table as a cheat sheet while you work. Do not try to memorise it.
| Concept | Why it matters | Example |
|---|---|---|
| Update style to match — format one heading the way you want, then tell the app to make that style match the selection | Faster than hunting every title, and works cleanly in both Word Online and Google Docs | You style one "Budget" heading by hand, then update Heading 2 so "Timeline" and "Next steps" match automatically |
| Global update — after you change a style, every paragraph using that style refreshes together | Long documents stay consistent when you add pages later or change colours for your audience | You darken Heading 1 once; all five section titles in your enterprise pitch update in the same second |
| Fake or inconsistent styling — a "heading" made with the bold button and a bigger font on Normal, or two real headings that still do not match | Style updates skip direct formatting; peers and examiners spot the uneven look instantly | One section title is true Heading 2; another is Normal text made bold and larger by hand — they will never stay matched |
Worked example: what done looks like
Aoife's small enterprise pitch for a phone-repair side hustle in Cork used default blue Heading 1. She wants a darker look for adults reading the pitch.
- She formats one Heading 1 sample: clear font, about 18 pt, bold, dark navy or dark grey.
- She chooses Update Heading 1 to match; every main title (What it is, Who it is for, Costs, Next steps) snaps to the same look.
- Later she repeats a lighter version for Heading 2 (about 14 pt, same colour family) so the hierarchy stays obvious.
You will practise the Heading 1 move on the class sample next. Heading 2 uses the same idea in Independent Practice.
3 - Step-by-step Task ~15 mins
Work through the guided task with your teacher on the class sample (not your final project file yet). You will format one Heading 1, update the style once, watch every real Heading 1 change together, then spot a fake heading with a partner.
What you will do:
- Open the class sample from the path your teacher gives you.
- Format one real Heading 1 the way you want (about 18 pt, bold, one dark colour).
- Update the Heading 1 style to match that sample.
- Scroll and check that every true Heading 1 matched; name any title that did not (likely a fake heading).
- In pairs, find one fake or mismatched heading and say the fix in one sentence.
You will apply Heading 1 and Heading 2 on your own project document in Independent Practice and save the v5 file there. Heading 2 uses the same update-to-match idea as Heading 1.
4 - Common Issues ~2 mins
Common Issues
Keep this table open as a desk card while you finish the guided task and Independent Practice. Your teacher will flash it on screen briefly; you do not need to copy every row.
| Issue | Solution |
|---|---|
| I updated Heading 1 but one title still looks different | That title is probably not using the Heading 1 style. Click it and apply Heading 1 again, then re-check. Direct bold or size on Normal will never follow a style update. |
| My body text changed when I only meant to change headings | You may have modified Normal, or selected body text when you updated a style. Re-apply Normal to body paragraphs. Next time, put the cursor in a true heading before you update Heading 1 or Heading 2. This happens to everyone the first time; fixing Normal is a two-minute recovery, not a rewrite. |
| I cannot find Update to match / Update Heading 1 to Match Selection | Word Online: Home tab, Styles gallery, right-click (or two-finger tap on a Chromebook) the style name; if that fails, use the small arrow on the style chip or the Styles pane. Google Docs: Format, Paragraph styles, Heading 1 (or 2), Update 'Heading …' to match. Keep the cursor inside the sample paragraph you already formatted. |
| Heading 2 looks louder than Heading 1 after my edits | Reduce Heading 2 size or weight so Heading 1 stays dominant (for example 18 pt bold for H1, 14 pt for H2, same colour family). Hierarchy should be obvious at a glance. |
5 - Independent Practice ~22 mins
Independent Practice
Work through these steps on your own machine. Heading 2 uses the same update-to-match idea you just used for Heading 1.
Heading 2 quick how-to: Click inside a real Heading 2. Format it (about 14 pt, same colour family as Heading 1, slightly lighter weight if you like). Then update the style: Word Online: right-click, two-finger tap, or the small arrow on the {{btn:Heading 2}} chip → Update Heading 2 to Match Selection. Google Docs: {{menu:Format -> Paragraph styles -> Heading 2 -> Update 'Heading 2' to match}}. Scroll to check every sub-heading matched.
- Open your styled project document in {{code:Project_Portfolio}}, then {{code:09_specialism}}, then {{code:sm1}}. If you do not have a multi-section project file, copy the class sample into {{code:sm1}} and open that copy.
- Choose one dark colour that suits your audience (supervisor, club, customer, or examiner). Aim for about 18 pt bold for Heading 1 and about 14 pt for Heading 2 in the same colour family.
- Update Heading 1 to match your sample (same path as guided practice).
- Update Heading 2 to match using the quick how-to above. Scroll to verify.
- Check that body paragraphs stay on Normal and stay readable. Fix any fake headings by applying the real Heading style.
- Save clearly inside {{code:sm1}}.
Legal filenames: {{code:sm1_doc1_from_template_v5}} (your project) or {{code:sm1_styles_practice_v5}} (sample copy).
Optional: if your teacher allows a quick peer glance, ask a partner to confirm the headings match (about 30 seconds).
- Every main section title shares one clear Heading 1 look (font, size, weight, colour)
- Every sub-heading shares one clear Heading 2 look that sits under Heading 1, not above it
- Body paragraphs stay readable on Normal and do not accidentally match heading styling
- A named v5 file ({{code:sm1_doc1_from_template_v5}} or {{code:sm1_styles_practice_v5}}) is saved inside your {{code:sm1}} Specialism folder
Unlock the full learning experience
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.
This lesson is copyright of Coding Ireland 2017 - 2025. Unauthorised use, copying or distribution is not allowed.