aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorBenny Powers <bennypowers@users.noreply.github.com>2017-08-18 10:45:36 +0300
committerJack Humbert <jack.humb@gmail.com>2017-08-18 12:49:55 -0400
commit9fed4f79489959045dd30f02c3113aec3808d92c (patch)
treedf1acbf42c79fb2656f694a06f6b9d2a05308da4 /docs
parentc0a6935fb3748baea0c3c6d3fdbf07cc1f5e5609 (diff)
downloadfirmware-9fed4f79489959045dd30f02c3113aec3808d92c.tar.gz
firmware-9fed4f79489959045dd30f02c3113aec3808d92c.tar.bz2
firmware-9fed4f79489959045dd30f02c3113aec3808d92c.zip
Add link to keycodes doc in how_keyboards_work
Diffstat (limited to 'docs')
-rw-r--r--docs/how_keyboards_work.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/how_keyboards_work.md b/docs/how_keyboards_work.md
index 3969c5680..edd219a32 100644
--- a/docs/how_keyboards_work.md
+++ b/docs/how_keyboards_work.md
@@ -51,7 +51,7 @@ layout is set to QWERTY, a sample of the matching table is as follow:
## Back to the firmware
-As the layout is generally fixed (unless you create your own), the firmware can actually call a keycode by its layout name directly to ease things for you. This is exactly what is done here with `KC_A` actually representing `0x04` in QWERTY. The full list can be found in `keycode.txt`.
+As the layout is generally fixed (unless you create your own), the firmware can actually call a keycode by its layout name directly to ease things for you. This is exactly what is done here with `KC_A` actually representing `0x04` in QWERTY. The full list can be found in [keycodes](keycodes.md).
## List of Characters You Can Send