Richard Lundeen (richlundeen) · Oct 24, 2026 · Oct 24, 2026
diff --git a/doc/code/registry/0_registry.md b/doc/code/registry/0_registry.md
@@ -171,9 +171,7 @@ Construction and reference resolution remain owned by `ScorerRegistry`.
 Scorer list responses build identifiers only for the requested page. Runtime
 replacement clears the cached scorer service so requests use the new registry.
 
-The backend owns file-upload handling and cleanup, not the registry. See the
-[registry API migration notes](../../gui/0_gui.md#registry-api-migration-notes)
-for the REST contract and temporary compatibility behavior.
+The backend owns file-upload handling and cleanup, not the registry.
 
 ## Attack Class Registry
 

diff --git a/doc/code/setup/0_setup.md b/doc/code/setup/0_setup.md
@@ -34,7 +34,7 @@ The CoPyRIT configuration page separates **Save** from **Reinitialize PyRIT**.
 On a single-process, single-replica backend, administrators can apply saved
 configuration, environment documents, and custom initializer scripts without
 restarting Python. The saved `.pyrit_conf` must set `enable_live_reinitialization: true`.
-See [the GUI reinitialization guide](../../gui/0_gui.md) for status, failure behavior, and deployment limits.
+Use the [GUI Configuration page](../../gui/0_gui.md#configuration) to manage these sources.
 
 The backend first validates the saved sources without changing live setup state. It rejects live apply while any
 runtime work is active. When the runtime is idle, it closes admission, checks for work again, and then rebuilds

diff --git a/doc/gui/0_gui.md b/doc/gui/0_gui.md
diff --git a/doc/gui/images/analytics.png b/doc/gui/images/analytics.png
diff --git a/doc/gui/images/attack_history.png b/doc/gui/images/attack_history.png
diff --git a/doc/gui/images/chat.png b/doc/gui/images/chat.png
diff --git a/doc/gui/images/configuration.png b/doc/gui/images/configuration.png
diff --git a/doc/gui/images/datasets.png b/doc/gui/images/datasets.png
diff --git a/doc/gui/images/home.png b/doc/gui/images/home.png
diff --git a/doc/gui/images/operations.png b/doc/gui/images/operations.png
diff --git a/doc/gui/images/registry.png b/doc/gui/images/registry.png
diff --git a/doc/gui/images/scanner.png b/doc/gui/images/scanner.png
diff --git a/doc/gui/images/technique_execute.png b/doc/gui/images/technique_execute.png
diff --git a/doc/gui/images/technique_execute_objective.png b/doc/gui/images/technique_execute_objective.png
diff --git a/frontend/README.md b/frontend/README.md
@@ -79,8 +79,8 @@ Expanded details stack each label above its stored value.
 ## Resuming a scenario run
 
 Failed runs offer **Resume run** on the run page and **Resume** in Scanner History.
-See the [GUI guide](../doc/gui/0_gui.md#resuming-a-failed-scanner-run) for resume
-behavior and the saved launch configuration requirement.
+See the [GUI History guide](../doc/gui/0_gui.md#history) for a short overview
+of resume behavior.
 
 ## Default labels after runtime changes
 
@@ -99,8 +99,7 @@ and keep that attack's attribution.
 
 Open **Analytics** to filter saved results, compare SDK-computed outcome
 statistics, and drill into matching attacks. See the
-[analytics GUI guide](../doc/gui/0_gui.md#attack-results-analytics) for cohort
-semantics, denominators, time bounds, URL sharing, and refresh behavior.
+[analytics GUI guide](../doc/gui/0_gui.md#analytics) for a short overview.
 The implementation follows
 [part 5 of the analytics roadmap](https://gist.github.com/romanlutz/34230aba87f7fa07996772a4099e9a78).