1 files changed, 8 insertions, 8 deletions
diff --git a/docs/feature_advanced_keycodes.md b/docs/feature_advanced_keycodes.md
index a6ddf458c..f748ccd70 100644
--- a/docs/feature_advanced_keycodes.md
+++ b/docs/feature_advanced_keycodes.md
@@ -256,10 +256,10 @@ If you press a Mod Tap key, tap another key (press and release) and then release
 For Instance:
- `SHFT_T(KC_A)` Down
+- `SFT_T(KC_A)` Down
 - `KC_X` Down
 - `KC_X` Up
- `SHFT_T(KC_A)` Up
+- `SFT_T(KC_A)` Up
 Normally, if you do all this within the `TAPPING_TERM` (default: 200ms) this will be registered as `ax` by the firmware and host system. With permissive hold enabled, this modifies how this is handled by considering the Mod Tap keys as a Mod if another key is tapped, and would registered as `X` (`SHIFT`+`x`). 
@@ -279,9 +279,9 @@ Setting `Ignore Mod Tap Interrupt` requires  holding both keys for the `TAPPING_
 For Instance:
- `SHFT_T(KC_A)` Down
+- `SFT_T(KC_A)` Down
 - `KC_X` Down
- `SHFT_T(KC_A)` Up
+- `SFT_T(KC_A)` Up
 - `KC_X` Up
 Normally, this would send `X` (`SHIFT`+`x`). With `Ignore Mod Tap Interrupt` enabled, holding both keys are required for the `TAPPING_TERM` to register the hold action. A quick tap will output `ax` in this case, while a hold on both will still output `X`  (`SHIFT`+`x`).
@@ -303,11 +303,11 @@ When the user holds a key after tap, this repeats the tapped key rather to hold
 Example:
- SHFT_T(KC_A) Down
+- SFT_T(KC_A) Down
- SHFT_T(KC_A) Up
+- SFT_T(KC_A) Up
- SHFT_T(KC_A) Down
+- SFT_T(KC_A) Down
 - wait more than tapping term...
- SHFT_T(KC_A) Up
+- SFT_T(KC_A) Up
 With default settings, `a` will be sent on the first release, then `a` will be sent on the second press allowing the computer to trigger its auto repeat function.

diff --git a/docs/feature_advanced_keycodes.md b/docs/feature_advanced_keycodes.md index a6ddf458c..f748ccd70 100644 --- a/docs/feature_advanced_keycodes.md +++ b/docs/feature_advanced_keycodes.md
@@ -256,10 +256,10 @@ If you press a Mod Tap key, tap another key (press and release) and then release
256		256
257	For Instance:	257	For Instance:
258		258
259	- `SHFT_T(KC_A)` Down	259	- `SFT_T(KC_A)` Down
260	- `KC_X` Down	260	- `KC_X` Down
261	- `KC_X` Up	261	- `KC_X` Up
262	- `SHFT_T(KC_A)` Up	262	- `SFT_T(KC_A)` Up
263		263
264	Normally, if you do all this within the `TAPPING_TERM` (default: 200ms) this will be registered as `ax` by the firmware and host system. With permissive hold enabled, this modifies how this is handled by considering the Mod Tap keys as a Mod if another key is tapped, and would registered as `X` (`SHIFT`+`x`).	264	Normally, if you do all this within the `TAPPING_TERM` (default: 200ms) this will be registered as `ax` by the firmware and host system. With permissive hold enabled, this modifies how this is handled by considering the Mod Tap keys as a Mod if another key is tapped, and would registered as `X` (`SHIFT`+`x`).
265		265
@@ -279,9 +279,9 @@ Setting `Ignore Mod Tap Interrupt` requires holding both keys for the `TAPPING_
279		279
280	For Instance:	280	For Instance:
281		281
282	- `SHFT_T(KC_A)` Down	282	- `SFT_T(KC_A)` Down
283	- `KC_X` Down	283	- `KC_X` Down
284	- `SHFT_T(KC_A)` Up	284	- `SFT_T(KC_A)` Up
285	- `KC_X` Up	285	- `KC_X` Up
286		286
287	Normally, this would send `X` (`SHIFT`+`x`). With `Ignore Mod Tap Interrupt` enabled, holding both keys are required for the `TAPPING_TERM` to register the hold action. A quick tap will output `ax` in this case, while a hold on both will still output `X` (`SHIFT`+`x`).	287	Normally, this would send `X` (`SHIFT`+`x`). With `Ignore Mod Tap Interrupt` enabled, holding both keys are required for the `TAPPING_TERM` to register the hold action. A quick tap will output `ax` in this case, while a hold on both will still output `X` (`SHIFT`+`x`).
@@ -303,11 +303,11 @@ When the user holds a key after tap, this repeats the tapped key rather to hold
303		303
304	Example:	304	Example:
305		305
306	- SHFT_T(KC_A) Down	306	- SFT_T(KC_A) Down
307	- SHFT_T(KC_A) Up	307	- SFT_T(KC_A) Up
308	- SHFT_T(KC_A) Down	308	- SFT_T(KC_A) Down
309	- wait more than tapping term...	309	- wait more than tapping term...
310	- SHFT_T(KC_A) Up	310	- SFT_T(KC_A) Up
311		311
312	With default settings, `a` will be sent on the first release, then `a` will be sent on the second press allowing the computer to trigger its auto repeat function.	312	With default settings, `a` will be sent on the first release, then `a` will be sent on the second press allowing the computer to trigger its auto repeat function.
313		313