deploy.

2026-09-11 03:46:11 +08:00
parent 45b9f9ed5d
commit b7f55aa631
114 changed files with 3646 additions and 576 deletions
@@ -207,10 +207,10 @@ counts sit below it and follow what you type.</p>
 <p><strong>Nothing is checked while you type.</strong> The text is stored exactly as written, and a mistake in it
 surfaces when the mission plays it — in <strong>NC Diagnostics</strong>, see
 <a href="when-something-goes-wrong.html">When Something Goes Wrong</a>.</p>
-<p>The demo mission's short hand-written pass, at <code>/execution?tree=execution/mission/4</code>. The title
+<p>The demo mission's short hand-written pass, at <code>/execution?tree=execution/mission/5</code>. The title
 above the editor is what the row brackets, and the line and character counts below it are the whole
 of the feedback this editor gives.</p>
-<p><img src="playing-a-program-img/nc-code.en.png" alt="The NC Code command panel: a Title field reading Face check above a monospace text area holding a short NC program, with line and character counts and the Trim Blank Lines and Clear buttons below it"></p>
+<p><img src="playing-a-program-img/nc-code.en.png" alt="The NC Code command panel: a Title field reading Inline finishing pass above a monospace text area holding a short NC program, with line and character counts and the Trim Blank Lines and Clear buttons below it"></p>
 <h2 id="after-it-has-played">After it has played</h2>
 <p>Every program a session read appears under the <strong>Program</strong> branch, with the passes that went over it
 and the marks the run left on each line. That is where you see what happened to a line, as opposed