1 files changed, 24 insertions, 24 deletions
diff --git a/docs/newbs_building_firmware_configurator.md b/docs/newbs_building_firmware_configurator.md
index becceb669..472b30cac 100644
--- a/docs/newbs_building_firmware_configurator.md
+++ b/docs/newbs_building_firmware_configurator.md
@@ -1,51 +1,51 @@
 # QMK Configurator
-The [QMK Configurator](https://config.qmk.fm) is an online graphical user interface that generates QMK Firmware hex files.  
+The [QMK Configurator](https://config.qmk.fm) is an online graphical user interface that generates QMK Firmware hex files.
 ?> **Please follow these steps in order.**
 Watch the [Video Tutorial](https://youtu.be/tx54jkRC9ZY)
-The QMK Configurator works best with Chrome/Firefox. 
+The QMK Configurator works best with Chrome/Firefox.
 !> **Files from other tools such as KLE, or kbfirmware will not be compatible with QMK Configurator. Do not load them, do not import them. QMK Configurator is a DIFFERENT tool. **
 ## Selecting your keyboard
-Click the drop down box and select the keyboard you want to create a keymap for. 
+Click the drop down box and select the keyboard you want to create a keymap for.
-?> If your keyboard has several versions, make sure you select the correct one.** 
+?> If your keyboard has several versions, make sure you select the correct one.**
 I'll say that again because it's important
 !> **MAKE SURE YOU SELECT THE RIGHT VERSION!**
-If your keyboard has been advertised to be powered by QMK but is not in the list, chances are a developer hasn't gotten to it yet or we haven't had a chance to merge it in yet. File an issue at [qmk_firmware](https://github.com/qmk/qmk_firmware/issues) requesting to support that particular keyboard, if there is no active [Pull Request](https://github.com/qmk/qmk_firmware/pulls?q=is%3Aopen+is%3Apr+label%3Akeyboard) for it. There are also QMK powered keyboards that are in their manufacturer's own github accounts. Double check for that as well. 
+If your keyboard has been advertised to be powered by QMK but is not in the list, chances are a developer hasn't gotten to it yet or we haven't had a chance to merge it in yet. File an issue at [qmk_firmware](https://github.com/qmk/qmk_firmware/issues) requesting to support that particular keyboard, if there is no active [Pull Request](https://github.com/qmk/qmk_firmware/pulls?q=is%3Aopen+is%3Apr+label%3Akeyboard) for it. There are also QMK powered keyboards that are in their manufacturer's own github accounts. Double check for that as well.
 ## Selecting your keyboard layout
-Choose the layout that best represents the keymap you want to create. Some keyboards do not have enough layouts or correct layouts defined yet. They will be supported in the future. 
+Choose the layout that best represents the keymap you want to create. Some keyboards do not have enough layouts or correct layouts defined yet. They will be supported in the future.
 ## Keymap Name
-Call this keymap what you want. 
+Call this keymap what you want.
 ?> If you are running into issues when compiling, it may be worth changing this name, as it may already exist in the QMK  Firmware repo.
 ## Creating Your Keymap
-Keycode Entry is accomplished in 3 ways.  
+Keycode Entry is accomplished in 3 ways.
-1. Drag and dropping 
+1. Drag and dropping
 2. Clicking on an empty spot on the layout and clicking the keycode you desire
-3. Clicking on an empty spot on the layout, pressing the physical key on your keyboard. 
+3. Clicking on an empty spot on the layout, pressing the physical key on your keyboard.
-Hover your mouse over a key and a short blurb will tell you what that keycode does. For a more verbose description please see    
+Hover your mouse over a key and a short blurb will tell you what that keycode does. For a more verbose description please see
-[Basic Keycode Reference](https://docs.qmk.fm/#/keycodes_basic)    
+[Basic Keycode Reference](keycodes_basic.md)    
-[Advanced Keycode Reference](https://docs.qmk.fm/#/feature_advanced_keycodes)    
+[Advanced Keycode Reference](feature_advanced_keycodes.md)    
-In the event that you can't find a layout that supports your keymap, for example three spots for spacebar, or two spots for backspace, or 2 spots for shift etc etc, Fill them ALL up. 
+In the event that you can't find a layout that supports your keymap, for example three spots for spacebar, or two spots for backspace, or 2 spots for shift etc etc, Fill them ALL up.
 ### Example:
@@ -57,21 +57,21 @@ In the event that you can't find a layout that supports your keymap, for example
 1 spot for left shift and 1 spot for iso support: Fill them both with left shift
-5 spots, but only 4 keys: Guess and check or ask someone who has done it before. 
+5 spots, but only 4 keys: Guess and check or ask someone who has done it before.
 ## Saving Your Keymap for Future Edits
-When you're satisfied with your keymap or just want to work on it later, press the `Export Keymap` button. It will save your keymap as the name you chose above appended with .json. 
+When you're satisfied with your keymap or just want to work on it later, press the `Export Keymap` button. It will save your keymap as the name you chose above appended with .json.
-You can then load this .json file in the future by pressing the `Import Keymap` button. 
+You can then load this .json file in the future by pressing the `Import Keymap` button.
-!> **CAUTION:** This is not the same type of .json file used for kbfirmware.com or any other tool. If you try to use this for those tools, or the .json from those tools with QMK Configurator, there is a chance your keyboard will **explode**. 
+!> **CAUTION:** This is not the same type of .json file used for kbfirmware.com or any other tool. If you try to use this for those tools, or the .json from those tools with QMK Configurator, there is a chance your keyboard will **explode**.
 ## Generating your firmware file
 Press the green `Compile` button.
-When the compilation is done, you will be able to press the green `Download Firmware` button. 
+When the compilation is done, you will be able to press the green `Download Firmware` button.
 ## Flashing Your Keyboard
@@ -83,9 +83,9 @@ Please refer to [Flashing Firmware](newbs_flashing.md)
 If the .json file was generated with QMK Configurator, congratulations you have stumbled upon a bug. File an issue at [qmk_configurator](https://github.com/qmk/qmk_configurator/issues)
-If not....how did you miss my big bold message at the top saying not to use other .json files? 
+If not....how did you miss my big bold message at the top saying not to use other .json files?
-#### There are extra spaces in my layout? What do I do? 
+#### There are extra spaces in my layout? What do I do?
 If you're referring to having three spots for space bar, the best course of action is to just fill them all with space bar. The same can be done for backspace and shifts
@@ -93,12 +93,12 @@ If you're referring to having three spots for space bar, the best course of acti
 Please see
-[Basic Keycode Reference](https://docs.qmk.fm/#/keycodes_basic)    
+[Basic Keycode Reference](keycodes_basic.md)    
-[Advanced Keycode Reference](https://docs.qmk.fm/#/feature_advanced_keycodes)    
+[Advanced Keycode Reference](feature_advanced_keycodes.md)    
 #### It won't compile
-Please double check the other layers of your keymap to make sure there are no random keys present. 
+Please double check the other layers of your keymap to make sure there are no random keys present.
 ## Problems and Bugs

diff --git a/docs/newbs_building_firmware_configurator.md b/docs/newbs_building_firmware_configurator.md index becceb669..472b30cac 100644 --- a/docs/newbs_building_firmware_configurator.md +++ b/docs/newbs_building_firmware_configurator.md
@@ -1,51 +1,51 @@
1	# QMK Configurator	1	# QMK Configurator
2		2
3	The [QMK Configurator](https://config.qmk.fm) is an online graphical user interface that generates QMK Firmware hex files.	3	The [QMK Configurator](https://config.qmk.fm) is an online graphical user interface that generates QMK Firmware hex files.
4		4
5	?> Please follow these steps in order.	5	?> Please follow these steps in order.
6		6
7	Watch the [Video Tutorial](https://youtu.be/tx54jkRC9ZY)	7	Watch the [Video Tutorial](https://youtu.be/tx54jkRC9ZY)
8		8
9	The QMK Configurator works best with Chrome/Firefox.	9	The QMK Configurator works best with Chrome/Firefox.
10		10
11		11
12	!> Files from other tools such as KLE, or kbfirmware will not be compatible with QMK Configurator. Do not load them, do not import them. QMK Configurator is a DIFFERENT tool.	12	!> Files from other tools such as KLE, or kbfirmware will not be compatible with QMK Configurator. Do not load them, do not import them. QMK Configurator is a DIFFERENT tool.
13		13
14	## Selecting your keyboard	14	## Selecting your keyboard
15		15
16	Click the drop down box and select the keyboard you want to create a keymap for.	16	Click the drop down box and select the keyboard you want to create a keymap for.
17		17
18	?> If your keyboard has several versions, make sure you select the correct one.**	18	?> If your keyboard has several versions, make sure you select the correct one.**
19		19
20	I'll say that again because it's important	20	I'll say that again because it's important
21		21
22	!> MAKE SURE YOU SELECT THE RIGHT VERSION!	22	!> MAKE SURE YOU SELECT THE RIGHT VERSION!
23		23
24	If your keyboard has been advertised to be powered by QMK but is not in the list, chances are a developer hasn't gotten to it yet or we haven't had a chance to merge it in yet. File an issue at [qmk_firmware](https://github.com/qmk/qmk_firmware/issues) requesting to support that particular keyboard, if there is no active [Pull Request](https://github.com/qmk/qmk_firmware/pulls?q=is%3Aopen+is%3Apr+label%3Akeyboard) for it. There are also QMK powered keyboards that are in their manufacturer's own github accounts. Double check for that as well.	24	If your keyboard has been advertised to be powered by QMK but is not in the list, chances are a developer hasn't gotten to it yet or we haven't had a chance to merge it in yet. File an issue at [qmk_firmware](https://github.com/qmk/qmk_firmware/issues) requesting to support that particular keyboard, if there is no active [Pull Request](https://github.com/qmk/qmk_firmware/pulls?q=is%3Aopen+is%3Apr+label%3Akeyboard) for it. There are also QMK powered keyboards that are in their manufacturer's own github accounts. Double check for that as well.
25		25
26	## Selecting your keyboard layout	26	## Selecting your keyboard layout
27		27
28	Choose the layout that best represents the keymap you want to create. Some keyboards do not have enough layouts or correct layouts defined yet. They will be supported in the future.	28	Choose the layout that best represents the keymap you want to create. Some keyboards do not have enough layouts or correct layouts defined yet. They will be supported in the future.
29		29
30	## Keymap Name	30	## Keymap Name
31		31
32	Call this keymap what you want.	32	Call this keymap what you want.
33		33
34	?> If you are running into issues when compiling, it may be worth changing this name, as it may already exist in the QMK Firmware repo.	34	?> If you are running into issues when compiling, it may be worth changing this name, as it may already exist in the QMK Firmware repo.
35		35
36	## Creating Your Keymap	36	## Creating Your Keymap
37		37
38	Keycode Entry is accomplished in 3 ways.	38	Keycode Entry is accomplished in 3 ways.
39	1. Drag and dropping	39	1. Drag and dropping
40	2. Clicking on an empty spot on the layout and clicking the keycode you desire	40	2. Clicking on an empty spot on the layout and clicking the keycode you desire
41	3. Clicking on an empty spot on the layout, pressing the physical key on your keyboard.	41	3. Clicking on an empty spot on the layout, pressing the physical key on your keyboard.
42		42
43	Hover your mouse over a key and a short blurb will tell you what that keycode does. For a more verbose description please see	43	Hover your mouse over a key and a short blurb will tell you what that keycode does. For a more verbose description please see
44		44
45	[Basic Keycode Reference](https://docs.qmk.fm/#/keycodes_basic)	45	[Basic Keycode Reference](keycodes_basic.md)
46	[Advanced Keycode Reference](https://docs.qmk.fm/#/feature_advanced_keycodes)	46	[Advanced Keycode Reference](feature_advanced_keycodes.md)
47		47
48	In the event that you can't find a layout that supports your keymap, for example three spots for spacebar, or two spots for backspace, or 2 spots for shift etc etc, Fill them ALL up.	48	In the event that you can't find a layout that supports your keymap, for example three spots for spacebar, or two spots for backspace, or 2 spots for shift etc etc, Fill them ALL up.
49		49
50	### Example:	50	### Example:
51		51
@@ -57,21 +57,21 @@ In the event that you can't find a layout that supports your keymap, for example
57		57
58	1 spot for left shift and 1 spot for iso support: Fill them both with left shift	58	1 spot for left shift and 1 spot for iso support: Fill them both with left shift
59		59
60	5 spots, but only 4 keys: Guess and check or ask someone who has done it before.	60	5 spots, but only 4 keys: Guess and check or ask someone who has done it before.
61		61
62	## Saving Your Keymap for Future Edits	62	## Saving Your Keymap for Future Edits
63		63
64	When you're satisfied with your keymap or just want to work on it later, press the `Export Keymap` button. It will save your keymap as the name you chose above appended with .json.	64	When you're satisfied with your keymap or just want to work on it later, press the `Export Keymap` button. It will save your keymap as the name you chose above appended with .json.
65		65
66	You can then load this .json file in the future by pressing the `Import Keymap` button.	66	You can then load this .json file in the future by pressing the `Import Keymap` button.
67		67
68	!> CAUTION: This is not the same type of .json file used for kbfirmware.com or any other tool. If you try to use this for those tools, or the .json from those tools with QMK Configurator, there is a chance your keyboard will explode.	68	!> CAUTION: This is not the same type of .json file used for kbfirmware.com or any other tool. If you try to use this for those tools, or the .json from those tools with QMK Configurator, there is a chance your keyboard will explode.
69		69
70	## Generating your firmware file	70	## Generating your firmware file
71		71
72	Press the green `Compile` button.	72	Press the green `Compile` button.
73		73
74	When the compilation is done, you will be able to press the green `Download Firmware` button.	74	When the compilation is done, you will be able to press the green `Download Firmware` button.
75		75
76	## Flashing Your Keyboard	76	## Flashing Your Keyboard
77		77
@@ -83,9 +83,9 @@ Please refer to [Flashing Firmware](newbs_flashing.md)
83		83
84	If the .json file was generated with QMK Configurator, congratulations you have stumbled upon a bug. File an issue at [qmk_configurator](https://github.com/qmk/qmk_configurator/issues)	84	If the .json file was generated with QMK Configurator, congratulations you have stumbled upon a bug. File an issue at [qmk_configurator](https://github.com/qmk/qmk_configurator/issues)
85		85
86	If not....how did you miss my big bold message at the top saying not to use other .json files?	86	If not....how did you miss my big bold message at the top saying not to use other .json files?
87		87
88	#### There are extra spaces in my layout? What do I do?	88	#### There are extra spaces in my layout? What do I do?
89		89
90	If you're referring to having three spots for space bar, the best course of action is to just fill them all with space bar. The same can be done for backspace and shifts	90	If you're referring to having three spots for space bar, the best course of action is to just fill them all with space bar. The same can be done for backspace and shifts
91		91
@@ -93,12 +93,12 @@ If you're referring to having three spots for space bar, the best course of acti
93		93
94	Please see	94	Please see
95		95
96	[Basic Keycode Reference](https://docs.qmk.fm/#/keycodes_basic)	96	[Basic Keycode Reference](keycodes_basic.md)
97	[Advanced Keycode Reference](https://docs.qmk.fm/#/feature_advanced_keycodes)	97	[Advanced Keycode Reference](feature_advanced_keycodes.md)
98		98
99	#### It won't compile	99	#### It won't compile
100		100
101	Please double check the other layers of your keymap to make sure there are no random keys present.	101	Please double check the other layers of your keymap to make sure there are no random keys present.
102		102
103	## Problems and Bugs	103	## Problems and Bugs
104		104