summaryrefslogtreecommitdiffstats
path: root/docs/flashing.md
diff options
context:
space:
mode:
authorfauxpark <fauxpark@gmail.com>2017-12-09 16:36:32 +1100
committerJack Humbert <jack.humb@gmail.com>2017-12-09 10:46:11 -0500
commit7b0356d1d49da6574570e110f61f95692afdb3d0 (patch)
treea3e70802085ea8089f1e7851529f0296247fa264 /docs/flashing.md
parent6eb89ae906db7f226570e1839b88dcdd3a8fa962 (diff)
Convert all headings to Title Case
Diffstat (limited to 'docs/flashing.md')
-rw-r--r--docs/flashing.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/flashing.md b/docs/flashing.md
index 5b3c1a4447..8a2e2806ec 100644
--- a/docs/flashing.md
+++ b/docs/flashing.md
@@ -1,4 +1,4 @@
-# Flashing Intrustructions / Bootloader Information
+# Flashing Instructions and Bootloader Information
There are quite a few different types of bootloaders that keyboards use, and just about all of the use a different flashing method. Luckily, projects like the [QMK Toolbox](https://github.com/qmk/qmk_toolbox/releases) aim to be compatible with all the different types without having to think about it much, but this article will describe the different types of bootloaders, and available methods for flashing them.
@@ -102,4 +102,3 @@ Flashing sequence:
2. Wait for the OS to detect the device
4. Flash a .hex file
5. Reset the device into application mode (may be done automatically)
-