deploy.

App/wwwroot/HiAPI-docsite/manual/run/building-a-mission.html

@@ -144,8 +144,8 @@ is what narrows them, and the first result is highlighted ready for <kbd>Enter</
 <h2 id="read-a-row">Read a row</h2>
 <p>Each row shows the command's kind followed by the detail that identifies it, in brackets. Where you
 can name a command that detail is the title you typed, so a row still says what it is after it has
-been named: <code>List [Roughing]</code>, <code>NC Code [Face check]</code>. Where you cannot, the command brackets what
-it holds instead — <code>Program File [NC/facing.ptp]</code>, <code>Machining Resolution [0.25 mm]</code>,
+been named: <code>List [Roughing]</code>, <code>NC Code [Inline finishing pass]</code>. Where you cannot, the command brackets what
+it holds instead — <code>Program File [NC/circle.ptp]</code>, <code>Machining Resolution [1 mm]</code>,
 <code>Collision Detection [On]</code> — so a mission is readable without opening anything.</p>
 <p>Beside the label sit four buttons — <strong>up</strong>, <strong>down</strong>, <strong>duplicate</strong> and <strong>delete</strong>. Up and down are
 disabled at the ends of the list. Delete asks first, in a dialog naming the command. Duplicate is a
@@ -165,11 +165,12 @@ mission can be grouped by operation rather than left flat.</p>
 <p>A list carries an optional title, entered on its own node above the embedded editor. The row reads
 <code>List</code> while the title is empty and <code>List [title]</code> once it says something; a title of nothing but
 spaces counts as unset. The Mission root is the one list with no title field — it reads <strong>Mission</strong>.</p>
-<p>The demo mission at <code>/execution?tree=execution/mission</code>: three groups and four loose entries. The
-tree above shows <strong>List [Setup]</strong> opened, with the three settings commands inside it bracketing
-their values; the editor below shows the same seven entries as rows. The greyed <strong>Script</strong> row is an
-entry left in place with its checkbox cleared — part of the mission, and not run.</p>
-<p><img src="building-a-mission-img/grouped-mission.en.png" alt="The Mission branch of the Control Tree with List Setup expanded over Machining Resolution 0.25 mm, Collision Detection On and Physics On, then NC Optimization Config, List Roughing, List Finishing, NC Code Face check, Post-Execution and a greyed Script Export result row with its checkbox cleared; below it the list editor shows the same seven entries, each with up, down, duplicate and delete buttons, above the line reading that commands run top-down"></p>
+<p>The demo mission at <code>/execution?tree=execution/mission</code>: two groups and seven loose entries. The
+tree above shows <strong>List [Roughing]</strong> and <strong>List [Finishing]</strong> opened, with the two Program File
+entries inside each bracketing their files; the editor below shows the same nine root entries as
+rows. The greyed <strong>Program File</strong> and <strong>Post-Execution</strong> rows are entries left in place with their
+checkboxes cleared — part of the mission, and not run.</p>
+<p><img src="building-a-mission-img/grouped-mission.en.png" alt="The Mission branch of the Control Tree showing Machining Resolution 1 mm and Collision Detection On, then List Roughing expanded over Program File NC/circle.ptp and Program File NC/drill_slot.ptp, List Finishing expanded over Program File NC/side.ptp and Program File NC/slide.ptp, then Program File NC/circle.ptp, NC Code Inline finishing pass, a greyed Program File NC/slide-test-resolution-script.ptp with its checkbox cleared, NC Optimization Config and a greyed Post-Execution with its checkbox cleared; below it the list editor shows the same nine root entries under an Add Command button and a Commands badge reading 9, each row with up, down, duplicate and delete buttons, above the line reading that commands run top-down"></p>
 <h2 id="reorder-and-move-in-and-out">Reorder, and move in and out</h2>
 <p>Up and down move an entry within its own list and never change which list owns it. Dragging does
 more, and where you drop decides which:</p>