From 922ed2b8a633d4e09ef5ae06128054f1d0c67e2b Mon Sep 17 00:00:00 2001
From: Huston Hedinger <1875033+hdngr@users.noreply.github.com>
Date: Sat, 24 Feb 2024 15:03:31 -0800
Subject: [PATCH] Update atak-plugin.mdx

---
 docs/software/integrations/atak-plugin.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/software/integrations/atak-plugin.mdx b/docs/software/integrations/atak-plugin.mdx
index 544b1683..d2732ecc 100644
--- a/docs/software/integrations/atak-plugin.mdx
+++ b/docs/software/integrations/atak-plugin.mdx
@@ -21,7 +21,7 @@ The ATAK plugin does not permit any Meshtastic configuration. The plugin does th
 
 1. Use the Meshtastic Android App on all parties' devices, and ensure they can talk to their local LoRa radio. Confirm they are able to achieve basic text messaging using the App.
 
-2. Set the device's role to `TAK` in the (device configuration settings)[/docs/configuration/radio/device/].
+2. Set the device's role to `TAK` in the [device configuration settings](/docs/configuration/radio/device/).
 
 3. With the Meshtastic Android App running in the background (to ensure the IMeshService is alive), launch ATAK (with the Meshtastic ATAK-Plugin installed or install it once ATAK is running) and you should observe a green Meshtastic icon in the bottom right. If the icon is red, then the plugin was not able to bind to the IMeshService provided by the Meshtastic Android App. If this is the case, check to ensure the Meshtastic Android App is functioning. The plugin will reconnect after a failed bind without restarting ATAK.