bb53635f33c213e5a940edea8b07026ef89aed42
- Author
- fauxpark <fauxpark@gmail.com>
- Committer
- Jack Humbert <jack.humb@gmail.com>
- Date
Message
Trim trailing whitespace
Diff
This diff is truncated to protect this page.
1diff --git a/docs/contributing.md b/docs/contributing.md
2index a1534d9681ee47cbf9f45d3ab2ed40077da82fc5..0e8066f0053738c1e977b8ca2d2050c29dab5d1f 100644
3--- a/docs/contributing.md
4+++ b/docs/contributing.md
5@@ -75,7 +75,7 @@ Most of our style is pretty easy to pick up on, but right now it's not entirely
6
7 We have a few different types of changes in QMK, each requiring a different level of rigor. We'd like you to keep the following guidelines in mind no matter what type of change you're making.
8
9-* Separate PR's into logical units. For example, do not submit one PR covering two separate features, instead submit a separate PR for each feature.
10+* Separate PR's into logical units. For example, do not submit one PR covering two separate features, instead submit a separate PR for each feature.
11 * Check for unnecessary whitespace with `git diff --check` before committing.
12 * Make sure your code change actually compiles.
13 * Keymaps: Make sure that `make keyboard:your_new_keymap` does not return an error
14@@ -111,7 +111,7 @@ Most first-time QMK contributors start with their personal keymaps. We try to ke
15
16diff --git a/docs/custom_quantum_functions.md b/docs/custom_quantum_functions.md
17index 16faf9732a7fb161245f06cf2ebb12c9b2f03d2d..928dccc9c349717a120e4a534ceeefee77bb4c06 100644
18--- a/docs/custom_quantum_functions.md
19+++ b/docs/custom_quantum_functions.md
20@@ -1,6 +1,6 @@
21 # How to Customize Your Keyboard's Behavior
22
23diff --git a/docs/faq_build.md b/docs/faq_build.md
24index 0474e27465806db083f9741c0026270222625f9b..d38ca69d0d857ab79f55651eeffc2db94233a286 100644
25--- a/docs/faq_build.md
26+++ b/docs/faq_build.md
27@@ -6,7 +6,7 @@ This page covers questions about building QMK. If you have not yet you should re
28 You will need proper permission to operate a device. For Linux users see udev rules below. Easy way is to use `sudo` command, if you are not familiar with this command check its manual with `man sudo` or this page on line.
29
30 In short when your controller is ATMega32u4,
31-
32+
33 $ sudo dfu-programmer atmega32u4 erase --force
34 $ sudo dfu-programmer atmega32u4 flash your.hex
35 $ sudo dfu-programmer atmega32u4 reset
36@@ -81,11 +81,11 @@ make: *** [obj_alps64/protocol/lufa/lufa.o] Error 1
37 Note that Teensy2.0++ bootloader size is 2048byte. Some Makefiles may have wrong comment.
38
39 ```
40-# Boot Section Size in *bytes*
41-# Teensy halfKay 512
42-# Teensy++ halfKay 2048
43+# Boot Section Size in *bytes*
44+# Teensy halfKay 512
45+# Teensy++ halfKay 2048
46 # Atmel DFU loader 4096 (TMK Alt Controller)
47-# LUFA bootloader 4096
48-# USBaspLoader 2048
49+# LUFA bootloader 4096
50+# USBaspLoader 2048
51 OPT_DEFS += -DBOOTLOADER_SIZE=2048
52 ```
53diff --git a/docs/faq_debug.md b/docs/faq_debug.md
54index 25226102d776e302a1c3d2e5798ba2d0f883df9c..7c1690d13f800e4950d57b598cdf22d8cddf153d 100644
55--- a/docs/faq_debug.md
56+++ b/docs/faq_debug.md
57@@ -116,12 +116,12 @@ http://deskthority.net/workshop-f7/rebuilding-and-redesigning-a-classic-thinkpad
58 Properly configure bootloader size in **Makefile**. With wrong section size bootloader won't probably start with **Magic command** and **Boot Magic**.
59 ```
60 # Size of Bootloaders in bytes:
61-# Atmel DFU loader(ATmega32U4) 4096
62-# Atmel DFU loader(AT90USB128) 8192
63-# LUFA bootloader(ATmega32U4) 4096
64-# Arduino Caterina(ATmega32U4) 4096
65-# USBaspLoader(ATmega***) 2048
66-# Teensy halfKay(ATmega32U4) 512
67+# Atmel DFU loader(ATmega32U4) 4096
68+# Atmel DFU loader(AT90USB128) 8192
69+# LUFA bootloader(ATmega32U4) 4096
70+# Arduino Caterina(ATmega32U4) 4096
71+# USBaspLoader(ATmega***) 2048
72+# Teensy halfKay(ATmega32U4) 512
73 # Teensy++ halfKay(AT90USB128) 2048
74 OPT_DEFS += -DBOOTLOADER_SIZE=4096
75 ```
76@@ -135,14 +135,14 @@ byte Atmel/LUFA(ATMega32u4) byte Atmel(AT90SUB1286)
77 | | | |
78 | | | |
79 | Application | | Application |
80- | | | |
81+ | | | |
82 = = = =
83 | | 32KB-4KB | | 128KB-8KB
84 0x6000 +---------------+ 0x1E000 +---------------+
85 | Bootloader | 4KB | Bootloader | 8KB
86 0x7FFF +---------------+ 0x1FFFF +---------------+
87
88-
89+
90 byte Teensy(ATMega32u4) byte Teensy++(AT90SUB1286)
91 0x0000 +---------------+ 0x00000 +---------------+
92 | | | |
93@@ -230,7 +230,7 @@ https://geekhack.org/index.php?topic=14290.msg1884034#msg1884034
94 ## Problem on BIOS (UEFI)/Resume (Sleep & Wake)/Power Cycles
95 Some people reported their keyboard stops working on BIOS and/or after resume(power cycles).
96
97-As of now root of its cause is not clear but some build options seem to be related. In Makefile try to disable those options like `CONSOLE_ENABLE`, `NKRO_ENABLE`, `SLEEP_LED_ENABLE` and/or others.
98+As of now root of its cause is not clear but some build options seem to be related. In Makefile try to disable those options like `CONSOLE_ENABLE`, `NKRO_ENABLE`, `SLEEP_LED_ENABLE` and/or others.
99
100 https://github.com/tmk/tmk_keyboard/issues/266
101 https://geekhack.org/index.php?topic=41989.msg1967778#msg1967778
102diff --git a/docs/faq_keymap.md b/docs/faq_keymap.md
103index f0410fcb4de3fffe761ea1a3919ffa63ceb03cfd..7093dec2025ca64f36fcb3c91776d721f0386ade 100644
104--- a/docs/faq_keymap.md
105+++ b/docs/faq_keymap.md
106@@ -48,7 +48,7 @@ For Modifier keys and layer actions you have to place `KC_TRANS` on same positio
107 ## Mechanical Lock Switch Support
108
109 This feature is for *mechanical lock switch* like [this Alps one](http://deskthority.net/wiki/Alps_SKCL_Lock). You can enable it by adding this to your `config.h`:
110-
111+
112 ```
113 #define LOCKING_SUPPORT_ENABLE
114 #define LOCKING_RESYNC_ENABLE
115@@ -187,7 +187,7 @@ ___TO BE IMPROVED___
116 real_mods is intended to retains state of real/physical modifier key state, while
117 weak_mods retains state of virtual or temporary modifiers which should not affect state real modifier key.
118
119-Let's say you hold down physical left shift key and type ACTION_MODS_KEY(LSHIFT, KC_A),
120+Let's say you hold down physical left shift key and type ACTION_MODS_KEY(LSHIFT, KC_A),
121
122 with weak_mods,
123 * (1) hold down left shift: real_mods |= MOD_BIT(LSHIFT)
124diff --git a/docs/feature_advanced_keycodes.md b/docs/feature_advanced_keycodes.md
125index 3ea28ca4e8d3fa0d20ebc6aec4530d745ea3f257..0e22154f624a5a3c732a597f9df263736c267ca6 100644
126--- a/docs/feature_advanced_keycodes.md
127+++ b/docs/feature_advanced_keycodes.md
128@@ -41,7 +41,7 @@ If you are just getting started with QMK you will want to keep everything simple
129
130 ### Intermediate Users
131
132diff --git a/docs/feature_audio.md b/docs/feature_audio.md
133index 774e0ae5a2450dbdb743a5c2eb762d305440bd29..6b991a9afd9ff44970e1b7d64604120585f84531 100644
134--- a/docs/feature_audio.md
135+++ b/docs/feature_audio.md
136@@ -49,7 +49,7 @@ It's advised that you wrap all audio features in `#ifdef AUDIO_ENABLE` / `#endif
137
138 ## Music Mode
139
140diff --git a/docs/feature_dynamic_macros.md b/docs/feature_dynamic_macros.md
141index 23fefea4ce7e5c7406504c9dec073f786ca77acf..9803557e9e7fa51f2f79df68daea93d6b2239c34 100644
142--- a/docs/feature_dynamic_macros.md
143+++ b/docs/feature_dynamic_macros.md
144@@ -52,7 +52,7 @@ For users of the earlier versions of dynamic macros: It is still possible to fin
145
146 ```c
147 uint16_t macro_kc = (keycode == MO(_DYN) ? DYN_REC_STOP : keycode);
148-
149+
150 if (!process_record_dynamic_macro(macro_kc, record)) {
151 return false;
152 }
153diff --git a/docs/feature_layouts.md b/docs/feature_layouts.md
154index fcfe9cd1cf21adba7b5ff5952ef47f7511e124e0..24c42c09feb1867f0cd885adba47035c4217c843 100644
155--- a/docs/feature_layouts.md
156+++ b/docs/feature_layouts.md
157@@ -1,6 +1,6 @@
158 # Layouts: Using a Keymap with Multiple Keyboards
159
160-The `layouts/` folder contains different physical key layouts that can apply to different keyboards.
161+The `layouts/` folder contains different physical key layouts that can apply to different keyboards.
162
163 ```
164 layouts/
165@@ -21,7 +21,7 @@ layouts/
166 | + ...
167 ```
168
169diff --git a/docs/feature_macros.md b/docs/feature_macros.md
170index a9c138e815daf5cbed79afbb5b5734eb2fda75f3..dff692bd8f0cc28ee81d124ac241500668f78050 100644
171--- a/docs/feature_macros.md
172+++ b/docs/feature_macros.md
173@@ -1,6 +1,6 @@
174 # Macros
175
176-Macros allow you to send multiple keystrokes when pressing just one key. QMK has a number of ways to define and use macros. These can do anything you want: type common phrases for you, copypasta, repetitive game movements, or even help you code.
177+Macros allow you to send multiple keystrokes when pressing just one key. QMK has a number of ways to define and use macros. These can do anything you want: type common phrases for you, copypasta, repetitive game movements, or even help you code.
178
179 {% hint style='danger' %}
180diff --git a/docs/feature_ps2_mouse.md b/docs/feature_ps2_mouse.md
181index 51ae5fa2633f98b6050949494c6d75066216d3bf..909406e7d2acac5250ac170f5ebc6bd477c301bd 100644
182--- a/docs/feature_ps2_mouse.md
183+++ b/docs/feature_ps2_mouse.md
184@@ -135,7 +135,7 @@ These enable settings supported by the PS/2 mouse protocol: http://www.computer-
185
186 ```
187 /* Use remote mode instead of the default stream mode (see link) */
188-#define PS2_MOUSE_USE_REMOTE_MODE
189+#define PS2_MOUSE_USE_REMOTE_MODE
190
191 /* Enable the scrollwheel or scroll gesture on your mouse or touchpad */
192 #define PS2_MOUSE_ENABLE_SCROLLING
193diff --git a/docs/feature_tap_dance.md b/docs/feature_tap_dance.md
194index 271d1a0f00101b844c9b53c313a074b6d735d92b..e31e331679d7fd307f30026daafd6fc79171161e 100644
195--- a/docs/feature_tap_dance.md
196+++ b/docs/feature_tap_dance.md
197@@ -187,9 +187,9 @@ enum {
198 SINGLE_TAP = 1,
199 SINGLE_HOLD = 2,
200 DOUBLE_TAP = 3,
201- DOUBLE_HOLD = 4,
202+ DOUBLE_HOLD = 4,
203 DOUBLE_SINGLE_TAP = 5 //send SINGLE_TAP twice - NOT DOUBLE_TAP
204- // Add more enums here if you want for triple, quadruple, etc.
205+ // Add more enums here if you want for triple, quadruple, etc.
206 };
207
208 typedef struct {
209@@ -209,14 +209,14 @@ int cur_dance (qk_tap_dance_state_t *state) {
210 if (state->interrupted) return DOUBLE_SINGLE_TAP;
211 else if (state->pressed) return DOUBLE_HOLD;
212 else return DOUBLE_TAP;
213- }
214+ }
215 else return 6; //magic number. At some point this method will expand to work for more presses
216 }
217
218 //**************** Definitions needed for quad function to work *********************//
219
220 //instanalize an instance of 'tap' for the 'x' tap dance.
221-static tap xtap_state = {
222+static tap xtap_state = {
223 .is_press_action = true,
224 .state = 0
225 };
226diff --git a/docs/feature_terminal.md b/docs/feature_terminal.md
227index 5c805e6ca514016d9d39d493ffca507ff8c43fdf..334a46c2d469b1342ad7b901b1599c872da014f1 100644
228--- a/docs/feature_terminal.md
229+++ b/docs/feature_terminal.md
230@@ -68,11 +68,11 @@ Prints out the entire keymap for a certain layer
231
232 ```
233 > keymap 0
234-0x002b, 0x0014, 0x001a, 0x0008, 0x0015, 0x0017, 0x001c, 0x0018, 0x000c, 0x0012, 0x0013, 0x002a,
235-0x0029, 0x0004, 0x0016, 0x0007, 0x0009, 0x000a, 0x000b, 0x000d, 0x000e, 0x000f, 0x0033, 0x0034,
236-0x00e1, 0x001d, 0x001b, 0x0006, 0x0019, 0x0005, 0x0011, 0x0010, 0x0036, 0x0037, 0x0038, 0x0028,
237+0x002b, 0x0014, 0x001a, 0x0008, 0x0015, 0x0017, 0x001c, 0x0018, 0x000c, 0x0012, 0x0013, 0x002a,
238+0x0029, 0x0004, 0x0016, 0x0007, 0x0009, 0x000a, 0x000b, 0x000d, 0x000e, 0x000f, 0x0033, 0x0034,
239+0x00e1, 0x001d, 0x001b, 0x0006, 0x0019, 0x0005, 0x0011, 0x0010, 0x0036, 0x0037, 0x0038, 0x0028,
240 0x5cd6, 0x00e0, 0x00e2, 0x00e3, 0x5cd4, 0x002c, 0x002c, 0x5cd5, 0x0050, 0x0051, 0x0052, 0x004f,
241->
242+>
243 ```
244
245 ### `exit`
246diff --git a/docs/feature_userspace.md b/docs/feature_userspace.md
247index 9d7737fe1de70cc44456049c07ce56d598bde7dd..950377423bdf85e0469c00ac9dc0bea5f101340c 100644
248--- a/docs/feature_userspace.md
249+++ b/docs/feature_userspace.md
250@@ -18,7 +18,7 @@ All this only happens when you build a keymap named `<name>`, like this:
251
252 make planck:<name>
253
254-For example,
255+For example,
256
257 make planck:jack
258
259@@ -32,9 +32,9 @@ Please include authorship (your name, github username, email), and optionally [a
260
261diff --git a/docs/flashing.md b/docs/flashing.md
262index 1adacc55c278c7f28e898b1cd3f1372a4db33475..8e1381f6981858ad34720713765eb5b00f0b6019 100644
263--- a/docs/flashing.md
264+++ b/docs/flashing.md
265@@ -12,7 +12,7 @@ To ensure compatibility with the DFU bootloader, make sure this block is present
266
267 # Bootloader
268 # This definition is optional, and if your keyboard supports multiple bootloaders of
269- # different sizes, comment this out, and the correct address will be loaded
270+ # different sizes, comment this out, and the correct address will be loaded
271 # automatically (+60). See bootloader.mk for all options.
272 BOOTLOADER = atmel-dfu
273
274@@ -57,7 +57,7 @@ To ensure compatibility with the Caterina bootloader, make sure this block is pr
275
276 # Bootloader
277 # This definition is optional, and if your keyboard supports multiple bootloaders of
278- # different sizes, comment this out, and the correct address will be loaded
279+ # different sizes, comment this out, and the correct address will be loaded
280 # automatically (+60). See bootloader.mk for all options.
281 BOOTLOADER = caterina
282
283@@ -86,7 +86,7 @@ To ensure compatibility with the Halfkay bootloader, make sure this block is pre
284
285 # Bootloader
286 # This definition is optional, and if your keyboard supports multiple bootloaders of
287- # different sizes, comment this out, and the correct address will be loaded
288+ # different sizes, comment this out, and the correct address will be loaded
289 # automatically (+60). See bootloader.mk for all options.
290 BOOTLOADER = halfkay
291
292diff --git a/docs/getting_started_build_tools.md b/docs/getting_started_build_tools.md
293index cd92ed68a7c4900d334ace0e78c6a64267a08b11..6c8eca0de4a4ea91ed37fac7cc0580585e5c14bf 100644
294--- a/docs/getting_started_build_tools.md
295+++ b/docs/getting_started_build_tools.md
296@@ -78,15 +78,15 @@ In addition to the Creators Update, you need Windows 10 Subystem for Linux, so i
297 ### Git
298 If you already have cloned the repository on your Windows file system you can ignore this section.
299
300diff --git a/docs/getting_started_make_guide.md b/docs/getting_started_make_guide.md
301index ecf030d1dd1ebc9f51b3855dce8e4574e75c80f7..39ea34a60f6ca86fb34482b2699236e7797d6923 100644
302--- a/docs/getting_started_make_guide.md
303+++ b/docs/getting_started_make_guide.md
304@@ -4,7 +4,7 @@ The full syntax of the `make` command is `<keyboard_folder>:<keymap>:<target>`,
305
306 * `<keyboard_folder>` is the path of the keyboard, for example `planck`
307 * Use `all` to compile all keyboards
308- * Specify the path to compile a revision, for example `planck/rev4` or `planck/rev3`
309+ * Specify the path to compile a revision, for example `planck/rev4` or `planck/rev3`
310 * If the keyboard doesn't have any folders, it can be left out
311 * To compile the default folder, you can leave it out
312 * `<keymap>` is the name of the keymap, for example `algernon`
313@@ -14,7 +14,7 @@ The full syntax of the `make` command is `<keyboard_folder>:<keymap>:<target>`,
314 The `<target>` means the following
315 * If no target is given, then it's the same as `all` below
316 * `all` compiles as many keyboard/revision/keymap combinations as specified. For example, `make planck/rev4:default` will generate a single .hex, while `make planck/rev4:all` will generate a hex for every keymap available to the planck.
317diff --git a/docs/glossary.md b/docs/glossary.md
318index 1ccd8f76c8607220d549c2ce5b7510ba0f82ea69..c8c54d6dedab1a79bdee7ee8311a8d6525fccbed 100644
319--- a/docs/glossary.md
320+++ b/docs/glossary.md
321@@ -167,4 +167,4 @@ The USB Host is your computer, or whatever device your keyboard is plugged into.
322
323 # Couldn't Find the Term You're Looking For?
324
325-[Open an issue](https://github.com/qmk/qmk_firmware/issues) with your question and the term in question could be added here. Better still, open a pull request with the definition. :)
326+[Open an issue](https://github.com/qmk/qmk_firmware/issues) with your question and the term in question could be added here. Better still, open a pull request with the definition. :)
327diff --git a/docs/hand_wire.md b/docs/hand_wire.md
328index 4d4bd3c72f90735b94789fb3687d665e68d7c25e..1cbc16dfea82b0e20797c0a16b8c9afcf8a4b764 100644
329--- a/docs/hand_wire.md
330+++ b/docs/hand_wire.md
331@@ -133,7 +133,7 @@ Starting at the top-left switch, place the diode (with tweezers if you have them
332 │o
333 ┌┴┐ o
334 │ │ O
335- ├─┤
336+ ├─┤
337 └┬┘
338 └─────────────
339 ```
340@@ -150,7 +150,7 @@ When the first diode is complete, the next one will need to be soldered to both
341 │o │o
342 ┌┴┐ o ┌┴┐ o
343 │ │ O │ │ O
344- ├─┤ ├─┤
345+ ├─┤ ├─┤
346 └┬┘ └┬┘
347 └────────────────┴─────────────
348 ```
349diff --git a/docs/hardware_keyboard_guidelines.md b/docs/hardware_keyboard_guidelines.md
350index fcc3b75ceb44e5bfd007cf9a7016712546f3f7da..0a4e2d11b8730fec7cac725e6f20f8a587969e78 100644
351--- a/docs/hardware_keyboard_guidelines.md
352+++ b/docs/hardware_keyboard_guidelines.md
353@@ -91,7 +91,7 @@ All key positions and rotations are specified in relation to the top-left corner
354 * `RY`
355 * The absolute position of the point to rotate the key around in the vertical axis. Default: `y`
356 * `KS`
357- * Key Shape: define a polygon by providing a list of points, in Key Units.
358+ * Key Shape: define a polygon by providing a list of points, in Key Units.
359 * **Important**: These are relative to the top-left of the key, not absolute.
360 * Example ISO Enter: `[ [0,0], [1.5,0], [1.5,2], [0.25,2], [0.25,1], [0,1], [0,0] ]`
361
362diff --git a/docs/isp_flashing_guide.md b/docs/isp_flashing_guide.md
363index c2668c63b4e3e8f520abd01b9accd7a63b0ad08b..8abc454868592d9cf092deff0e23537510e00353 100644
364--- a/docs/isp_flashing_guide.md
365+++ b/docs/isp_flashing_guide.md
366@@ -17,8 +17,8 @@ If you're having trouble flashing/erasing your board, and running into cryptic e
367 atmel.c:1434: Error flashing the block: err -2.
368 ERROR
369 Memory write error, use debug for more info.
370- commands.c:360: Error writing memory data. (err -4)
371-
372+ commands.c:360: Error writing memory data. (err -4)
373+
374diff --git a/docs/keycode.txt b/docs/keycode.txt
375index 3ecf4242e67aba6099abe556ff7029903ad2496f..b2070f7117d67f71582067823a914f290d7470b5 100644
376--- a/docs/keycode.txt
377+++ b/docs/keycode.txt
378@@ -183,7 +183,7 @@ KC_RSHIFT KC_RSFT E5 Keyboard RightShift
379 KC_RALT E6 Keyboard RightAlt
380 KC_RGUI E7 Keyboard Right GUI(Windows/Apple/Meta key)
381
382-/*
383+/*
384 * Virtual keycodes
385 */
386 /* System Control */
387diff --git a/docs/keycodes_us_ansi_shifted.md b/docs/keycodes_us_ansi_shifted.md
388index 53b4cad594f97a5195fa231c66ec86c4edb1e281..5163b3bf15852c74c62cff3f0e42b678697f63a4 100644
389--- a/docs/keycodes_us_ansi_shifted.md
390+++ b/docs/keycodes_us_ansi_shifted.md
391@@ -1,6 +1,6 @@
392 # US ANSI Shifted Symbols
393
394-These keycodes correspond to characters that are "shifted" on a standard US ANSI keyboards. They do not have dedicated keycodes but are instead typed by holding down shift and then sending a keycode.
395+These keycodes correspond to characters that are "shifted" on a standard US ANSI keyboards. They do not have dedicated keycodes but are instead typed by holding down shift and then sending a keycode.
396
397 It's important to remember that all of these keycodes send a left shift - this may cause unintended actions if unaccounted for. The short code is preferred in most situations.
398
399diff --git a/docs/keymap.md b/docs/keymap.md
400index 96d4563c01c65e680248f30f00438226d4d216e3..8401ee1484b85daea960900c16005196de6fef21 100644
401--- a/docs/keymap.md
402+++ b/docs/keymap.md
403@@ -35,8 +35,8 @@ The state of the Keymap layer is determined by two 32 bit parameters:
404
405diff --git a/docs/power.txt b/docs/power.txt
406index 0abbbe48e832a5ca2f943f0f75d0272a3a661178..ff28ba0c7f1c5dc5407f7c5ec2a0454be793dd1d 100644
407--- a/docs/power.txt
408+++ b/docs/power.txt
409@@ -21,7 +21,7 @@ MCUSR MCU Status Register
410
411 SMCR Sleep Mode Control Register
412 SE Sleep Enable
413- SM2:0
414+ SM2:0
415 #define set_sleep_mode(mode) \
416 #define SLEEP_MODE_IDLE (0)
417 #define SLEEP_MODE_ADC _BV(SM0)
418diff --git a/docs/quantum_keycodes.md b/docs/quantum_keycodes.md
419index 4b7ee93846a71f72155a1226400656b5f2e9e130..1d7fc0e12706fc399bfe6f9e3a56205d57884b21 100644
420--- a/docs/quantum_keycodes.md
421+++ b/docs/quantum_keycodes.md
422@@ -2,7 +2,7 @@
423
424 Quantum keycodes allow for easier customisation of your keymap than the basic ones provide, without having to define custom actions.
425
426diff --git a/docs/understanding_qmk.md b/docs/understanding_qmk.md
427index 0d3d24017d6bbeaa1d7cc49568d2c88d02db8d5f..13b6e2ef63f9c3cbc093cb8e3451e4765e9fedde 100644
428--- a/docs/understanding_qmk.md
429+++ b/docs/understanding_qmk.md
430@@ -94,11 +94,11 @@ const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
431 }
432 ```
433
434-Notice how all of these arguments match up with the first half of the `KEYMAP()` macro from the last section? This is how we take a keycode and map it to our Matrix Scan from earlier.
435+Notice how all of these arguments match up with the first half of the `KEYMAP()` macro from the last section? This is how we take a keycode and map it to our Matrix Scan from earlier.
436
437 ##### State Change Detection
438
439diff --git a/docs/unit_testing.md b/docs/unit_testing.md
440index 31aa79f82d4fd3a421fb4d6178fac1252e71e929..06d23a9cce020019a43c3b0d755b84d690ed0e41 100644
441--- a/docs/unit_testing.md
442+++ b/docs/unit_testing.md
443@@ -52,7 +52,7 @@ In that model you would emulate the input, and expect a certain output from the
444