From 3c6d2e2b3f8aadd918ff72c4dd6f2c9639145d4c Mon Sep 17 00:00:00 2001
From: Simon Chan <1330321+yume-chan@users.noreply.github.com>
Date: Tue, 6 Aug 2024 02:35:43 +0800
Subject: [PATCH] fix broken links

---
 docs/tango/custom-transport/index.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/tango/custom-transport/index.mdx b/docs/tango/custom-transport/index.mdx
index 0fe1845..5f83550 100644
--- a/docs/tango/custom-transport/index.mdx
+++ b/docs/tango/custom-transport/index.mdx
@@ -6,7 +6,7 @@ While there might not be any other transports that can create ADB Sockets direct
 
 :::info
 
-The difference between a custom transport and a custom [Daemon Transport connection](./daemon/custom-connection.mdx) or [Server Transport connector](./server/client.mdx#create-connector) is that, the former handles raw request and response data for ADB commands, while the latter always has those data in an encoded format.
+The difference between a custom transport and a custom [Daemon Transport connection](../daemon/custom-connection.mdx) or [Server Transport connector](../server/client.mdx#create-connector) is that, the former handles raw request and response data for ADB commands, while the latter always has those data in an encoded format.
 
 For example, to write a unit test for an ADB command, a custom transport only needs to return the expected response data, but a Daemon Transport connection must encode that response using Daemon protocol, which then gets decoded by Daemon Transport.