aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorskullydazed <skullydazed@users.noreply.github.com>2017-04-04 22:35:21 -0700
committerskullydazed <skullydazed@users.noreply.github.com>2017-04-04 22:35:21 -0700
commit1ca879687c4ca672ee7e2924526068052e16df90 (patch)
treeb736d6e1b99c4c4e2f7b6d2bf437b7331a7962d0
parent32e55f918238adcd1ab026718bd9eda089518e9e (diff)
downloadfirmware-1ca879687c4ca672ee7e2924526068052e16df90.tar.gz
firmware-1ca879687c4ca672ee7e2924526068052e16df90.tar.bz2
firmware-1ca879687c4ca672ee7e2924526068052e16df90.zip
Updated Custom Quantum Functions (markdown)
-rw-r--r--Custom-Quantum-Functions.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Custom-Quantum-Functions.md b/Custom-Quantum-Functions.md
index 26398563e..fe973c21c 100644
--- a/Custom-Quantum-Functions.md
+++ b/Custom-Quantum-Functions.md
@@ -10,7 +10,7 @@ We have structured QMK as a hierarchy:
Each of the functions described below can be defined with a `_kb()` suffix or an `_user()` suffix. We intend for you to use the `_kb()` suffix at the Keyboard/Revision level, while the `_user()` suffix should be used at the Keymap level.
-When defining functions at the Keyboard/Revision level it is important that your `_kb()` implementation call `*_user()` before executing anything else- otherwise the keymap level function will never be called.
+When defining functions at the Keyboard/Revision level it is important that your `_kb()` implementation call `_user()` before executing anything else- otherwise the keymap level function will never be called.
## Matrix Initialization Code