Deploying to gh-pages from @ 7083879 🚀

Code_Overview.html

@@ -1851,10 +1851,10 @@ <h2 id="adding-new-kinematics">Adding new kinematics<a class="headerlink" href="
    be efficient as it is typically only called during homing and
    probing operations.</li>
 <li>Other methods. Implement the <code>check_move()</code>, <code>get_status()</code>,
-   <code>get_steppers()</code>, <code>home()</code>, and <code>set_position()</code> methods. These
-   functions are typically used to provide kinematic specific checks.
-   However, at the start of development one can use boiler-plate code
-   here.</li>
+   <code>get_steppers()</code>, <code>home()</code>, <code>clear_homing_state()</code>, and <code>set_position()</code>
+   methods. These functions are typically used to provide kinematic
+   specific checks. However, at the start of development one can use
+   boiler-plate code here.</li>
 <li>Implement test cases. Create a g-code file with a series of moves
    that can test important cases for the given kinematics. Follow the
    <a href="Debugging.html">debugging documentation</a> to convert this g-code file

G-Codes.html

@@ -5250,15 +5250,18 @@ <h4 id="force_move_1">FORCE_MOVE<a class="headerlink" href="#force_move_1" title
 state; issue a G28 afterwards to reset the kinematics. This command is
 intended for low-level diagnostics and debugging.</p>
 <h4 id="set_kinematic_position">SET_KINEMATIC_POSITION<a class="headerlink" href="#set_kinematic_position" title="Permanent link">&para;</a></h4>
-<p><code>SET_KINEMATIC_POSITION [X=&lt;value&gt;] [Y=&lt;value&gt;] [Z=&lt;value&gt;]</code>: Force
-the low-level kinematic code to believe the toolhead is at the given
-cartesian position. This is a diagnostic and debugging command; use
-SET_GCODE_OFFSET and/or G92 for regular axis transformations. If an
-axis is not specified then it will default to the position that the
-head was last commanded to. Setting an incorrect or invalid position
-may lead to internal software errors. This command may invalidate
-future boundary checks; issue a G28 afterwards to reset the
-kinematics.</p>
+<p><code>SET_KINEMATIC_POSITION [X=&lt;value&gt;] [Y=&lt;value&gt;] [Z=&lt;value&gt;]
+[CLEAR=&lt;[X][Y][Z]&gt;]</code>: Force the low-level kinematic code to believe the
+toolhead is at the given cartesian position. This is a diagnostic and
+debugging command; use SET_GCODE_OFFSET and/or G92 for regular axis
+transformations. If an axis is not specified then it will default to the
+position that the head was last commanded to. Setting an incorrect or
+invalid position may lead to internal software errors. Use the CLEAR
+parameter to forget the homing state for the given axes. Note that CLEAR
+will not override the previous functionality; if an axis is not specified
+to CLEAR it will have its kinematic position set as per above. This
+command may invalidate future boundary checks; issue a G28 afterwards to
+reset the kinematics.</p>
 <h3 id="gcode">[gcode]<a class="headerlink" href="#gcode" title="Permanent link">&para;</a></h3>
 <p>The gcode module is automatically loaded.</p>
 <h4 id="restart">RESTART<a class="headerlink" href="#restart" title="Permanent link">&para;</a></h4>