summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHugo Gayosso <tribrhy@gmail.com>2017-12-20 11:33:34 -0500
committerJack Humbert <jack.humb@gmail.com>2017-12-20 14:38:24 -0500
commitd8f0faabdad2e2bc80d2258bda80e6b9e9918b63 (patch)
tree46a21331cfaf853562d070228ca2ff519062ded3
parent818042b2c3820f4ca5ae25d5de82851ca8405f06 (diff)
Fixed typo
-rw-r--r--docs/custom_quantum_functions.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/custom_quantum_functions.md b/docs/custom_quantum_functions.md
index 3df1d73a28..e7a45e0bfd 100644
--- a/docs/custom_quantum_functions.md
+++ b/docs/custom_quantum_functions.md
@@ -36,7 +36,7 @@ enum my_keycodes {
## Programming the Behavior of Any Keycode
-When you want to override the behavior of an existing key, or define the behavior for a new key, you should use the `process_record_kb()` and `process_record_user()` functions. These are called by QMK during key processing before the actual key event is handled. If these functions return `true` QMK will process the keycodes as usual. That can be handy for extending the functionality of a key rather than replacing it. If these functions return `false` QMK will skip the normal key handling, and it will be up you to send any key up or down events that are required.
+When you want to override the behavior of an existing key, or define the behavior for a new key, you should use the `process_record_kb()` and `process_record_user()` functions. These are called by QMK during key processing before the actual key event is handled. If these functions return `true` QMK will process the keycodes as usual. That can be handy for extending the functionality of a key rather than replacing it. If these functions return `false` QMK will skip the normal key handling, and it will be up to you to send any key up or down events that are required.
These function are called every time a key is pressed or released.