diff --git a/docs/pages/deploy-a-cluster/helm-deployments/custom.mdx b/docs/pages/deploy-a-cluster/helm-deployments/custom.mdx
index 71674021f47d9..6a2153906673b 100644
--- a/docs/pages/deploy-a-cluster/helm-deployments/custom.mdx
+++ b/docs/pages/deploy-a-cluster/helm-deployments/custom.mdx
@@ -251,7 +251,7 @@ $ helm upgrade teleport teleport/teleport-cluster \
When using `custom` mode, you **must** use highly-available storage (e.g. etcd, DynamoDB, or Firestore) for multiple replicas to be supported.
- [Information on supported Teleport storage backends](../../set../../reference/backends.mdx)
+ [Information on supported Teleport storage backends](../../reference/backends.mdx)
Manually configuring NFS-based storage or `ReadWriteMany` volume claims is **NOT** supported for an HA deployment and will result in errors.
diff --git a/docs/pages/desktop-access/reference.mdx b/docs/pages/desktop-access/reference.mdx
index 743e5fb89590f..a2fa4f5c9256e 100644
--- a/docs/pages/desktop-access/reference.mdx
+++ b/docs/pages/desktop-access/reference.mdx
@@ -1,5 +1,6 @@
---
title: Desktop Access Reference
+description: Comprehensive guides to configuring and auditing Desktop Access.
layout: tocless-doc
---
diff --git a/docs/pages/faq.mdx b/docs/pages/faq.mdx
index 854f0b7d8c084..de598cfd4c817 100644
--- a/docs/pages/faq.mdx
+++ b/docs/pages/faq.mdx
@@ -116,7 +116,7 @@ Here is a detailed breakdown of the differences between Teleport's editions.
|Auth and Proxy Service management|Self-hosted|Self-hosted|Fully managed|
|Proxy Service domain name|Custom|Custom|A subdomain of `teleport.sh`|
|Version support|All supported releases available to install and download.|All supported releases available to install and download.|Deploys last stable release with 2-3 week lag for stability.|
-|[Backend support](set../../reference/backends.mdx)|Any S3-compatible storage for session records, many managed backends for custom audit log storage.|Any S3-compatible storage for session records, many managed backends for custom audit log storage|All data is stored in DynamoDB and S3 with server-side encryption|
+|[Backend support](reference/backends.mdx)|Any S3-compatible storage for session records, many managed backends for custom audit log storage.|Any S3-compatible storage for session records, many managed backends for custom audit log storage|All data is stored in DynamoDB and S3 with server-side encryption|
|Data storage location|Can store data anywhere in the world, on most managed cloud backends|Can store data anywhere in the world, on most managed cloud backends| Data is stored in `us-west-2`, with Proxy Service instances deployed across the world for low-latency access|
|[Hardware Security Module support](./deploy-a-cluster/teleport-enterprise/hsm.mdx) for encryption at rest|✖|✔|✖|
diff --git a/docs/pages/index.mdx b/docs/pages/index.mdx
index 35908abf68179..6783adf442736 100644
--- a/docs/pages/index.mdx
+++ b/docs/pages/index.mdx
@@ -87,13 +87,13 @@ Use Teleport to provide secure access to all of your infrastructure.
-
+
Collaborate through session sharing.
-
+
Discover servers and clusters with dynamic labels.
-
+
Connect to computing resources located behind firewalls or without static IPs.
diff --git a/docs/pages/server-access/getting-started.mdx b/docs/pages/server-access/getting-started.mdx
index 46d16f577bdce..2bd53c947f468 100644
--- a/docs/pages/server-access/getting-started.mdx
+++ b/docs/pages/server-access/getting-started.mdx
@@ -346,7 +346,7 @@ Feel free to shut down, clean up, and delete your resources, or use them in furt
## Next steps
-- Learn more about Teleport `tsh` through the [reference documentation](../set../../reference/cli.mdx#tsh-ssh).
+- Learn more about Teleport `tsh` through the [reference documentation](../reference/cli.mdx#tsh-ssh).
- Learn more about [Teleport Nodes](../architecture/nodes.mdx#connecting-to-nodes)
- For a complete list of ports used by Teleport, read the [Networking Guide](../reference/networking.mdx).