From 20e335a95e28ae00c7c7ec7f197810ad6d7b63e8 Mon Sep 17 00:00:00 2001 From: fauxpark Date: Sat, 6 Jan 2024 01:07:27 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20@=20qmk/qmk?= =?UTF-8?q?=5Ffirmware@a474cac2c387830063d803b96c9ac920bc1a7255=20?= =?UTF-8?q?=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- keymap.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/keymap.md b/keymap.md index f9d45b32676..b9c5da6be70 100644 --- a/keymap.md +++ b/keymap.md @@ -125,7 +125,7 @@ At the top of the file you'll find this: These are some handy definitions we can use when building our keymap and our custom function. The `GRAVE_MODS` definition will be used later in our custom function, and the following `_BL`, `_FL`, and `_CL` defines make it easier to refer to each of our layers. -Note: You may also find some older keymap files may also have a define(s) for `_______` and/or `XXXXXXX`. These can be used in place for `KC_TRNS` and `KC_NO` respectively, making it easier to see what keys a layer is overriding. These definitions are now unecessary, as they are included by default. +Note: You may also find some older keymap files may also have a define(s) for `_______` and/or `XXXXXXX`. These can be used in place for `KC_TRNS` and `KC_NO` respectively, making it easier to see what keys a layer is overriding. These definitions are now unnecessary, as they are included by default. ### Layers and Keymaps