summaryrefslogtreecommitdiff
path: root/keyboards/bastardkb/tbk/keymaps/xyverz
diff options
context:
space:
mode:
authorJoel Challis <git@zvecr.com>2022-10-01 17:47:12 +0100
committerGitHub <noreply@github.com>2022-10-01 17:47:12 +0100
commite068f7a8d1ff3a849011cf090ce63ad1fe063e7b (patch)
treed9b2e3b26d0409414042980e1ae3c5109d03bf54 /keyboards/bastardkb/tbk/keymaps/xyverz
parent818ef07c248933e895a3ea1a7521dda32d1caeb8 (diff)
RESET -> QK_BOOT user keymaps (#18560)
Diffstat (limited to 'keyboards/bastardkb/tbk/keymaps/xyverz')
-rw-r--r--keyboards/bastardkb/tbk/keymaps/xyverz/readme.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/keyboards/bastardkb/tbk/keymaps/xyverz/readme.md b/keyboards/bastardkb/tbk/keymaps/xyverz/readme.md
index 9359e6ad9c..b806bd265a 100644
--- a/keyboards/bastardkb/tbk/keymaps/xyverz/readme.md
+++ b/keyboards/bastardkb/tbk/keymaps/xyverz/readme.md
@@ -17,6 +17,6 @@ See the [keyboard build instructions](https://docs.bastardkb.com)
## Important information regarding the reset
-If you modify this firmware, make sure to always have a RESET key that can be triggered using only the master side ! This way you ensure that you can always flash the keyboard, even if you mess up.
+If you modify this firmware, make sure to always have a `QK_BOOT` key that can be triggered using only the master side ! This way you ensure that you can always flash the keyboard, even if you mess up.
Otherwise if you're stuck, open the case and reset manually by shorting Gnd and Rst, or pressing the RST button.