Typo fixes

diff --git a/Keymaphttps:--github.com-qmk-qmk_firmware-wiki-Keymap-_history.md b/Keymaphttps:--github.com-qmk-qmk_firmware-wiki-Keymap-_history.md
index 3353c30c25d20adbc312fbc435486a736aaf57b4..593e245aeb4f21bf04adae3d1b5a96447acce309 100644 (file)
--- a/Keymaphttps:--github.com-qmk-qmk_firmware-wiki-Keymap-_history.md
+++ b/Keymaphttps:--github.com-qmk-qmk_firmware-wiki-Keymap-_history.md
@@ -96,7 +96,7 @@ We define the `fn_actions[]` array to point to custom functions. `F(N)` in a key
 
 In this case we've instructed QMK to call the `ACTION_FUNCTION` callback, which we will define in the next section.
 
-> This `fn_actions[]` interface is mostly for backward compatibility.  In QMK, you don't need to use `fn_actions[]`.  You can directly `ACTION_FUNCTION(N)` or any other action code value itself in `keymaps[][MATRIX_ROWS][MATRIX_COLS]`.  N in `F(N)` can only be 0 to 31.  Use of the action code directly in `keymaps` unlock this limitation.
+> This `fn_actions[]` interface is mostly for backward compatibility.  In QMK, you don't need to use `fn_actions[]`.  You can directly use `ACTION_FUNCTION(N)` or any other action code value itself normally generated by the macro in `keymaps[][MATRIX_ROWS][MATRIX_COLS]`.  N in `F(N)` can only be 0 to 31.  Use of the action code directly in `keymaps` unlocks this limitation.
 
 #### `action_function()`