summaryrefslogtreecommitdiffstats
path: root/docs/feature_macros.md
diff options
context:
space:
mode:
authornoroadsleft <xxiinophobia@yahoo.com>2019-02-22 00:24:44 +0100
committerDrashna Jaelre <drashna@live.com>2019-02-22 08:19:26 +0100
commit384fef72d3a08f6bdc4e8557caf0bb78953dab32 (patch)
tree547202f9e3be33692c5c49920c176e5f4f057396 /docs/feature_macros.md
parent8a2346eda1e9fbdec71adf023a1337d5536fe1fa (diff)
downloadqmk_firmware-384fef72d3a08f6bdc4e8557caf0bb78953dab32.tar.gz
qmk_firmware-384fef72d3a08f6bdc4e8557caf0bb78953dab32.tar.xz
Replace instances of KEYMAP with LAYOUT
Many instances in the QMK Docs referenced KEYMAP macros, which is outdated terminology. Replaced most instances of KEYMAP with LAYOUT, to reflect the desired usage.
Diffstat (limited to 'docs/feature_macros.md')
-rw-r--r--docs/feature_macros.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/feature_macros.md b/docs/feature_macros.md
index aa13fb97f..79419abd2 100644
--- a/docs/feature_macros.md
+++ b/docs/feature_macros.md
@@ -183,11 +183,11 @@ A macro can include the following commands:
### Mapping a Macro to a Key
-Use the `M()` function within your `KEYMAP()` to call a macro. For example, here is the keymap for a 2-key keyboard:
+Use the `M()` function within your keymap to call a macro. For example, here is the keymap for a 2-key keyboard:
```c
const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
- [0] = KEYMAP(
+ [0] = LAYOUT(
M(0), M(1)
),
};
@@ -216,7 +216,7 @@ If you have a bunch of macros you want to refer to from your keymap while keepin
#define M_BYE M(1)
const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
- [0] = KEYMAP(
+ [0] = LAYOUT(
M_HI, M_BYE
),
};