summaryrefslogtreecommitdiff
path: root/readme.md
diff options
context:
space:
mode:
authorSeth Chandler <sethbc@sethbc.org>2016-07-17 03:24:36 -0400
committerSeth Chandler <sethbc@sethbc.org>2016-07-17 03:24:36 -0400
commita95ab371627073a85ae420118ac7d1d55a096583 (patch)
treebc56c8a5762070f6934545b8cac051720bcca9fd /readme.md
parent38508180c755158a1933bc74b1b294bab3dd4c57 (diff)
update link to Vagrant docfile
Diffstat (limited to 'readme.md')
-rw-r--r--readme.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/readme.md b/readme.md
index 07280c2b40..a8ed51b818 100644
--- a/readme.md
+++ b/readme.md
@@ -76,7 +76,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 file](doc/VAGRANT_GUIDE.md).
## Verify Your Installation
1. If you haven't already, obtain this repository ([https://github.com/jackhumbert/qmk_firmware](https://github.com/jackhumbert/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.