summaryrefslogtreecommitdiffstats
path: root/keyboard
diff options
context:
space:
mode:
authorJack Humbert <jack.humb@gmail.com>2015-10-30 05:49:47 +0100
committerJack Humbert <jack.humb@gmail.com>2015-10-30 05:49:47 +0100
commit3511a830ac0ae0f3dbaaac22eca2c5360a9c7e2d (patch)
treee42e76f434b887441eb4da7e08a173b147504fe3 /keyboard
parent5901f5911b7642822b05c53a5a1d6b6549e15199 (diff)
downloadqmk_firmware-3511a830ac0ae0f3dbaaac22eca2c5360a9c7e2d.tar.gz
qmk_firmware-3511a830ac0ae0f3dbaaac22eca2c5360a9c7e2d.tar.xz
readme
Diffstat (limited to 'keyboard')
-rw-r--r--keyboard/atomic/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/keyboard/atomic/README.md b/keyboard/atomic/README.md
index 5e6727015..7c3095843 100644
--- a/keyboard/atomic/README.md
+++ b/keyboard/atomic/README.md
@@ -164,7 +164,7 @@ This requires [some hardware changes](https://www.reddit.com/r/MechanicalKeyboar
## Building
-Download or clone the whole firmware and navigate to the keyboard/planck folder. Once your dev env is setup, you'll be able to type `make` to generate your .hex - you can then use `make dfu` to program your PCB once you hit the reset button.
+Download or clone the whole firmware and navigate to the keyboard/atomic folder. Once your dev env is setup, you'll be able to type `make` to generate your .hex - you can then use `make dfu` to program your PCB once you hit the reset button.
Depending on which keymap you would like to use, you will have to compile slightly differently.