summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKonstantin Đorđević <vomindoraan@gmail.com>2019-01-14 10:00:03 -0800
committerskullydazed <skullydazed@users.noreply.github.com>2019-02-08 15:13:20 -0800
commit24b7d058e2e456dc4ec9cd1e640374b033b57223 (patch)
treed4904df1eaca45b578b3a7c638d1f6f3c7de6d71
parenta45b625b6253c30a573f29684829b6200c12b8a3 (diff)
Update docs/hardware_keyboard_guidelines.md
Co-Authored-By: skullydazed <skullydazed@users.noreply.github.com>
-rw-r--r--docs/hardware_keyboard_guidelines.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/hardware_keyboard_guidelines.md b/docs/hardware_keyboard_guidelines.md
index 6b996ecf62..e6be7aeced 100644
--- a/docs/hardware_keyboard_guidelines.md
+++ b/docs/hardware_keyboard_guidelines.md
@@ -72,7 +72,7 @@ The following functions are typically defined in this file:
### `<keyboard_name.h>`
-This file is used to define the matrix for your keyboard. You should define at least one CPP macro named `LAYOUT` which translates an array into a matrix representing your switch matrix. If it's possible to build your keyboard with multiple layouts you may define additional macros.
+This file is used to define the matrix for your keyboard. You should define at least one C macro named `LAYOUT` which translates an array into a matrix representing the physical switch matrix for your keyboard. If it's possible to build your keyboard with multiple layouts you may define additional macros.
When defining multiple layouts you should have a base layout, named `LAYOUT`, that supports all possible switch positions on your matrix, even if that layout is impossible to build physically. This is the macro you should use in your `default` keymap. You should then have additional keymaps named `default-<layout>` that use your other layout macros. This will make it easier for people to use the layouts you define.