Challenge 2: Multiple Cursors vs. Rename — Not Interchangeable — Solution Walkthrough

What Rename actually is:

Per this chapter's own material, Android Studio's own Rename
refactoring operates on the IDE's actual structural understanding of
the code — which specific declaration a given identifier refers to —
updating every genuine reference across the entire project
automatically and safely, with no risk of accidentally touching an
unrelated piece of text that happens to look similar.

What multiple cursors actually is:

Multiple cursors is a manual, visual editing technique — the person
using it decides where each cursor goes and what gets typed at each
one. It has no understanding of code structure at all; it simply
allows several locations to be edited live and simultaneously,
wherever the cursors happen to be placed.

Why they're not interchangeable:

Rename is structurally safe and automatically scoped to real
references only, but it only performs one specific kind of operation
(renaming a declared identifier). Multiple cursors can perform any
edit at all across several manually chosen locations, but carries no
built-in guarantee about which locations are genuinely related to each
other — that judgment is entirely the user's own responsibility. One
is a narrow, safe, structural operation; the other is a broad,
flexible, manual one — different tools built for different kinds of
tasks, not two names for the same capability.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that the distinction between a structure-aware
refactoring tool and a manual multi-point editing technique is
understood clearly, correctly explaining why "both let you change
several things at once" doesn't make them the same kind of tool.