docs: sanitize documentation and generalize upstream reference server citations

docs/cw-route-continuation-audit.md

@@ -37,7 +37,7 @@ Supply offer from captured role variants and equipment. SupplyBox is not
 implemented. Automated offer
 generation checks pass; the new route is not yet verified in the Client.
 
-## Updated FFGO Supply evidence
+## Updated Reference Supply evidence
 
 The user-supplied reference binary has SHA-256
 `00a75ef82614977d951250705250c6ad478ef7cdde717c761f0c70244a84ed10`.
@@ -76,7 +76,7 @@ The native captured Encounter at route 2801 chapter 1 section 4 contains two
 branch displays, each with its own penalty, monster wave and `BOAMLLHPNEC`
 drop. A read-only check of the saved run at chapter 2 section 1 generated its
 next Supply node and four choices on a detached copy; the saved run was not
-written and no Client interaction was performed. The latest FFGO's
+written and no Client interaction was performed. The latest reference implementation's
 `gfRouteFillEliteBranch` constructs branch IDs from the node template's first
 parameter and option kind, resolves difficulty through
 `gfRouteEliteBranchDifficulty`, and builds the reward in
@@ -85,8 +85,8 @@ branches to this Client's option, penalty and difficulty data remains open.
 
 After the final node, `cwAdvanceRouteNode` returns `CW route has no next node`.
 At zero HP, `finishCurrencyWarsBattle` returns `CW defeat settlement requires
-terminal-run handler`. Neither path currently settles the run. FFGO's extracted
-descriptor names settlement reasons Quit=1, HpZero=2, and Finish=3; the current
+terminal-run handler`. Neither path currently settles the run. The extracted
+reference descriptor names settlement reasons Quit=1, HpZero=2, and Finish=3; the current
 Client's obfuscated enum has matching numeric slots, but only Quit=1 has been
 confirmed for the current implementation. The reference `gfSettleSend` builds
 and archives a settlement record before sending the settlement notification.