← VCE Data Analytics U4O1

Proofreading text and labels

Carefully reading text, labels and figures to find and fix spelling, wording and number errors before you publish your work.

Part of: VCE Data Analytics - U4O1 - Development and Evaluation — Module 81

Understanding Proofreading text and labels in VCE Data Analytics U4O1

What it does: Saying the title or label out loud slows you down so you notice wording errors before you publish. A fresh pair of eyes catches mistakes, like a wrong year in a title, that the author no longer sees. Proofreading is about finding and fixing spelling, wording and number errors, not about restyling the design. Spelling mistakes in titles make a visualisation look careless and can reduce trust, so fix them before publishing. Proofreading units and numbers means checking that every value has the correct unit so the reader knows what is measured. Swapped digits are a common number error. Proofreading compares figures on the page to the source data.

Common mistakes: Rainfall is misspelt in the axis label. Proofreading should catch it. It should read Y axis: Rainfall (mm). Students is misspelt in the chart title. Titles are the first thing readers see, so fix it to Title: Students by Year.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add Proofreading text and labels to a class →

This module's key terms are also in a printable crossword (Modules 63–83) and word search (Modules 63–105).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
Which is the best description of proofreading a dashboard before publishing?
Reading titles, labels and figures carefully to find and fix errorsChanging the colours so the dashboard looks more attractive
Matches
Max Temp: 310
↓
The figure has a typo (it should be 31.0) and the unit is missing. Check numbers against the source and add the unit, e.g. 31.0 °C.
Applying
Meanings
Term
proofreading
Meaning
Carefully reading text, labels and figures to find and fix spelling, wording and number errors before you publish your work.
Practice
<h2>Average Maths Mark by Year Level</h2>
Testing
Gaps
(chartTitle, axisLabels)
Check Answer
Spots
2X axis: Month
3Y axis: Rainfal (mm)

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Viperfish' badge — Deep Debugger, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. Which is the best description of proofreading a dashboard before publishing?
A. Reading titles, labels and figures carefully to find and fix errors ✓
B. Changing the colours so the dashboard looks more attractive
Proofreading is about finding and fixing spelling, wording and number errors, not about restyling the design.
2. A chart title reads 'Avarage monthly sales'. What should you do?
A. Correct the spelling to 'Average monthly sales' ✓
B. Leave it, because the chart data is still correct
Spelling mistakes in titles make a visualisation look careless and can reduce trust, so fix them before publishing.
3. An axis shows values from 0 to 50 but has no unit. Which fix is better?
A. Change the label to 'Temperature'
B. Change the label to 'Temperature (°C)' ✓
Proofreading units and numbers means checking that every value has the correct unit so the reader knows what is measured.
4. Your source data says 1,250 but your infographic says 1,520. What kind of error is this?
A. A number error that must be corrected to match the source ✓
B. A style choice that does not need to be fixed
Swapped digits are a common number error. Proofreading compares figures on the page to the source data.
5. Which technique helps you notice missing words or clumsy wording in a label?
A. Skimming the text quickly once
B. Reading the text aloud slowly ✓
Reading aloud slows you down, so you hear mistakes your eyes skip over.

Match the Pairs

Title: "Avrage Maths Mark" → A spelling error in a chart title that proofreading should catch and fix to "Average".
Axis label: "Rainfall (mm)" → A correct label that includes its unit, which a proofreader checks is present and right.
Reading aloud helps you hear wording mistakes, such as a missing or repeated word, that your eyes skip over. → Read aloud: "Sales by month, in dollars"
A second reader can spot errors you miss because you are too familiar with your own work. → Reviewer: "Title says 2024 but data is 2025"
Max Temp: 310 → The figure has a typo (it should be 31.0) and the unit is missing. Check numbers against the source and add the unit, e.g. 31.0 °C.
Rainfall (kg): 14 → The unit is wrong because rainfall is measured in millimetres, not kilograms. The label should read Rainfall (mm).

Key Term

proofreading
Carefully reading text, labels and figures to find and fix spelling, wording and number errors before you publish your work.

Fill in the Blanks

1. proofread(chartTitle, axisLabels)
Hint: Type the name of the step that carefully reads text and labels for errors before publishing.
2. IF labelUnit ≠ dataUnit THEN fixLabel
Hint: Type the operator that checks whether two values are not equal, to catch a wrong unit.
3. readAloud(subtitle)
Hint: Type the function that speaks the text out loud so awkward wording and typos stand out.
4. errors ← secondReader.findErrors(title)
Hint: Type the name of the person who gives a fresh pair of eyes on your work.
5. IF labelFigure != sourceFigure THEN fixNumber
Hint: Type the keyword that starts the action to run when the condition is true.

Spot the Error

Question 1
A Title: Rainfall by Month
B X axis: Month
C Y axis: Rainfal (mm)
D Data: Jan 82, Feb 74, Mar 69
Line C — Rainfall is misspelt in the axis label. Proofreading should catch it. It should read Y axis: Rainfall (mm).
Question 2
A Title: Studnets by Year
B X axis: Year level
C Y axis: Number of students
Line A — Students is misspelt in the chart title. Titles are the first thing readers see, so fix it to Title: Students by Year.
Question 3
A Source value: 4.5 km
B Label: 45 km
C Check label matches source
Line B — The decimal point was dropped, so the label says 45 km but the source says 4.5 km. The label should be Label: 4.5 km.
Question 4
A Y axis: Temperature (cm)
B X axis: Day of week
C Data: Mon 24, Tue 27, Wed 31
Line A — cm is a unit of length, not temperature. The unit must match the measure, so it should be (deg C).
Question 5
A FOR each label in chart
B READ label aloud
C IF sounds wrong THEN skip it
D NEXT label
Line C — Reading aloud is meant to find errors so they can be fixed. Skipping a label that sounds wrong leaves the error in. It should be THEN fix it.

Student with a class code? Join your class →