summaryrefslogtreecommitdiffstats
path: root/Custom-Quantum-Functions.md
diff options
context:
space:
mode:
authorskullydazed <skullydazed@users.noreply.github.com>2017-04-04 22:33:36 -0700
committerskullydazed <skullydazed@users.noreply.github.com>2017-04-04 22:33:36 -0700
commit32e55f918238adcd1ab026718bd9eda089518e9e (patch)
treec36a988c80669c07eda6b5485798bbc46206f1bf /Custom-Quantum-Functions.md
parent34836a16ed44b8e70738178602e0475f665242a8 (diff)
Updated Custom Quantum Functions (markdown)
Diffstat (limited to 'Custom-Quantum-Functions.md')
-rw-r--r--Custom-Quantum-Functions.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/Custom-Quantum-Functions.md b/Custom-Quantum-Functions.md
index c4bf418e8a..26398563e3 100644
--- a/Custom-Quantum-Functions.md
+++ b/Custom-Quantum-Functions.md
@@ -19,7 +19,7 @@ When defining functions at the Keyboard/Revision level it is important that your
This function gets called when the matrix is initiated. You should use this function to initialize any custom hardware you may have, such as speakers, LED drivers, or other features which need to be setup after the keyboard powers on.
-#### Example
+### Example
```
void matrix_init_kb(void) {
@@ -90,7 +90,7 @@ This allows you to control the 5 LED's defined as part of the USB Keyboard spec.
* `USB_LED_COMPOSE`
* `USB_LED_KANA`
-#### Example:
+### Example:
```
void led_set_kb(uint8_t usb_led) {