summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMamoor Jaan Khan <56243233+LowNightSnack@users.noreply.github.com>2020-09-11 23:48:53 +0530
committerGitHub <noreply@github.com>2020-09-11 23:48:53 +0530
commitce8ade4afaa4cc9fc2b94050e98680301e539e56 (patch)
tree928030bd446ff2c71531cd86b8e6ce6037a65940
parent223a19cb0472d453fbe734b37a8ac59a82f61c67 (diff)
A bad commit
-rw-r--r--docs/docs/behavior/hold-tap.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/docs/behavior/hold-tap.md b/docs/docs/behavior/hold-tap.md
index ab51022..d51edd3 100644
--- a/docs/docs/behavior/hold-tap.md
+++ b/docs/docs/behavior/hold-tap.md
@@ -59,4 +59,4 @@ If this config does not work for you, try the flavor "tap-preferred" and a short
If you want to use a tap-hold with a keycode from a different code page, you have to define another behavior with another "bindings" parameter.For example, if you want to use SHIFT and volume up, define the bindings like `bindings = <&kp>, <&cp>;`. Only single-argument behaviors are supported at the moment.
#### Note
-Astute readers may notice similarities between the possible behaviors in ZMK and other firmware, such as QMK. The hold-preferred flavor works similar to the `HOLD_ON_OTHER_KEY_PRESS` setting. The 'balanced' flavor is similar to the `PERMISSIVE_HOLD` setting, and the `tap-preferred` flavor is similar to `IGNORE_MOD_TAP_INTERRUPT`.
+Astute readers may notice similarities between the possible behaviors in ZMK and other firmware, such as QMK. The hold-preferred flavor works similar to the `HOLD_ON_OTHER_KEY_PRESS` setting. The 'balanced' flavor is similar to the `PERMISSIVE_HOLD` setting, and the `tap-preferred` flavor is similar to `IGNORE_MOD_TAP_INTERRUPT`