summaryrefslogtreecommitdiffstats
path: root/docs/BUILD_GUIDE.md
diff options
context:
space:
mode:
authorJack Humbert <jack.humb@gmail.com>2017-06-10 14:58:24 -0400
committerJack Humbert <jack.humb@gmail.com>2017-06-10 14:58:24 -0400
commitca01d94005f67ec4fa9528353481faa622d949ae (patch)
treedd6d59d065492e3bb8192263a8a7e7cc0709c48f /docs/BUILD_GUIDE.md
parent558db0e03f0f3993e2b7fb5cc3f285393da0a4c3 (diff)
convert docs to lowercase and underscores
Diffstat (limited to 'docs/BUILD_GUIDE.md')
-rw-r--r--docs/BUILD_GUIDE.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/BUILD_GUIDE.md b/docs/BUILD_GUIDE.md
index 78cf00b917..8573b0fd15 100644
--- a/docs/BUILD_GUIDE.md
+++ b/docs/BUILD_GUIDE.md
@@ -35,7 +35,7 @@ Debian/Ubuntu example:
sudo apt-get install gcc-avr avr-libc dfu-programmer
### Vagrant
-If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that's ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the [VAGRANT_GUIDE file](VAGRANT_GUIDE.md).
+If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that's ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the [vagrant guide](vagrant_guide.md).
## Verify Your Installation
1. If you haven't already, obtain this repository ([https://github.com/qmk/qmk_firmware](https://github.com/qmk/qmk_firmware)). You can either download it as a zip file and extract it, or clone it using the command line tool git or the Github Desktop application.