Challenge 1: Naming a Version — Solution Walkthrough

Steps:
  1. File > Version History > See Version History.
  2. Locate a meaningful point in the list (e.g. right before sending
     a draft out, or after finishing a major section).
  3. Click the three-dot menu next to that version and choose "Name
     this version," giving it a descriptive name like "Draft sent to
     client."

Why naming is useful given how many auto-generated checkpoints exist:

Version History creates checkpoints continuously and automatically —
based on time intervals and edit activity, not on anyone deciding a
moment was significant. For a document worked on over hours or days,
this can easily produce dozens or hundreds of auto-timestamped
entries, most of which look identical and unremarkable at a glance.
Naming the SPECIFIC version that actually matters — "Draft sent to
client" — makes it instantly findable later without needing to guess
which of many similar timestamps corresponds to that meaningful
moment, or manually compare content across several candidates to
figure out which one is "the" version you actually want.

WHY THIS WORKS AS AN ANSWER
------------------------------
This directly demonstrates this chapter's own point about naming: the
sheer VOLUME of automatic checkpoints (a genuine strength for
comprehensive protection) is exactly what makes naming a specific,
meaningful version worthwhile — without it, finding the right version
later among so many similar-looking automatic ones would be
needlessly difficult.