Updated Keymap (markdown)

[qmk_firmware.git] / Keymap.md

diff --git a/Keymap.md b/Keymap.md
index a3f40d392e8431b402a81c9e2980f8073e604e6e..bc135dd6f7c8274a2b84c277229fb5c0284b5fee 100644 (file)
--- a/Keymap.md
+++ b/Keymap.md
@@ -1,6 +1,6 @@
 # Keymap Overview
 
-QMK keymaps are defined inside a C source file. The data structure is an array of arrays. The outer array is a list of layer arrays while the inner layer array is a list of keys. Most keyboards define a KEYMAP() macro to help you create this array of arrays.
+QMK keymaps are defined inside a C source file. The data structure is an array of arrays. The outer array is a list of layer arrays while the inner layer array is a list of keys. Most keyboards define a `KEYMAP()` macro to help you create this array of arrays.
 
 ## Anatomy Of A `keymap.c`
 
@@ -20,10 +20,12 @@ At the top of the file you'll find this:
     #define GRAVE_MODS  (MOD_BIT(KC_LSHIFT)|MOD_BIT(KC_RSHIFT)|MOD_BIT(KC_LGUI)|MOD_BIT(KC_RGUI)|MOD_BIT(KC_LALT)|MOD_BIT(KC_RALT))
     #define _______ KC_TRNS
 
-    // Each layer gets a name for readability, which is then used in the keymap matrix below.
-    // The underscores don't mean anything - you can have a layer called STUFF or any other name.
-    // Layer names don't all need to be of the same length, obviously, and you can also skip them
-    // entirely and just use numbers.
+    // Each layer gets a name for readability.
+    // The underscores don't mean anything - you can
+    // have a layer called STUFF or any other name.
+    // Layer names don't all need to be of the same 
+    // length, and you can also skip them entirely
+    // and just use numbers.
     #define _BL 0
     #define _FL 1
     #define _CL 2