From 82504a6265fba6489afebe3af319b0997b12d323 Mon Sep 17 00:00:00 2001 From: jding Date: Fri, 29 Oct 2021 20:40:38 +0000 Subject: [PATCH] fix docs --- docs/docs/behaviors/hold-tap.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/docs/docs/behaviors/hold-tap.md b/docs/docs/behaviors/hold-tap.md index 5faf41bb..8e1443c6 100644 --- a/docs/docs/behaviors/hold-tap.md +++ b/docs/docs/behaviors/hold-tap.md @@ -99,13 +99,8 @@ If this config does not work for you, try the flavor "balanced" with a medium `t * Including `hold-trigger-key-postions` in your hold-tap behavior definition enables the positional hold-tap feature. * With positional hold-tap enabled, your hold-tap behavior will only produce a hold behavior if, while the hold-tap key is still held down, the next key to be pressed is at one of the positions listed in the `hold-trigger-key-postions` array. -* `hold-trigger-key-postions` is an array of key positions. See the info section below about how to figure out the positions of keys on your board. -:::info - -Key positions are numbered according to the keys in your keymap, starting at 0. So, if the first key in your keymap is Q, this key is in position 0. The next key (possibly W) will have position 1, et cetera. - -::: -* See the following example, which references the below hold-tap behavior definiton: +* `hold-trigger-key-postions` is an array of key positions indexes. Key positions are numbered / indexed according to the keys in your keymap, starting at 0. So, if the first key in your keymap is Q, this key is in position 0. The next key (possibly W) will have position 1, et cetera. +* See the following example, which references the below hold-tap behavior definition: ``` #include