deploy.

App/wwwroot/HiAPI-docsite/manual/basics/finding-your-way.html

@@ -96,7 +96,7 @@ described.</p>
 job, in the order a job uses it:</p>
 <ul>
 <li><strong>Tool House</strong> — the tools, one editor per tool</li>
-<li><strong>General Setup</strong> — the equipment: the machine tool, the spindle capability, the background and
+<li><strong>General Setup</strong> — the equipment: the machine tool, the spindle capability, the ambient and
 coolant conditions, the fixture, the workpiece and the controller</li>
 <li><strong>Execution</strong> — the run: the mission that is executed, the program as it was played, and what the
 run reports</li>
@@ -124,9 +124,9 @@ address is <code>/preference/log</code>.</li>
 path of the selection — <em>General Setup / Workpiece / Anchor / Geom To Fixture</em> — which is also how
 these pages name a place in prose; the header shows as much of it as the dock is wide, so a deep
 path arrives truncated.</p>
-<p>General Setup's tree has one root, <strong>General Setup</strong>, holding <strong>Machine Tool</strong>, <strong>Spindle
-Capability</strong>, <strong>Background</strong>, <strong>Coolant</strong>, <strong>Fixture</strong>, <strong>Workpiece</strong> and <strong>Controller</strong>, in that
-order. With a project open, a <strong>CSV Controller</strong> and a <strong>CL Controller</strong> node follow, each behind
+<p>General Setup's tree has four roots — <strong>Mechanism</strong> (holding <strong>Machine Tool</strong>, <strong>Fixture</strong> and
+<strong>Workpiece</strong>), <strong>Spindle Capability</strong>, <strong>Environment</strong> (holding <strong>Ambient Temperature</strong> and
+<strong>Coolant</strong>) and <strong>Controller</strong> — in that order. With a project open, a <strong>CSV Controller</strong> and a <strong>CL Controller</strong> node follow, each behind
 its own Preference checkbox — as siblings of Controller at the same level, not as children of it.
 With no project open neither node is built, whatever the preferences say. Execution's tree has one
 root, <strong>Execution</strong>, holding <strong>Mission</strong> above <strong>Program</strong>.</p>
@@ -253,7 +253,7 @@ page's node instead:</p>
 </tr>
 <tr>
 <td><code>/equipment/background-coolant</code></td>
-<td>General Setup, the Background item</td>
+<td>General Setup, the Environment root (Ambient Temperature / Coolant)</td>
 </tr>
 <tr>
 <td><code>/mission</code></td>

App/wwwroot/HiAPI-docsite/manual/basics/projects.html

@@ -88,7 +88,7 @@
           <h1 id="projects">Projects</h1>
 
 <p>A project is the whole of what a simulation runs against: the machine tool, the spindle capability,
-the background and coolant conditions, the fixture, the workpiece, the tool house, the controller and
+the ambient and coolant conditions, the fixture, the workpiece, the tool house, the controller and
 the NC programs a mission plays. It is a project file together with the folder that file sits in, and
 the <strong>Project</strong> dropdown on the menu bar is where one is created, opened, saved and closed. The
 equipment and mission screens are editors on whichever project is open, so a change of project

App/wwwroot/HiAPI-docsite/manual/setup/coolant.html

@@ -93,10 +93,11 @@ temperatures and everything downstream of them — and setting them needs no hea
 all, because the cooling types ship as ready-made files.</p>
 <h2 id="where-it-is">Where it is</h2>
 <p>The General Setup page, at <code>/general-setup</code>, reached from the menu bar's <strong>Page</strong> dropdown.
-<strong>Background</strong> (<code>/general-setup?tree=equipment/background</code>) and <strong>Coolant</strong>
-(<code>/general-setup?tree=equipment/coolant</code>) are two leaves of the Control Tree, sitting together
-between Spindle Capability and Fixture. Both are inert until a project is open: the fields are
-disabled and the panel says so.</p>
+<strong>Ambient Temperature</strong> (<code>/general-setup?tree=equipment/background/environment-temperature</code>) and
+<strong>Coolant</strong> (<code>/general-setup?tree=equipment/background/coolant</code>) are the two leaves of the Control
+Tree's <strong>Environment</strong> root, between Spindle Capability and Controller (the ids keep the legacy
+<code>background</code> spelling). Both are inert until a project is
+open: the fields are disabled and the panel says so.</p>
 <p>The <strong>Coolant</strong> leaf selected on a demo project. The panel under the tree opens with the file row —
 the <strong>Select</strong> dropdown, the path field reading <em>No coolant file (saved inline)</em>, and <strong>Save As&hellip;</strong>
 — then the read-only <strong>Name</strong> and <strong>Note</strong> of whatever file is loaded, and then the condition's own
@@ -190,17 +191,19 @@ loses its <code>.default</code> marker on the way, because that marker means <em
 yours.</p>
 <p>The result is loadable into the next project through the same <strong>Select</strong> dropdown — which is the
 point of saving one: a shop with its own measured coolant performance describes it once.</p>
-<h2 id="background-temperature">Background temperature</h2>
-<p>The <strong>Background</strong> leaf carries a single field, <strong>Background Temperature</strong> in °C: the surrounding
-temperature the thermal model works against. It defaults to 25 °C, it belongs to the project exactly
-as the coolant condition does, and it is read by the same milling-temperature model and by the feed
-optimizer, so it is not a display setting.</p>
-<p>Set it to the shop's real ambient. There is no file to load and nothing else to configure: one
-number, applied to the whole project.</p>
+<h2 id="ambient-temperature">Ambient temperature</h2>
+<p>The <strong>Ambient Temperature</strong> leaf carries a single field of the same name, in °C: the shop-floor ambient
+temperature — the temperature the workpiece, the cutter, the chips and the spindle start at, and the
+one the spindle cools toward. The cutting zone itself convects to the <strong>Coolant</strong> leaf's coolant
+temperature, not to this one. It defaults to 25 °C, it belongs to the project exactly as the coolant
+condition does, and it is read by the same milling-temperature model and by the feed optimizer, so
+it is not a display setting.</p>
+<p>Set it to the shop's real ambient temperature. There is no file to load and nothing else to
+configure: one number, applied to the whole project.</p>
 <h2 id="see-also">See Also</h2>
 <ul>
 <li><a class="xref" href="../../technique/milling-physics/coolant-model.html">Coolant Model</a> — the coefficients, the M-code that selects one, the shipped presets and the file format</li>
-<li><a class="xref" href="../../anatomy/general-setup/background-coolant.html">Background / Coolant Page</a> — the Control-Tree editor for these values, field by field</li>
+<li><a class="xref" href="../../anatomy/general-setup/background-coolant.html">Environment: Ambient Temperature / Coolant Page</a> — the Control-Tree editor for these values, field by field</li>
 <li><a href="index.html">Setup</a> — the rest of the pre-simulation configuration</li>
 </ul>
 

App/wwwroot/HiAPI-docsite/manual/setup/index.html

@@ -112,7 +112,7 @@
 </ul>
 <h2 id="environment">Environment</h2>
 <ul>
-<li><a href="coolant.html">Coolant</a> — Pick how the cutting zone is cooled, and set the ambient temperature it works against</li>
+<li><a href="coolant.html">Coolant</a> — Pick how the cutting zone is cooled, and set the shop's ambient temperature the thermal model starts from</li>
 </ul>
 <p>Which NC vocabulary a controller brand honours is not a setup task and no longer lives here — it is
 <a href="../../technique/nc-dialects/index.html">NC Dialects</a>. Neither is what a cutter's quantities mean: the

App/wwwroot/HiAPI-docsite/manual/utilities/mech-builder.html

@@ -195,7 +195,8 @@ runtime — a machine's moving axes are branches carrying those.</p>
 <p><img src="mech-builder-img/branch-transformer.en.png" alt="The same mechanism with a branch picked instead: the graph edge is stroked green, the Identity card names the two anchors it joins with an arrow between them, and the Transformer card reads Dynamic Rotation over a rotation axis, an angle and a pivot"></p>
 <p><em>At <code>/util/mech-builder</code>, with a branch picked. A <code>Dynamic Rotation</code> carries the axis it turns
 about and the pivot it turns around; the angle is the value a run varies, so the number shown here
-is the resting one. The sentence under the fields names the same three parts.</em></p>
+is the resting one. The sentence under the fields names two of those parts, the axis and the
+angle, and says that the angle is the one a run varies.</em></p>
 <h2 id="see-also">See Also</h2>
 <ul>
 <li><a href="file-explorer.html">File Explorer</a> — the server-side browser behind this page's Load and Save As dialogs, and the roots they offer</li>