deploy.

App/wwwroot/HiAPI-docsite/anatomy/by-source/webservice-spa.html

@@ -95,8 +95,8 @@ out where they occur.</p>
 <h2 id="the-one-thing-to-know-first">The One Thing to Know First</h2>
 <p><code>components/</code> is grouped <strong>both ways at the same level</strong>, and that is deliberate rather than untidy:</p>
 <ul>
-<li><strong>Page-scoped</strong> — <code>components/controller/</code>, <code>components/execution/</code> and half of <code>components/mech/</code>
-are chrome for exactly one route.</li>
+<li><strong>Page-scoped</strong> — <code>components/execution/</code> and half of <code>components/mech/</code> are chrome for exactly
+one route.</li>
 <li><strong>Domain-scoped</strong> — <code>components/geom/</code>, <code>components/topo/</code>, <code>components/toolhouse/</code>,
 <code>components/spindle/</code>, <code>components/workpiece/</code> and <code>components/mission/</code> are pulled in from
 wherever the domain surfaces, most often the Control Tree.</li>
@@ -200,7 +200,7 @@ place&rdquo; behaviour the tree pages describe. Documented in
 <a class="xref" href="../platform/session-state.html">Session State</a> for the keep-mounted flag that decides whether a
 collapse unmounts its content.</li>
 <li><code>wwwroot-src/src/components/mission/</code>, <code>.../toolhouse/</code>, <code>.../spindle/</code>, <code>.../preference/</code>,
-<code>.../mech/</code>, <code>.../workpiece/</code> and <code>.../controller/</code> — the domain and page folders named above. The
+<code>.../mech/</code> and <code>.../workpiece/</code> — the domain and page folders named above. The
 <code>*Div.vue</code> suffix inside the Tool House folder is a convention carried over from the legacy Blazor
 components: a Div is an embeddable content fragment with no panel chrome.</li>
 </ul>