summaryrefslogtreecommitdiff
path: root/docs/feature_key_lock.md
diff options
context:
space:
mode:
authorJoel Challis <git@zvecr.com>2022-10-24 23:29:23 +0100
committerGitHub <noreply@github.com>2022-10-24 23:29:23 +0100
commit67fd4e6b7afe5515b67f153723f57beabbebe25e (patch)
treee384be6bb0459af427ce6fef7eff73314a8d2cbf /docs/feature_key_lock.md
parent40aa9c87456b8677c10c241ec13ef9de0a84b64f (diff)
[DOCS] Use correct OSM arguments (#18835)
Diffstat (limited to 'docs/feature_key_lock.md')
-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 7681394229..1b02c7c291 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](one_shot_keys.md) 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](one_shot_keys.md) keys (for example, if you have your Shift defined as `OSM(MOD_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. The Key Lock can be cancelled by calling the `cancel_key_lock()` function.