diff --git a/Marlin/src/HAL/HAL_DUE/fastio_Due.h b/Marlin/src/HAL/HAL_DUE/fastio_Due.h
index d60441b641..e1d3fc7563 100644
--- a/Marlin/src/HAL/HAL_DUE/fastio_Due.h
+++ b/Marlin/src/HAL/HAL_DUE/fastio_Due.h
@@ -100,7 +100,7 @@
 /// check if pin is an output
 #define _GET_OUTPUT(IO)
 
-/// check if pin is an timer
+/// check if pin is a timer
 #define _GET_TIMER(IO)
 
 /// Read a pin wrapper
@@ -124,7 +124,7 @@
 /// check if pin is an output wrapper
 #define GET_OUTPUT(IO)  _GET_OUTPUT(IO)
 
-/// check if pin is an timer wrapper
+/// check if pin is a timer (wrapper)
 #define GET_TIMER(IO)  _GET_TIMER(IO)
 
 // Shorthand
diff --git a/Marlin/src/HAL/HAL_LPC1768/fastio.h b/Marlin/src/HAL/HAL_LPC1768/fastio.h
index 221ecdbce4..e19500141f 100644
--- a/Marlin/src/HAL/HAL_LPC1768/fastio.h
+++ b/Marlin/src/HAL/HAL_LPC1768/fastio.h
@@ -102,7 +102,7 @@ bool useable_hardware_PWM(pin_t pin);
 // hg42: we cannot use USEABLE_HARDWARE_PWM because it uses a function that cannot be used statically
 // hg42: instead use PWM bit from the #define
 
-/// check if pin is an timer
+/// check if pin is a timer
 #define _GET_TIMER(IO)        TRUE  // could be LPC1768_PIN_PWM(IO), but there
 // hg42: could be this:
 // #define _GET_TIMER(IO)        LPC1768_PIN_PWM(IO)
@@ -132,7 +132,7 @@ bool useable_hardware_PWM(pin_t pin);
 /// check if pin is an output wrapper
 #define GET_OUTPUT(IO)  _GET_OUTPUT(IO)
 
-/// check if pin is an timer wrapper
+/// check if pin is a timer (wrapper)
 #define GET_TIMER(IO)  _GET_TIMER(IO)
 
 // Shorthand
diff --git a/Marlin/src/HAL/HAL_STM32F7/TMC2660.h b/Marlin/src/HAL/HAL_STM32F7/TMC2660.h
index 9b0f50e402..4c8f2bf731 100644
--- a/Marlin/src/HAL/HAL_STM32F7/TMC2660.h
+++ b/Marlin/src/HAL/HAL_STM32F7/TMC2660.h
@@ -205,12 +205,12 @@ class TMC26XStepper {
      * The more regurlarly you call this function the better. In both senses of 'regularly': Calling it as often as
      * possible is not a bad idea and if you even manage that the intervals you call this function are not too irregular helps too.
      *
-     * You can call this routine even if you know that the motor is not miving. It introduces just a very small penalty in your code.
+     * You can call this routine even if you know that the motor is not moving. It introduces just a very small penalty in your code.
      * You must not call isMoving() to determine if you need to call this function, since taht is done internally already and only
      * slows down you code.
      *
-     * How often you call this function directly influences your top miving speed for the motor. It may be a good idea to call this
-     * from an timer overflow interrupt to ensure proper calling.
+     * How often you call this function directly influences your top moving speed for the motor. It may be a good idea to call this
+     * from a timer overflow interrupt to ensure proper calling.
      * \sa step()
      */
     char move(void);