diff options
| author | Anthony Som <half-kh-hacker@hackery.site> | 2018-10-01 17:39:45 +0100 |
|---|---|---|
| committer | Jack Humbert <jack.humb@gmail.com> | 2018-10-01 12:42:05 -0400 |
| commit | b3f6aa9480a5ddb0b0ba0d611d988121c0ff848b (patch) | |
| tree | 90c162995772385b5b579ef78bd7f2138fa27a27 | |
| parent | 285ed08867931e967d2660f6179a57d247191d4c (diff) | |
Correct small typo
A small typo (it -> in) that I noticed while reading through the documentation
| -rw-r--r-- | docs/flashing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/flashing.md b/docs/flashing.md index 66c08a3610..1edbe22253 100644 --- a/docs/flashing.md +++ b/docs/flashing.md @@ -2,7 +2,7 @@ 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. -If you have a bootloader selected with the `BOOTLOADER` variable in your `rules.mk`, QMK will automatically calculate if your .hex file is the right size to be flashed to the device, and output the total size it bytes (along with the max). To run this process manually, compile with the target `check-size`, eg `make planck/rev4:default:check-size`. +If you have a bootloader selected with the `BOOTLOADER` variable in your `rules.mk`, QMK will automatically calculate if your .hex file is the right size to be flashed to the device, and output the total size in bytes (along with the max). To run this process manually, compile with the target `check-size`, eg `make planck/rev4:default:check-size`. ## DFU |