docs: use relative links for doc pages

docs/pages/contributing/documentation/how-to-contribute.mdx

@@ -93,8 +93,7 @@ the most recent version of our documentation are reflected for the versions of
 Teleport we currently support.
 
 <Admonition type="tip" title="Supported Versions">
-You can find our list of currently supported versions in the FAQ:
-https://goteleport.com/docs/faq/#which-version-of-teleport-is-supported
+You can find our list of currently supported versions in the [FAQ](../../faq.mdx#which-version-of-teleport-is-supported).
 </Admonition>
 
 There are many ways to create a backport, and we will illustrate three common

docs/pages/database-access/troubleshooting.mdx

@@ -142,12 +142,12 @@ access see the [RBAC](../database-access/rbac.mdx) documentation.
 
 When TLS Routing is disable by default, the Teleport Proxy Service returns `8.0.0-Teleport` as the MySQL server version. In some cases, like connecting with a GUI Client, this can result in obtaining an `Unknown system variable 'query_cache_size'` error that indicates that MySQL capabilities were not properly negotiated between the MySQL client and server.
 
-One way to solve this issue is to [use the TLS Routing feature](https://goteleport.com/docs/manageAment/operations/tls-routing/), where the Teleport Proxy Service propagates the correct MySQL server version via TLS Routing extensions.
+One way to solve this issue is to [use the TLS Routing feature](../management/operations/tls-routing.mdx), where the Teleport Proxy Service propagates the correct MySQL server version via TLS Routing extensions.
 
-If migration to TLS Routing is not possible, another way to bypass this error is to use the [Teleport local proxy command](https://goteleport.com/docs/connect-your-client/gui-clients/#get-connection-information), which allows you to establish a TLS Routing connection to the Teleport Proxy Service even if TLS Routing was not enabled on the Teleport cluster.
+If migration to TLS Routing is not possible, another way to bypass this error is to use the [Teleport local proxy command](../connect-your-client/gui-clients.mdx#get-connection-information), which allows you to establish a TLS Routing connection to the Teleport Proxy Service even if TLS Routing was not enabled on the Teleport cluster.
 
 Another possibility is to overwrite the default MySQL server version (8.0.0-Teleport) returned by the Teleport Proxy Service. To do this, assign the `mysql_server_version` field in the `proxy_service` configuration block on your Teleport Proxy Service instances:
 ```yaml
 proxy_service:
   mysql_server_version: "8.0.4"
-```
+```

docs/pages/deploy-a-cluster/deployments/aws-gslb-proxy-peering-ha-deployment.mdx

@@ -24,8 +24,8 @@ entry while also ensuring minimal latency when accessing connected resources.
 - High-availability Auto Scaling group of Proxy Service instances deployed across multiple regions
 - [AWS Route 53 latency-based routing](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-latency.html) 
 - [GSLB](https://www.cloudflare.com/learning/cdn/glossary/global-server-load-balancing-gslb/)
-- [Teleport TLS Routing](https://goteleport.com/docs/architecture/tls-routing/) to reduce the number of ports needed to use Teleport
-- [Teleport Proxy Peering](https://goteleport.com/docs/architecture/proxy-peering/) for reducing the number of resource connections
+- [Teleport TLS Routing](../../architecture/tls-routing.mdx) to reduce the number of ports needed to use Teleport
+- [Teleport Proxy Peering](../../architecture/proxy-peering.mdx) for reducing the number of resource connections
 - [AWS Network Load Balancing](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html)
 - [AWS DynamoDB](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Introduction.html) for cluster state storage
 - [AWS S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html) for session recording storage
@@ -174,12 +174,12 @@ teleport:
         enabled: yes
     ...
 ```
-Review the [configuration reference](https://goteleport.com/docs/reference/config/) page for 
+Review the [configuration reference](../../reference/config.mdx) page for 
 additional settings.       
 
 ## Configure Proxy Peering
 
-In this deployment architecture, [Proxy Peering](https://goteleport.com/docs/architecture/proxy-peering/) is used to restrict the number of connections made from 
+In this deployment architecture, [Proxy Peering](../../architecture/proxy-peering.mdx) is used to restrict the number of connections made from 
 resources to proxies in the Teleport Cluster.
 
 This guide covers the necessary Proxy Peering settings for deploying an HA Teleport Cluster routing resource
@@ -196,7 +196,7 @@ auth_service:
   type: proxy_peering
   agent_connection_count: 2
 ```
-Reference the [Auth Server configuration](https://goteleport.com/docs/reference/config/#auth-service) reference page 
+Reference the [Auth Server configuration](../../reference/config.mdx#auth-service) reference page 
 for additional settings.
 
 ### Proxy Service Proxy Peering configuration 
@@ -243,5 +243,5 @@ proxy_service:
 the likelihood of agents being unavailable.
 </Admonition>
 
-Reference the [Proxy Service configuration](https://goteleport.com/docs/reference/config/#proxy-service) reference page 
+Reference the [Proxy Service configuration](../../reference/config.mdx#proxy-service) reference page 
 for additional settings.