Proofreading, Publishing and Producing Finished Work

The zine that almost went to print

Your class makes a zine (a small self-published magazine) about winter in your town, to hand out at the local library. Everyone has written and revised. The night before printing, someone notices: the cover says Winter in Elm Bay, the title page says Winter at Elm Bay, one article spells Saskatoon three different ways, and a photo on page 4 was taken from a website with no permission or credit.

The last stage of writing is easy to rush. The Grade 11 curriculum asks you to regularly proofread and correct your writing (3.5), to use presentation features (print and script, fonts, graphics and layout) to improve clarity and appeal for your audience (3.6), and to produce pieces of published work that meet criteria based on the curriculum expectations (3.7). Its examples include peer checks, verifying feedback with reliable resources, using track changes, keeping a file of corrections, choosing a suitable letter format for a specific newspaper editor, and designing a zine for peers.

Proofreading as a routine, not a rescue

Regularly is the key word in the expectation. Proofread at the end of every writing session for a few minutes, not only the night before a deadline.

• Separate passes: one for spelling and homophones, one for punctuation, one for grammar (agreement, case, tense), one for formatting and consistency (names, titles, numbers, headings, citations).
• Consistency check: search (Ctrl+F or Cmd+F) for every proper noun and check it is spelled the same way each time. Check that you used one spelling system (colour everywhere, not sometimes color).
• Read aloud or use text-to-speech; your ear catches missing and doubled words.
• Your correction file. Each time a teacher, peer or tool catches an error, record it by type: the error, the correction, and the rule. Every few weeks, look for patterns. If eight of your last twenty errors are comma splices, you know exactly what to proofread for.

Proofreading marks

When you mark a printed page (your own or a peer's), standard symbols are faster and clearer than rewriting. Publishers and teachers use them, so it is worth knowing the common ones.

Peer proofreading that helps

A fresh reader sees errors you skip. Make peer proofreading useful:

• Agree on the focus: Please check comma splices, MLA citations and spelling of names.
• Mark, don't rewrite. The writer should make the changes.
• Explain briefly: comma splice, agreement, check spelling of Iqaluit.
• Verify before you accept. Peers (and grammar checkers, and AI tools) are sometimes wrong. If a suggestion conflicts with what you learned, check a reliable resource: a dictionary, a style guide such as the MLA Handbook or a university writing centre's guide, or your teacher. You are responsible for every change you accept.

Track changes and comments

In most word processors, turn on Track Changes (Word) or Suggesting mode (Google Docs). Every deletion and insertion is shown, and the writer can accept or reject each one. Comments hold questions and explanations without changing the text. Two good habits: resolve every comment before submitting, and keep a copy of the marked-up draft for your portfolio, since it shows your process.

Publishing: design for your reader

The same words can be published very differently depending on the form and audience.

• A formal essay or report: a plain, readable font at 11 to 12 points, MLA or assigned format, headings for reports, numbered and captioned figures. Design should be invisible: the reader notices only clarity.
• A letter to the editor: the format the publication asks for (often a short email with Letter to the editor in the subject line, your full name and community).
• A zine, poster or brochure for peers: design is part of the message. Use contrast (a large headline, a bold pull quote), a clear focal point (an image), aligned columns, repeated styles for headings, and white space so pages breathe. Handwritten script or hand lettering can make a zine feel personal; keep body text legible.
• Fonts: sans-serif fonts are often easier to read on screens and at small sizes; serif fonts are traditional in long printed text. Use two fonts at most (one for headings, one for body).
• Graphics: use images you made, images with a licence that allows reuse (such as many Creative Commons images, with the credit the licence requires) or public-domain images. Add a caption and credit.

Accessible publishing

• Enough contrast between text and background.
• Do not use colour alone to carry meaning (add labels or patterns).
• Add alt text to images in digital work.
• Use real headings (heading styles) in digital documents, so screen readers can navigate.
• Keep body text large enough to read comfortably.

Producing a finished work

Expectation 3.7 asks for published work that meets criteria: usually that ideas are well developed, organization is logical, form and style suit the purpose, and conventions are correct. Before you submit:

1. Reread the task and tick every requirement (length, form, number of sources, audience).
2. Check the rubric level by level. Honestly: which level does each criterion show? What one change would raise the lowest one?
3. Final proofreading passes, then the consistency check.
4. Format and file: the required layout, file type and file name (for example, Shah_ENG3U_Report.docx or a PDF if asked).
5. Credits: Works Cited, image credits, acknowledgement of any help or tools as your teacher requires.
6. Keep the final version and your marked-up drafts for your portfolio (Lesson 14).