summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael van Eerd <michael@cache.works>2021-08-15 22:54:31 +0200
committerPete Johanson <peter@peterjohanson.com>2021-09-17 10:45:37 -0400
commit50174af658872b8bd317bb00b0c18b140e1ccbaa (patch)
treebc41b407e4fbe2a1410c0537e8d7a1cd756d1c3f
parentc27c1048e4486e5dd046d8d98a4278f0d77d2937 (diff)
fix(docs) add `BT_PRV` as suggested
Co-authored-by: Cem Aksoylar <caksoylar@users.noreply.github.com>
-rw-r--r--docs/docs/behaviors/bluetooth.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/docs/behaviors/bluetooth.md b/docs/docs/behaviors/bluetooth.md
index d4690f9..df264ce 100644
--- a/docs/docs/behaviors/bluetooth.md
+++ b/docs/docs/behaviors/bluetooth.md
@@ -10,7 +10,7 @@ between the keyboard and the host. By default, ZMK supports five "profiles" for
computer/laptop/keyboard should receive the keyboard input; many of the commands here operate on those profiles.
:::note Connection Management
-When pairing to a host device ZMK saves bond information to the selected profile. It will not replace this when you initiate pairing with another device. To pair with a new device select an unused profile with `BT_SEL`, `BT_NXT` or by clearing an existing profile using `BT_CLR`.
+When pairing to a host device ZMK saves bond information to the selected profile. It will not replace this when you initiate pairing with another device. To pair with a new device select an unused profile with `BT_SEL`, `BT_NXT` or `BT_PRV` bindings, or by clearing an existing profile using `BT_CLR`.
A ZMK device may show as "connected" on multiple hosts at the same time. This is working as intended, and only the host associated with the active profile will receive keystrokes.
:::