docs: Minor updates to SmartEffector docs

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

1 files changed, 9 insertions, 7 deletions

diff --git a/docs/Config_Reference.md b/docs/Config_Reference.md
index f297dbdc..cc44f0ad 100644
--- a/docs/Config_Reference.md
+++ b/docs/Config_Reference.md
@@ -1747,10 +1747,12 @@ control_pin:
 ```
 
 ### [smart_effector]
-Smart Effector. One may define this section instead of `[probe]` to enable
-the SmartEffector-specific features. This also enables
-[runtime commands](G-Codes.md#smart-effector) to adjust the parameters of
-the Smart Effector at run time.
+
+The "Smart Effector" from Duet3d implements a Z probe using a force
+sensor. One may define this section instead of `[probe]` to enable the
+Smart Effector specific features. This also enables
+[runtime commands](G-Codes.md#smart_effector) to adjust the parameters
+of the Smart Effector at run time.
 
 ```
 [smart_effector]
@@ -1762,16 +1764,16 @@ pin:
 #   value pullup resistor on the Z probe input, which will likely result in an
 #   always-triggered probe state. In this case, connect the Smart Effector to
 #   a different pin on the board. This parameter is required.
-# control_pin:
+#control_pin:
 #   Pin connected to the Smart Effector control input pin (pin 7). If provided,
 #   Smart Effector sensitivity programming commands become available.
-# probe_accel:
+#probe_accel:
 #   If set, limits the acceleration of the probing moves (in mm/sec^2).
 #   A sudden large acceleration at the beginning of the probing move may
 #   cause spurious probe triggering, especially if the hotend is heavy.
 #   To prevent that, it may be necessary to reduce the acceleration of
 #   the probing moves via this parameter.
-# recovery_time: 0.4
+#recovery_time: 0.4
 #   A delay between the travel moves and the probing moves in seconds. A fast
 #   travel move prior to probing may result in a spurious probe triggering.
 #   This may cause 'Probe triggered prior to movement' errors if no delay