aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authormakenova <makenova@users.noreply.github.com>2019-10-13 19:26:03 -0500
committerJoel Challis <git@zvecr.com>2019-10-14 01:26:03 +0100
commit6560dffc05131c05655f8e0d74cc65c5918894fa (patch)
treec53be034d0397b38c786bd9c4e7cbfcc9ba4b4bb
parente796d7b49ebe8d0398853abb0d2dfa86396aa630 (diff)
downloadfirmware-6560dffc05131c05655f8e0d74cc65c5918894fa.tar.gz
firmware-6560dffc05131c05655f8e0d74cc65c5918894fa.tar.bz2
firmware-6560dffc05131c05655f8e0d74cc65c5918894fa.zip
update one shot keys link (#7020)
-rw-r--r--docs/feature_key_lock.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_key_lock.md b/docs/feature_key_lock.md
index 718d9c5bd..46935adda 100644
--- a/docs/feature_key_lock.md
+++ b/docs/feature_key_lock.md
@@ -16,7 +16,7 @@ First, enable Key Lock by setting `KEY_LOCK_ENABLE = yes` in your `rules.mk`. Th
## Caveats
-Key Lock is only able to hold standard action keys and [One Shot modifier](quantum_keycodes.md#one-shot-keys) keys (for example, if you have your Shift defined as `OSM(KC_LSFT)`).
+Key Lock is only able to hold standard action keys and [One Shot modifier](feature_advanced_keycodes.md#one-shot-keys) keys (for example, if you have your Shift defined as `OSM(KC_LSFT)`).
This does not include any of the QMK special functions (except One Shot modifiers), or shifted versions of keys such as `KC_LPRN`. If it's in the [Basic Keycodes](keycodes_basic.md) list, it can be held.
Switching layers will not cancel the Key Lock.