summaryrefslogtreecommitdiff
path: root/keyboards
diff options
context:
space:
mode:
authorArthur Nogueira Neves <github@arthurnn.com>2017-01-18 21:12:02 -0500
committerGitHub <noreply@github.com>2017-01-18 21:12:02 -0500
commit489d0ab5818555b8f8ff6e9e7d9a9ea717902ab0 (patch)
treeea2171cfabfb7200863a47a1005f8ed8ea53b9f5 /keyboards
parent3d264adfc5e4538b57315cb8d3d429b9ed310f25 (diff)
downloadqmk_firmware-489d0ab5818555b8f8ff6e9e7d9a9ea717902ab0.tar.gz
qmk_firmware-489d0ab5818555b8f8ff6e9e7d9a9ea717902ab0.zip
this is the atreus doc
Diffstat (limited to 'keyboards')
-rw-r--r--keyboards/atreus/readme.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/keyboards/atreus/readme.md b/keyboards/atreus/readme.md
index a4077668e3..8baa581f02 100644
--- a/keyboards/atreus/readme.md
+++ b/keyboards/atreus/readme.md
@@ -169,7 +169,7 @@ This requires [some hardware changes](https://www.reddit.com/r/MechanicalKeyboar
## Building
-Download or clone the whole firmware and navigate to the keyboards/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 keyboards/atreus 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.