deploy.

App/wwwroot/HiAPI-docsite/release-note/upgrading-to-3.2/index.html

@@ -88,7 +88,7 @@
           <h1 id="upgrading-from-31175-to-32">Upgrading from 3.1.175 to 3.2</h1>
 
 <p>These pages are the long form of the 3.1.175 → 3.2 line — the 3.2.7 entry and the
-<a href="../index.html">3.2.24</a> incremental drop. They exist because 3.2 is not
+<a href="../index.html">3.2.24 and 3.2.26</a> incremental drops. They exist because 3.2 is not
 an increment on the last release most callers hold — it is the accumulation of everything that
 landed after the 3.1.175 package set, delivered in one step.</p>
 <p>Read them in order the first time. The two sections that decide whether an upgrade is a recompile or
@@ -99,9 +99,9 @@ capability you can adopt when you need it.</p>
 <h5>Important</h5>
 <p>Read the <strong>Adoption status</strong> note on the <a href="../index.html">release-note page</a> before planning around this.
 The short version: 3.2 is published for review, verification is still in progress across most
-areas, <strong>NC optimization is not finished on this line</strong>, and <strong>SoftNc canned-cycle indexing
-with rotary A/B/C words is not finished</strong> — work that depends on either should stay on 3.1,
-serviced as <code>3.1.175.&lt;patch&gt;</code>, or run with SoftNc off for the rotary-cycle case.</p>
+areas and <strong>NC optimization is not finished on this line</strong> — work that depends on it should stay
+on 3.1, serviced as <code>3.1.175.&lt;patch&gt;</code>. The 3.2.24 hold on SoftNc canned cycles that index a
+rotary axis is lifted in 3.2.26.</p>
 </div>
 <h2 id="pages">Pages</h2>
 <p>Ordered the way to read them: what the package numbers mean, then the two sections that decide whether the upgrade is a recompile or an afternoon, then the new capability, adopted when needed.</p>