summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorEvan Callicoat <apsu@propter.net>2021-12-26 13:21:58 -0600
committerNick Winans <nick@winans.codes>2021-12-26 13:44:46 -0600
commit62e3b573b920b17f3f00781dde53d965dbe8a613 (patch)
treebe555c18f611cdb3cc9dab45cd889d17152eda9c /docs
parent2666bd622cde5f55366636a8fe24ca104633be85 (diff)
Typos
Diffstat (limited to 'docs')
-rw-r--r--docs/docs/behaviors/hold-tap.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/docs/behaviors/hold-tap.md b/docs/docs/behaviors/hold-tap.md
index 972df0b..8e35f75 100644
--- a/docs/docs/behaviors/hold-tap.md
+++ b/docs/docs/behaviors/hold-tap.md
@@ -62,12 +62,12 @@ For example, if you press `&mt LEFT_SHIFT A` and then release it without pressin
#### Positional hold-tap and `hold-trigger-key-positions`
-- Including `hold-trigger-key-postions` in your hold-tap definition turns on the positional hold-tap feature.
+- Including `hold-trigger-key-positions` in your hold-tap definition turns on the positional hold-tap feature.
- With positional hold-tap enabled, if you press any key **NOT** listed in `hold-trigger-key-positions` before `tapping-term-ms` expires, it will produce a tap.
- In all other situations, positional hold-tap will not modify the behavior of your hold-tap.
- Positional hold-tap is useful with home-row modifiers. If you have a home-row modifier key in the left hand for example, by including only keys positions from the right hand in `hold-trigger-key-positions`, you will only get hold behaviors during cross-hand key combinations.
-- Note that `hold-trigger-key-postions` is an array of key position indexes. Key positions are numbered according to your keymap, starting with 0. So if the first key in your keymap is Q, this key is in position 0. The next key (probably W) will be in position 1, et cetera.
-- See the following example, which uses a hold-tap behavior definition, configured with the `hold-preferrred` flavor, and with positional hold-tap enabled:
+- Note that `hold-trigger-key-positions` is an array of key position indexes. Key positions are numbered according to your keymap, starting with 0. So if the first key in your keymap is Q, this key is in position 0. The next key (probably W) will be in position 1, et cetera.
+- See the following example, which uses a hold-tap behavior definition, configured with the `hold-preferred` flavor, and with positional hold-tap enabled:
```
#include <dt-bindings/zmk/keys.h>