summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCasper Weiss Bang <master@thecdk.net>2020-01-02 22:06:46 +0100
committerfauxpark <fauxpark@gmail.com>2020-01-03 08:06:46 +1100
commitdd04079098a17e22693e83de227001fe548c1606 (patch)
treeba91ef193f437eb0a54d61a9ed506a2ba6ef360e
parentf08ffc271534ebe2bc4ea794bf95159c006688ad (diff)
downloadqmk_firmware-dd04079098a17e22693e83de227001fe548c1606.tar.gz
qmk_firmware-dd04079098a17e22693e83de227001fe548c1606.zip
Fixed a small typo (#7743)
-rw-r--r--docs/newbs_building_firmware.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/newbs_building_firmware.md b/docs/newbs_building_firmware.md
index 5a8f181b8c..d7d31c07fe 100644
--- a/docs/newbs_building_firmware.md
+++ b/docs/newbs_building_firmware.md
@@ -42,7 +42,7 @@ Open up your `keymap.c`. Inside this file you'll find the structure that control
const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
-This line indicates the start of the list of Layers. Below that you'll find lines containing either `LAYOUT` or `KEYMAP`, and these lines indicate the start of a layer. Below that line is the list of keys that comprise a that particular layer.
+This line indicates the start of the list of Layers. Below that you'll find lines containing either `LAYOUT` or `KEYMAP`, and these lines indicate the start of a layer. Below that line is the list of keys that comprise a particular layer.
!> When editing your keymap file be careful not to add or remove any commas. If you do you will prevent your firmware from compiling and it may not be easy to figure out where the extra, or missing, comma is.