docs: Note that FORCE_MOVE can lead to "No next step" errors in G-Codes.md

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

docs/G-Codes.md

@@ -488,13 +488,15 @@ section is enabled:
   the given distance (in mm) at the given constant velocity (in
   mm/s). If ACCEL is specified and is greater than zero, then the
   given acceleration (in mm/s^2) will be used; otherwise no
-  acceleration is performed. No boundary checks are performed; no
+  acceleration is performed. If acceleration is not performed then it
-  kinematic updates are made; other parallel steppers on an axis will
+  can lead to the micro-controller reporting "No next step" errors
-  not be moved. Use caution as an incorrect command could cause
+  (avoid these errors by specifying an ACCEL value or use a very low
-  damage! Using this command will almost certainly place the low-level
+  VELOCITY). No boundary checks are performed; no kinematic updates
-  kinematics in an incorrect state; issue a G28 afterwards to reset
+  are made; other parallel steppers on an axis will not be moved. Use
-  the kinematics. This command is intended for low-level diagnostics
+  caution as an incorrect command could cause damage! Using this
-  and debugging.
+  command will almost certainly place the low-level kinematics in an
+  incorrect state; issue a G28 afterwards to reset the kinematics.
+  This command is intended for low-level diagnostics and debugging.
 - `SET_KINEMATIC_POSITION [X=<value>] [Y=<value>] [Z=<value>]`: Force
   the low-level kinematic code to believe the toolhead is at the given
   cartesian position. This is a diagnostic and debugging command; use