aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar TuxForLife <beatvidsofficial@gmail.com>2016-06-06 07:42:41 -0700
committerGravatar Jack Humbert <jack.humb@gmail.com>2016-06-06 10:42:41 -0400
commitea63714950c4fef930142c1b81626522dceb152c (patch)
treecb31b2841dc3bb10ec72069490c2a626c0acbba1
parent3e3a07fc97d66d5f001aa3da4496d1268f4797cc (diff)
downloadqmk_firmware-ea63714950c4fef930142c1b81626522dceb152c.tar.gz
Tiny typo (#386)
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index a6bd3c495..0990dd834 100644
--- a/README.md
+++ b/README.md
@@ -176,7 +176,7 @@ void matrix_scan_user(void) {
}
```
-As you can see, you have three function. you can use - `SEQ_ONE_KEY` for single-key sequences (Leader followed by just one key), and `SEQ_TWO_KEYS` and `SEQ_THREE_.EYS` for longer sequences. Each of these accepts one or more keycodes as arguments. This is an important point: You can use keycodes from **any layer on your keyboard**. That layer would need to be active for the leader macro to fire, obviously.
+As you can see, you have three function. you can use - `SEQ_ONE_KEY` for single-key sequences (Leader followed by just one key), and `SEQ_TWO_KEYS` and `SEQ_THREE_KEYS` for longer sequences. Each of these accepts one or more keycodes as arguments. This is an important point: You can use keycodes from **any layer on your keyboard**. That layer would need to be active for the leader macro to fire, obviously.
### Temporarily setting the default layer