stepper_enable: Move motor_off() logic to stepper_enable.py

Directly disable all the stepper motors on a global motor_off() from
the StepperEnable() class in stepper_enable.py.  This simplifies the
toolhead and kinematic classes.

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>

1 files changed, 3 insertions, 4 deletions

diff --git a/docs/Code_Overview.md b/docs/Code_Overview.md
index 3459bd31..7b26f85d 100644
--- a/docs/Code_Overview.md
+++ b/docs/Code_Overview.md
@@ -336,10 +336,9 @@ Useful steps:
    need to be efficient as it is typically only called during homing
    and probing operations.
 5. Other methods. Implement the `check_move()`, `home()`,
-   `motor_off()`, `set_position()`, and `get_steppers()` methods.
-   These functions are typically used to provide kinematic specific
-   checks.  However, at the start of development one can use
-   boiler-plate code here.
+   `set_position()`, and `get_steppers()` methods. These functions are
+   typically used to provide kinematic specific checks. However, at
+   the start of development one can use boiler-plate code here.
 6. Implement test cases. Create a g-code file with a series of moves
    that can test important cases for the given kinematics. Follow the
    [debugging documentation](Debugging.md) to convert this g-code file