deploy.

App/wwwroot/HiAPI-docsite/anatomy/conventions/translation-remarks.html

@@ -164,16 +164,11 @@ MIME-ish strings (<code>STL</code>, <code>*.hincproj</code>) · units (<code>mm<
 localStorage keys and series identifiers — anything a machine compares. Language self-names
 (English, 简体中文, 繁體中文) stay in their own language in every locale. The full list lives with
 the bundles, in the i18n folder's README.</p>
-<h2 id="terms-carried-by-the-desktop-client">Terms Carried by the Desktop Client</h2>
-<p>Three milling-cutter surfaces exist only on the WPF client, and their terms belong to the same
-contract, so none of the words is reused elsewhere:</p>
-<ul>
-<li>Insert-Cutter 刀片 — a tab on <code>Mech/ToolHouse/MillingCutterPanel.xaml</code></li>
-<li>Flute-Inner-Beam 刃中芯 — the tab served by <code>Mech/ToolHouse/FluteInnerBeamPanel.xaml</code></li>
-<li>Cutter Integral Mode 刀頭形式 — a labelled tab there as well; the web application carries the
-same choice as the <code>integralMode</code> datum, which decides whether the Tool House material section
-offers a separate shank material, and shows no label of its own</li>
-</ul>
+<h2 id="a-choice-that-carries-no-label">A Choice That Carries No Label</h2>
+<p>The cutter's integral mode reaches the web application as the <code>integralMode</code> datum rather than as a
+named field: it decides whether the Tool House material section offers a separate shank material,
+and shows no label of its own. A term with no visible string is still part of the contract — it has
+to be settled before anything renders a value derived from it.</p>
 <h2 id="source-code-path">Source Code Path</h2>
 <p>See <a class="xref" href="../index.html">HiNC App Anatomy</a> for git repository links.</p>
 <ul>