Challenge 2: Why Simultaneous Editing Is Riskier for a Shared Word File — Solution Walkthrough

Why this is a genuinely different, riskier situation:

A .docx file on a shared network drive is still, fundamentally, a
single file on disk — when two people open it at the same moment,
each application typically loads its own in-memory copy of that
file's contents to work with. If both people then save at
overlapping moments, whichever save happens LAST simply overwrites
whatever the other person just saved, since neither application has
any live awareness of what the other person changed in their own,
separate in-memory copy. Depending on the exact file-locking behaviour
of the shared drive, this can also produce an outright "file is
locked by another user" error, or in the worst case, actual file
corruption if both save operations write to the file at close to the
same instant.

Why a Google Doc doesn't have this same risk:

There is no separate in-memory copy for each person to begin with —
both people's browser sessions are directly connected to the single
live cloud object described in Chapter 1, and every keystroke syncs
to that one shared object continuously as it happens, not as a single
large "save the whole document" operation at the end. There's nothing
analogous to two competing full-document saves overwriting each
other, because there's no "save the whole file" step at all — just a
continuous stream of small, individually-synced changes to the one
object everyone is already looking at.

WHY THIS WORKS AS AN ANSWER
------------------------------
This directly explains WHY Word & PowerPoint Chapter 6's Track Changes
exists as a workaround in the first place — it's specifically designed
to avoid the overwrite-on-save risk this exercise describes, by having
people work on separate tracked copies and reconcile afterward, rather
than risking simultaneous direct edits to the one shared file at all.