summaryrefslogtreecommitdiffstats
path: root/docs/getting_started_vagrant.md
diff options
context:
space:
mode:
authorfauxpark <fauxpark@gmail.com>2017-12-09 06:36:32 +0100
committerJack Humbert <jack.humb@gmail.com>2017-12-09 16:46:11 +0100
commit7b0356d1d49da6574570e110f61f95692afdb3d0 (patch)
treea3e70802085ea8089f1e7851529f0296247fa264 /docs/getting_started_vagrant.md
parent6eb89ae906db7f226570e1839b88dcdd3a8fa962 (diff)
downloadqmk_firmware-7b0356d1d49da6574570e110f61f95692afdb3d0.tar.gz
qmk_firmware-7b0356d1d49da6574570e110f61f95692afdb3d0.tar.xz
Convert all headings to Title Case
Diffstat (limited to 'docs/getting_started_vagrant.md')
-rw-r--r--docs/getting_started_vagrant.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/getting_started_vagrant.md b/docs/getting_started_vagrant.md
index 705a6af1a..e8542d751 100644
--- a/docs/getting_started_vagrant.md
+++ b/docs/getting_started_vagrant.md
@@ -10,7 +10,7 @@ Using the `/Vagrantfile` in this repository requires you have [Vagrant](http://w
Other than having Vagrant and Virtualbox installed and possibly a restart of your computer afterwards, you can simple run a 'vagrant up' anywhere inside the folder where you checked out this project and it will start a Linux virtual machine that contains all the tools required to build this project. There is a post Vagrant startup hint that will get you off on the right foot, otherwise you can also reference the build documentation below.
-# Flashing the firmware
+# Flashing the Firmware
The "easy" way to flash the firmware is using a tool from your host OS: