Digital Literacy

Lessons

Docs for Writing & Collaboration

Lesson

Why This Lesson Matters

Strong writing wins marks, jobs, and trust. The difference between a messy page and a professional one is not talent—it’s structure. Around the world, high-performing students use styles for headings, short paragraphs, tidy lists, and a small table to make facts clear. They give and receive comments without breaking the master file, and they export a clean PDF that prints perfectly at a shop. In Sri Lanka, this matters even more: shared devices, low data, and print shops punish messy files. This lesson gives you a simple, repeatable way to turn a blank page into a clear one-page brief and collaborate calmly.

“Neat pages earn easy marks.”

Step 1: Set Up the Page (once, then save as a template)

Before you write, fix the frame. A tidy frame makes tidy writing.

Page & margins: A4; margins 2–2.5 cm (default is fine).
Font: A clean, Unicode font (e.g., Noto Sans or a standard system serif). Size 11–12 for body, 14–16 for H2.
Line spacing: 1.15–1.5; add space after paragraph (6–8 pt) instead of pressing Enter twice.
Language: set spell-check to English (UK); if writing Sinhala/Tamil sections, add those keyboards (see Mobile Tip).
File name: and save it inside Docs (Lesson 3 rule).

Apply this once and save as “Brief Template” so you don’t redo it every time.

Step 2: Structure First—then Sentences

Good writing is a clear outline turned into short paragraphs. Use this proven one-page frame:

Title (H1) – one crisp line that names the topic and angle
Purpose (H2) – 2–3 lines: who this is for and what they need
Key Points (H2) – 2–3 short sections (H3 optional) with PEEL
Table (optional) – a 2–3 column table summarising facts
Action / Next Steps (H2) – 2–3 lines: what to do now
Works Cited (H2) – 1–3 sources (Lesson 10 style)

PEEL keeps each paragraph tight: Point (topic sentence), Evidence (fact/example), Explain (why it matters), Link (to the question or next point). Aim for 3–5 sentences per paragraph.

“Headings guide; sentences carry.”

The Golden Rule

Attempt → Hint → Verify → Produce. Outline first, ask for help second, check facts, then export PDF.

Bad vs Better — Paragraphs

Weak paragraph	Strong paragraph (PEEL)
“Budgeting is important for students. It helps save.”	Point: A weekly budget gives students control over small leaks. Evidence: In a 7-day diary, snacks and short rides often exceed LKR 1,500. Explain: Seeing totals by category helps choose cheaper swaps. Link: This supports the 50/30/20 plan in Lesson 4.

Step 3: Use Styles, Lists, and a Small Table

Styles (H1/H2/Normal) are not decoration—they’re structure. They make navigation, consistent formatting, and PDF output easy.

Apply H1 to the title, H2 to section headings, Normal to body.
Use bulleted lists for 3–5 quick items; numbered lists for steps.
Insert a table for compact facts (e.g., “Cost | Benefit | Tip”). Keep tables light—no merged cells, short labels, and a clear header row.

Mini Table Example (copy this pattern):

Cost (Monthly)	Why it’s worth it	Tip
LKR 150 for data	Upload/backup without delay	Use Wi-Fi only for large files
LKR 40 printing	Clean PDF avoids reprints	Export once; test on phone

Short, readable tables beat long paragraphs for comparisons.

Step 4: Comment, Suggest, Resolve—without breaking the master

Collaboration is how good drafts become excellent. Do it safely.

Comment to ask or suggest without changing the text. Select, Insert → Comment, write one issue per comment, use @name to assign.
Suggesting / Track Changes to edit with trace. Turn on Suggesting (Docs) or Track Changes (Word). The owner can accept/reject.
Resolve comments once fixed to keep the page clean.
Default share: Can comment (Lesson 11). Upgrade to Can edit only for the 1–2 active writers—agree roles first.

Comment Etiquette: be specific (“Shorten to one sentence”), friendly (“Great point—could we add a source?”), and brief. One issue per comment means faster fixes.

“Comment first. Edit last.”

Step 5: Produce a Clean PDF for Print & Sharing

When you’re done, export PDF to Outputs. PDFs preserve fonts (including Sinhala/Tamil), spacing, and page breaks—vital for print shops and email attachments.

Check before export: headings applied, spacing tidy, no double spaces, table fits page width.
Export and open on your phone to confirm it renders correctly.
Share the PDF with teachers/print shops; keep the editable master inside Docs.

Step 6: Bilingual & Low-Data Friendly Writing (Sri Lanka-ready)

If you include Sinhala/Tamil terms, put the English term first, then the local term in brackets on first use. Example: Compounding (සංකීර්ණීකරණය).
Use clear words and short sentences (average 12–18 words).
Avoid large images; one small table often beats a photo.
If you must include an image, keep it compressed and add a one-line caption (source and year).

Guided Production: Build Your One-Page Brief Now

Topic: pick one you can explain (e.g., “How to create a study week plan”). Audience: O/L student or job-seeker—choose one.

Outline (Attempt, 5–7 min). Write H1 and 3 H2s; add a 3-row table title.
Draft (10–15 min). Write one PEEL paragraph under each H2.
Self-check (5 min). Remove duplicated words; shorten long sentences.
Comment round (5 min). Add three self-comments: (a) clarity, (b) evidence missing, (c) sentence to shorten.
Revise (10 min). Accept/reject suggestions; tidy spacing.
Produce (3 min). Export PDF to Outputs; open on phone to confirm.

Quick Win Turn one long paragraph into PEEL. Keep the first sentence as your Point; move one fact to Evidence; add one Explain sentence; end with a Link to the next section.

Artifact to Produce

Brief_v1 (Doc) – your one-page brief with proper styles, a small table, and three comments you added to yourself.
Brief_v2 (PDF) – revised after addressing the comments. Save in Outputs as: YYYY-MM-DD_One-Page-Brief_V2.pdf

Suggested section headings (copy):

H1: Study Week, Made Simple
H2: Purpose
H2: Three Moves that Work
H2: Quick Table: Habit → Why → Tip
H2: Next Steps
H2: Works Cited

Self-Verification (SV) Checklist

File named with date + topic + V# and saved in Docs
H1/H2/Normal styles applied (no manual bold for headings)
3–5 short paragraphs using PEEL
One list (bullets or numbers) used appropriately
One small table with a header row; fits page width
Three comments added and resolved/acted upon
PDF exported to Outputs and opens correctly on phone
Works Cited box added if you used any facts/definitions
Sinhala/Tamil terms (if any) shown in Unicode and defined once
Brief_v1 (Doc) and Brief_v2 (PDF) stored in the right folders

Mobile Tip (Android & iOS)

In the Docs app, tap the A icon to open Styles; apply Title/H1/H2/Normal—don’t format by hand.
To insert a table, tap + → Table → 2×3 (start small).
Long-press text to Comment; use @ to mention a collaborator later.
Add the Sinhala/Tamil keyboard in Settings → Language & input (Unicode).
Slow data? Toggle Available offline for your brief and finish drafting without internet.

Stuck? Fast Fixes

Headings look wrong after export: reapply Styles (H1/H2/Normal); avoid mixing manual bold with styles.
Table breaks across pages: reduce columns, shorten labels, or set a smaller font inside the table only.
Weird spacing: remove double line breaks; use space after paragraph.
Teacher can’t open the file: send the PDF and a view-only link to the Doc; test the link in incognito first.
Sinhala/Tamil boxes show as squares: confirm Unicode font; export PDF and print that.

Common Roadblocks (and simple fixes)

“Everyone edited everything.” Switch sharing to Can comment; use Suggesting for a single review round (Lesson 11 will deepen this).
“Final_final_v3 syndrome.” Keep one master in Docs; name a version after each review; export PDF to Outputs only at the end.
“My paragraphs ramble.” Make the first sentence a short Point; cut any sentence that doesn’t support it.
“Looks fine on phone, messy on PC.” Always check the PDF on a second device (or incognito) before submitting.

Keeping Yourself Motivated

Professional documents come from process, not pressure. Each time you apply styles, write with PEEL, add three comments, and export a clean PDF, you are building a habit employers recognise: clarity, control, and care. Celebrate small wins: “One page, on time, zero reprints.”

“Write for the reader. Format for the future.”

Your First Step Is Complete

You can now turn a blank page into a tidy one-page brief, collaborate safely with comments and suggesting, and export a PDF that prints cleanly. Save Brief_v1 (Doc) and Brief_v2 (PDF) to the correct folders, tick the SV checklist, and add “Brief Template” to your drive for reuse.

Idasara