diff options
| author | skullY <skullydazed@gmail.com> | 2017-08-07 05:57:57 +0200 |
|---|---|---|
| committer | Jack Humbert <jack.humb@gmail.com> | 2017-08-16 21:47:20 +0200 |
| commit | 9d1a08e38ac9937cff4e61abfd0acc26ad5fdf4a (patch) | |
| tree | 352da3e60b219405be323306bcd67a6729107d61 /docs/keymap.md | |
| parent | 9b879b1267cd5cbebf4d73595c7ca4ed52fe5ef4 (diff) | |
| download | qmk_firmware-9d1a08e38ac9937cff4e61abfd0acc26ad5fdf4a.tar.gz qmk_firmware-9d1a08e38ac9937cff4e61abfd0acc26ad5fdf4a.tar.xz | |
Doc updates from going through every file
Diffstat (limited to 'docs/keymap.md')
| -rw-r--r-- | docs/keymap.md | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/docs/keymap.md b/docs/keymap.md index 53b17f401..170fdaed7 100644 --- a/docs/keymap.md +++ b/docs/keymap.md @@ -215,8 +215,7 @@ To actually handle the keypress event we define an `action_function()`. This fun This should have given you a basic overview for creating your own keymap. For more details see the following resources: -* https://github.com/qmk/qmk_firmware/wiki/Keycodes -* https://github.com/qmk/qmk_firmware/wiki/FAQ-Keymap -* https://github.com/qmk/qmk_firmware/wiki/Keymap-examples +* [Keycodes](keycodes.md) +* [Keymap FAQ](faq_keymap.md) -We are actively working to improve these docs. If you have suggestions for how they could be made better please [file an issue](https://github.com/qmk/qmk_firmware/issues/new)!
\ No newline at end of file +We are actively working to improve these docs. If you have suggestions for how they could be made better please [file an issue](https://github.com/qmk/qmk_firmware/issues/new)! |