Challenge 1: Recreating Steps 1-4 and Spotting Version History's Advantage — Solution Walkthrough

Recreating the steps:

  1. Create a new Google Doc, share it with a second account (or
     simply narrate this step) with Editor access — this is the
     cloud-native "share the object" model from Chapter 1, not
     attaching or sending a copy of a file.
  2. Make edits from both accounts around the same time, noticing
     each account's own labelled cursor and live changes appearing
     without either side saving anything — Chapter 2's simultaneous
     editing.
  3. From the second account, switch to Suggesting mode and propose
     a wording change; from the first account, leave a Comment on a
     different section — Chapter 3's pairing of Suggesting mode and
     Comments.
  4. Delete a paragraph deliberately, then open File > Version
     History, find the version from just before the deletion, and
     restore it — Chapter 4's continuous snapshot model.

The moment Version History gave an option a manual "Save As" habit
wouldn't have:

The paragraph was restored without needing to have manually saved a
backup copy beforehand, and without needing to remember to do so.
Version History had already been continuously recording snapshots in
the background the entire time, purely as a side effect of editing the
Doc normally — there was no separate "remember to save a version
first" step that had to happen before the mistake, the way a manual
Save As habit would require to have any chance of recovering the lost
paragraph.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise is a hands-on confirmation of Chapter 4's own central
point: Version History's value comes specifically from being
automatic and continuous, requiring no advance planning by the person
who ends up needing it — precisely the "different safety net" framing
the chapter used to contrast it with every other course's own
manual-save assumption.