deploy.

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>