1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_tap_dance.md b/docs/feature_tap_dance.md
index 40f9802db..6edce651c 100644
--- a/docs/feature_tap_dance.md
+++ b/docs/feature_tap_dance.md
@@ -10,7 +10,7 @@ With this feature one can specify keys that behave differently, based on the amo
 First, you will need `TAP_DANCE_ENABLE = yes` in your `rules.mk`, because the feature is disabled by default. This adds a little less than 1k to the firmware size. 
-Optionally, you might want to set a custom `TAPPING_TERM` time by adding something like this in you `config.h`:
+Optionally, you might want to set a custom `TAPPING_TERM` time by adding something like this in your `config.h` file:
 ```c
 #define TAPPING_TERM 175

diff --git a/docs/feature_tap_dance.md b/docs/feature_tap_dance.md index 40f9802db..6edce651c 100644 --- a/docs/feature_tap_dance.md +++ b/docs/feature_tap_dance.md
@@ -10,7 +10,7 @@ With this feature one can specify keys that behave differently, based on the amo
10		10
11	First, you will need `TAP_DANCE_ENABLE = yes` in your `rules.mk`, because the feature is disabled by default. This adds a little less than 1k to the firmware size.	11	First, you will need `TAP_DANCE_ENABLE = yes` in your `rules.mk`, because the feature is disabled by default. This adds a little less than 1k to the firmware size.
12		12
13	Optionally, you might want to set a custom `TAPPING_TERM` time by adding something like this in you `config.h`:	13	Optionally, you might want to set a custom `TAPPING_TERM` time by adding something like this in your `config.h` file:
14		14
15	```c	15	```c
16	#define TAPPING_TERM 175	16	#define TAPPING_TERM 175