remove some unnecessary external links

Also clean up some trailing whitespace.

docs/cli.md

@@ -167,8 +167,7 @@ $ qmk compile -kb dz60
 ## `qmk flash`
 
 This command is similar to `qmk compile`, but can also target a bootloader. The bootloader is optional, and is set to `:flash` by default.
-To specify a different bootloader, use `-bl <bootloader>`. Visit <https://docs.qmk.fm/#/flashing>
-for more details of the available bootloaders.
+To specify a different bootloader, use `-bl <bootloader>`. Visit the [Flashing Firmware](flashing.md) guide for more details of the available bootloaders.
 
 **Usage for Configurator Exports**:
 

docs/keycodes.md

@@ -312,8 +312,8 @@ This is a reference only. Each group of keys links to the page documenting their
 |----------------|----------------------------------------------------------------------------------|
 |`DF(layer)`     |Set the base (default) layer                                                      |
 |`MO(layer)`     |Momentarily turn on `layer` when pressed (requires `KC_TRNS` on destination layer)|
-|`OSL(layer)`    |Momentarily activates `layer` until a key is pressed. See [One Shot Keys](https://docs.qmk.fm/#/feature_advanced_keycodes?id=one-shot-keys) for details. |
-|`LM(layer, mod)`|Momentarily turn on `layer` (like MO) with `mod` active as well.  Where `mod` is a mods_bit.  Mods can be viewed [here](https://docs.qmk.fm/#/feature_advanced_keycodes?id=mod-tap).  Example Implementation: `LM(LAYER_1, MOD_LALT)`|
+|`OSL(layer)`    |Momentarily activates `layer` until a key is pressed. See [One Shot Keys](feature_advanced_keycodes#one-shot-keys) for details. |
+|`LM(layer, mod)`|Momentarily turn on `layer` (like MO) with `mod` active as well.  Where `mod` is a mods_bit.  Mods can be viewed [here](feature_advanced_keycodes#mod-tap).  Example Implementation: `LM(LAYER_1, MOD_LALT)`|
 |`LT(layer, kc)` |Turn on `layer` when held, `kc` when tapped                                       |
 |`TG(layer)`     |Toggle `layer` on or off                                                          |
 |`TO(layer)`     |Turns on `layer` and turns off all other layers, except the default layer |

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.  
-1. Drag and dropping 
+Keycode Entry is accomplished in 3 ways.
+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)    
-[Advanced Keycode Reference](https://docs.qmk.fm/#/feature_advanced_keycodes)    
+[Basic Keycode Reference](keycodes_basic.md)    
+[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,22 +83,22 @@ 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
 
 #### What is the keycode for.......
 
 Please see
 
-[Basic Keycode Reference](https://docs.qmk.fm/#/keycodes_basic)    
-[Advanced Keycode Reference](https://docs.qmk.fm/#/feature_advanced_keycodes)    
+[Basic Keycode Reference](keycodes_basic.md)    
+[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
 

docs/support.md

@@ -6,13 +6,13 @@ Don't forget to read our [Code of Conduct](https://qmk.fm/coc/).
 
 ## Help! I don't know where to start! 
 
-If this is the case, then you should start with our [Newbs Guide](https://docs.qmk.fm/#/newbs). There is a lot of great info there, and that should cover everything you need to get started.
+If this is the case, then you should start with our [Newbs Guide](newbs.md). There is a lot of great info there, and that should cover everything you need to get started.
 
 If that's an issue, hop onto the [QMK Configurator](https://config.qmk.fm), as that will handle a majority of what you need there. 
 
 ## Help! I'm having issues flashing!
 
-First, head to the [Compiling/Flashing FAQ Page](https://docs.qmk.fm/#/faq_build). There is a good deal of info there, and you'll find a bunch of solutions to common issues there. 
+First, head to the [Compiling/Flashing FAQ Page](faq_build.md). There is a good deal of info there, and you'll find a bunch of solutions to common issues there. 
 
 ## Help, I have an issue that isn't covered by the links above
 
@@ -26,9 +26,9 @@ Then please open an [issue](https://github.com/qmk/qmk_firmware/issues/new), and
 
 ## But `git` and `GitHub` are intimidating! 
 
-Don't worry, we have some pretty nice [Guidelines](https://docs.qmk.fm/#/newbs_best_practices) on how to start using `git` and GitHub to make things easier to develop. 
+Don't worry, we have some pretty nice [Guidelines](newbs_git_best_practices.md) on how to start using `git` and GitHub to make things easier to develop. 
 
-Additionally, you can find additional `git` and GitHub related links [here](https://docs.qmk.fm/#/newbs_learn_more_resources).
+Additionally, you can find additional `git` and GitHub related links [here](newbs_learn_more_resources.md).
 
 ## I have a Keyboard that I want to add support for