Writing together
Introduced| English | Meaning |
|---|---|
| cloud document/klaʊd ˈdɒkjuːmənt/ | A document stored on a remote service and accessed or edited over a network. |
| style/staɪl/ | The characteristic way content is expressed or presented, including choices of language, tone and form. |
| comments/ˈkɒments/ | Notes added to a document to explain, question or give feedback on particular parts of it. |
| suggestions/səˈdʒestʃnz/ | An editing mode that records proposed changes for another person to accept or reject. |
| version history/ˈvɜːʃn ˈhɪstəri/ | version history |
Two people changed the same conclusion
- Mei changes the final figure while Arun explains the old figure. A shared file alone has not made their report consistent.
- A cloud document 云端文档 gives the team a shared working copy. Agree how edits, reviews and the final version will be managed.
Agree an outline and a reviewer
- Split the report into sections with a named writer, a review partner and a deadline. Agree style 文体: spelling, terminology and tense appropriate to each section.
- Link each conclusion to the evidence section it uses. Writing sections separately is useful, but the team must review the joins.
Two teammates must produce one report. Which plan best supports a consistent final draft?
Difficulty 1/5 · 100 coins + a small bonus on first completion today
Section ownership clarifies responsibility; review of the joins checks that claims and evidence agree.
Make the disagreement easy to resolve
- Comments 批注 ask a question or explain a problem. Suggestions 建议模式 propose a visible edit that can be accepted or rejected where the tool supports it.
- Name the location and reason: “In paragraph 2, does ‘it’ mean the survey or the database?” Agree when direct edits are appropriate, such as fixing a typo.
Original: “It improved by 12.” Useful comment: “What improved, and is 12 a count or a percentage?” The writer checks the data before revising the claim.
A sentence says “It improved by 12.” Which comment helps the writer check it?
Difficulty 1/5 · 100 coins + a small bonus on first completion today
The first comment identifies two specific information gaps without judging the person.
A teammate writes “The new system is better.” Write a useful review comment.
Difficulty 3/5 · 200 coins + a small bonus on first completion today
Example: “Better than which system, and what measure in our data supports that comparison?”
Use history as one piece of evidence
- Version history 版本历史 can help identify edits and recover earlier work. Save a named checkpoint before a major revision if your tool supports it.
- History does not capture every contribution. Keep a short task log for research, discussion and offline drafts, and agree how offline work will be merged.
One late paste does not prove that a student did no work. Explain the contribution with drafts and task records. Before restoring an old version, protect newer contributions and tell the team.
A single late paste proves that its author did no earlier work.
Difficulty 1/5 · 100 coins + a small bonus on first completion today
Offline drafts and research may precede the paste. Use task records, drafts and discussion alongside history.
A paragraph was deleted after other teammates added new work. What is the safest first response?
Difficulty 1/5 · 100 coins + a small bonus on first completion today
Whole-version restoration may remove newer contributions. Identify the missing content and agree how to recover it.
Give each person the access they need
- Writers need editing access; reviewers may need commenting access; a reader may need viewing access only. Avoid a public editing link for private work.
- Test the final link with the intended reader's permissions. Check the brief for the required format and keep a backup export if appropriate.
Match each role to the least access needed for its stated task.
Difficulty 2/5 · 140 coins + a small bonus on first completion today
Choose permissions by task. A reader does not need a public editing link.
Finish with a cross-check
- One reviewer checks totals, citations, wording and section links; each writer confirms any change to their evidence or meaning.
- For your next group report, produce an outline, a responsibility table, one resolved comment and a checked final link.
A shared copy needs shared rules: ownership, review, access and a final checkpoint. Judge contributions using evidence from the whole process.
Tool guidance: Google Docs version history and suggested edits.
Which belong in a final cross-check? Select all that apply.
Difficulty 2/5 · 140 coins + a small bonus on first completion today
Correct evidence, consistent language and working access matter; a filename is not proof of final review.
For this workflow, arrange the main stages before submission.
Difficulty 3/5 · 200 coins + a small bonus on first completion today
Drafting follows the outline; cross-review needs a draft; final confirmation follows review.