X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=docs%2Fhow_keyboards_work.md;h=fac2b5a489d88b650e80cf3056e0f46f6543241d;hb=ade22f8e2c272044ea2f80ff6fe5ca9576858939;hp=edd219a32390fb6798d2d8a47ae82484b349833e;hpb=81d7e7d4c8b99e032ce9423da56dba46f8bce18f;p=qmk_firmware.git

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 @@
-# How keys are registered, and interpreted by computers
+# How Keys Are Registered, and Interpreted by Computers
 
 In this file, you can will learn the concepts of how keyboards work over USB,
 and you'll be able to better understand what you can expect from changing your
 firmware directly.
 
-## Schematic view
+## Schematic View
 
 Whenever you type on 1 particular key, here is the chain of actions taking
 place:
@@ -49,7 +49,7 @@ layout is set to QWERTY, a sample of the matching table is as follow:
 | 0x1D | z/Z |
 | ... | ... |
 
-## Back to the firmware
+## 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 [keycodes](keycodes.md).