kofal.net/zmk
1
0
Fork 1
mirror of https://github.com/zmkfirmware/zmk.git synced 2026-03-22 05:55:18 -05:00
Code Issues Packages Projects Releases Wiki Activity

refactor(docs): Use new admonition title syntax and disable mdx v1 compat

Browse Source
This commit is contained in:
Cem Aksoylar
2024-01-12 20:34:12 -08:00
parent ee855de349
commit dcfe07d9f6
13 changed files with 26 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docs/features/bluetooth.md
View File

@@ -22,7 +22,7 @@ The only known vulnerability in the protocol is a risk of an active man-in-the-m
By default, ZMK supports five "profiles" for selecting which bonded host
device should receive the keyboard input.
:::note Connection Management
:::note[Connection Management]
When pairing to a host device ZMK saves bond information to the selected profile. It will not replace this automatically when you initiate pairing with another device. To pair with a new device select an unused profile with or clearing the current profile, using the [`&bt` behavior](../behaviors/bluetooth.md) on your keyboard.

2
docs/docs/features/combos.md
View File

@@ -44,7 +44,7 @@ Key positions are numbered like the keys in your keymap, starting at 0. So, if t
- Fully overlapping combos like `0 1` and `0 1 2` are supported.
- You are not limited to `&kp` bindings. You can use all ZMK behaviors there, like `&mo`, `&bt`, `&mt`, `&lt` etc.
:::note Source-specific behaviors on split keyboards
:::note[Source-specific behaviors on split keyboards]
Invoking a source-specific behavior such as one of the [reset behaviors](behaviors/reset.md) using a combo will always trigger it on the central side of the keyboard, regardless of the side that the keys corresponding to `key-positions` are on.
:::