[Docs] Explain Tap Dance interruption (#5520)

diff --git a/docs/feature_tap_dance.md b/docs/feature_tap_dance.md
index 7427a77146b5ef9f75a4250f705c580dde6f1336..f48f11b1cb1a291fd7cd507facb43bf91081b16e 100644 (file)
--- a/docs/feature_tap_dance.md
+++ b/docs/feature_tap_dance.md
@@ -333,6 +333,8 @@ And then simply use `TD(X_CTL)` anywhere in your keymap.
 
 If you want to implement this in your userspace, then you may want to check out how [DanielGGordon](https://github.com/qmk/qmk_firmware/tree/master/users/gordon) has implemented this in their userspace.
 
+> In this configuration "hold" takes place **after** tap dance timeout (see `ACTION_TAP_DANCE_FN_ADVANCED_TIME`). To achieve instant hold, remove `state->interrupted` checks in conditions. As a result you may use comfortable longer tapping periods to have more time for taps and not to wait too long for holds (try starting with doubled `TAPPING_TERM`).
+
 ### Example 5: Using tap dance for advanced mod-tap and layer-tap keys
 
 Tap dance can be used to emulate `MT()` and `LT()` behavior when the tapped code is not a basic keycode. This is useful to send tapped keycodes that normally require `Shift`, such as parentheses or curly braces—or other modified keycodes, such as `Control + X`.