diff options
| author | fauxpark <fauxpark@gmail.com> | 2017-12-09 16:36:32 +1100 |
|---|---|---|
| committer | Jack Humbert <jack.humb@gmail.com> | 2017-12-09 10:46:11 -0500 |
| commit | 7b0356d1d49da6574570e110f61f95692afdb3d0 (patch) | |
| tree | a3e70802085ea8089f1e7851529f0296247fa264 /docs/how_keyboards_work.md | |
| parent | 6eb89ae906db7f226570e1839b88dcdd3a8fa962 (diff) | |
| download | qmk_firmware-7b0356d1d49da6574570e110f61f95692afdb3d0.tar.gz qmk_firmware-7b0356d1d49da6574570e110f61f95692afdb3d0.zip | |
Convert all headings to Title Case
Diffstat (limited to 'docs/how_keyboards_work.md')
| -rw-r--r-- | docs/how_keyboards_work.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/how_keyboards_work.md b/docs/how_keyboards_work.md index edd219a32..fac2b5a48 100644 --- a/docs/how_keyboards_work.md +++ b/docs/how_keyboards_work.md | |||
| @@ -1,10 +1,10 @@ | |||
| 1 | # How keys are registered, and interpreted by computers | 1 | # How Keys Are Registered, and Interpreted by Computers |
| 2 | 2 | ||
| 3 | In this file, you can will learn the concepts of how keyboards work over USB, | 3 | In this file, you can will learn the concepts of how keyboards work over USB, |
| 4 | and you'll be able to better understand what you can expect from changing your | 4 | and you'll be able to better understand what you can expect from changing your |
| 5 | firmware directly. | 5 | firmware directly. |
| 6 | 6 | ||
| 7 | ## Schematic view | 7 | ## Schematic View |
| 8 | 8 | ||
| 9 | Whenever you type on 1 particular key, here is the chain of actions taking | 9 | Whenever you type on 1 particular key, here is the chain of actions taking |
| 10 | place: | 10 | place: |
| @@ -49,7 +49,7 @@ layout is set to QWERTY, a sample of the matching table is as follow: | |||
| 49 | | 0x1D | z/Z | | 49 | | 0x1D | z/Z | |
| 50 | | ... | ... | | 50 | | ... | ... | |
| 51 | 51 | ||
| 52 | ## Back to the firmware | 52 | ## Back to the Firmware |
| 53 | 53 | ||
| 54 | 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). | 54 | 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). |
| 55 | 55 | ||