summaryrefslogtreecommitdiff
path: root/docs/newbs_building_firmware.md
diff options
context:
space:
mode:
authorskullY <skullydazed@gmail.com>2020-02-27 20:53:50 -0800
committerskullydazed <skullydazed@users.noreply.github.com>2020-03-05 16:00:10 -0800
commit54c58ea6de61a0f1fefa06e8271e2e11f9027940 (patch)
tree2ce4163cda8164edccd6f06f6e384861a205006c /docs/newbs_building_firmware.md
parenta95a314f78fd96aca7cc496b10bd310e28b1b66e (diff)
downloadqmk_firmware-54c58ea6de61a0f1fefa06e8271e2e11f9027940.tar.gz
qmk_firmware-54c58ea6de61a0f1fefa06e8271e2e11f9027940.zip
Add explicit id tags to externally linked headers
Diffstat (limited to 'docs/newbs_building_firmware.md')
-rw-r--r--docs/newbs_building_firmware.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/newbs_building_firmware.md b/docs/newbs_building_firmware.md
index 5c112a1cab..ed94a1460d 100644
--- a/docs/newbs_building_firmware.md
+++ b/docs/newbs_building_firmware.md
@@ -39,7 +39,7 @@ How to complete this step is entirely up to you. Make the one change that's been
?> While you get a feel for how keymaps work, keep each change small. Bigger changes make it harder to debug any problems that arise.
-## Build Your Firmware
+## Build Your Firmware :id=build-your-firmware
When your changes to the keymap are complete you will need to build the firmware. To do so go back to your terminal window and run the compile command: