diff options
| author |  Devin J. Pohly <djpohly+github@gmail.com> | 2017-11-30 12:18:01 -0600 |
|---|---|---|
| committer |  skullydazed <skullydazed@users.noreply.github.com> | 2017-11-30 10:18:01 -0800 |
| commit | 7aaef1626693f4e4449946de025aa6175adcfa3d (patch) | |
| tree | eb9c2b5f38515ddfda61e7dd036e5535692969b8 /docs/contributing.md | |
| parent | 28874a9f33e7527f5104ec507f78360481f51f9e (diff) | |
| download | qmk_firmware-7aaef1626693f4e4449946de025aa6175adcfa3d.tar.gz | |
Fix internal links in docs/ (#2080)
One link in the summary (Modding your keyboard) referred to a page that
was deleted; the rest have been updated to point to the new names.
Diffstat (limited to 'docs/contributing.md')
| -rw-r--r-- | docs/contributing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/contributing.md b/docs/contributing.md index 6a3f34e4c..c9dca9d08 100644 --- a/docs/contributing.md +++ b/docs/contributing.md @@ -122,7 +122,7 @@ We also ask that you follow these guidelines: ## Quantum/TMK Core -Before you put a lot of work into building your new feature you should make sure you are implementing it in the best way. You can get a basic understanding of QMK by reading [Understaning QMK](understanding_qmk.html), which will take you on a tour of the QMK program flow. From here you should talk to us to get a sense of the best way to implement your idea. There are two main ways to do this: +Before you put a lot of work into building your new feature you should make sure you are implementing it in the best way. You can get a basic understanding of QMK by reading [Understaning QMK](understanding_qmk.md), which will take you on a tour of the QMK program flow. From here you should talk to us to get a sense of the best way to implement your idea. There are two main ways to do this: * [Chat on Gitter](https://gitter.im/qmk/qmk_firmware) * [Open an Issue](https://github.com/qmk/qmk_firmware/issues/new) |