From 8b9db57957ca70092bba433076b2f97bc09da7c5 Mon Sep 17 00:00:00 2001
From: Pedro Diogo <158898+PedroDiogo@users.noreply.github.com>
Date: Sun, 15 Nov 2020 15:04:59 +0000
Subject: [PATCH] Update TapDance documentation

The code example was using an outdated header for `tapDanceAction` that used `row` and `col`.
Updated to use `key_addr` instead.

Solution found in this forum reply: https://community.keyboard.io/t/status-of-using-tapdance-with-chrysalis/4143/5

Signed-off-by: Pedro Diogo <158898+PedroDiogo@users.noreply.github.com>
---
 docs/plugins/TapDance.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/plugins/TapDance.md b/docs/plugins/TapDance.md
index 5a856230..c32f8dd6 100644
--- a/docs/plugins/TapDance.md
+++ b/docs/plugins/TapDance.md
@@ -66,7 +66,7 @@ time an action is to be performed.
 TD(0)
 
 // later in the Sketch:
-void tapDanceAction(uint8_t tap_dance_index, byte row, byte col, uint8_t tap_count,
+void tapDanceAction(uint8_t tap_dance_index, KeyAddr key_addr, uint8_t tap_count,
                     kaleidoscope::plugin::TapDance::ActionType tap_dance_action) {
   switch (tap_dance_index) {
   case 0:
@@ -131,7 +131,7 @@ property only:
 > how this function is called.
 >
 > The `tap_dance_index` and `tap_count` parameters help us choose which action
-> to perform. The `row` and `col` parameters tell us where the tap-dance key is
+> to perform. The `key_addr` parameter tells us where the tap-dance key is
 > on the keyboard.
 
 ## Dependencies