diff --git a/content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx b/content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx
index c895a0e668..efe3b5c49b 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/index.mdx
@@ -159,7 +159,7 @@ The following table shows which referential action each database supports.
 | CockroachDB   | ✔️      | ✔️         | ✔️        | ✔️       | ✔️          |
 | MongoDB††     | ✔️      | ✔️         | ✔️        | ✔️       | ❌         |
 
-- † See [special cases for MySQL](#mysql).
+- † See [special cases for MySQL](#mysqlmariadb).
 - ⌘ See [special cases for PostgreSQL](#postgresql).
 - ‡ See [special cases for SQL Server](#sql-server).
 - †† Referential actions for MongoDB are available in Prisma ORM versions 3.7.0 and later.
diff --git a/content/300-accelerate/600-faq.mdx b/content/300-accelerate/600-faq.mdx
index 3e46d6d8b1..9aa920820e 100644
--- a/content/300-accelerate/600-faq.mdx
+++ b/content/300-accelerate/600-faq.mdx
@@ -110,6 +110,6 @@ Based on our experimentation, we’ve seen cache items persist for around 18 hou
 
 In the rare event of a service disruption, falling back to a direct connection would bypass the connection pool. This could potentially deplete the database's available connections and cause other issues on the database level.
 
-If there is a service disruption, it's recommended to verify on the [status page](https://pris.ly/data-platform-status). You can reach out to one of Prisma's [support channels](https://www.prisma.io/docs/platform/support) for assistance.
+If there is a service disruption, it's recommended to verify on the [status page](https://pris.ly/data-platform-status). You can reach out to one of Prisma's [support channels](/platform/support) for assistance.
 
-> **Note:** Additionally, it's worth noting that some edge function runtime environments may not support direct connections with Prisma ORM. For further details, refer to our [Edge functions documentation](https://www.prisma.io/docs/orm/prisma-client/deployment/edge/overview).
+> **Note:** Additionally, it's worth noting that some edge function runtime environments may not support direct connections with Prisma ORM. For further details, refer to our [Edge functions documentation](/orm/prisma-client/deployment/edge/overview).
diff --git a/content/400-pulse/500-known-limitations.mdx b/content/400-pulse/500-known-limitations.mdx
index d892ef8f42..a58083bf88 100644
--- a/content/400-pulse/500-known-limitations.mdx
+++ b/content/400-pulse/500-known-limitations.mdx
@@ -45,7 +45,7 @@ For example, if you have two models in your schema, the `User` and `Post` model.
 CREATE PUBLICATION user_publication FOR TABLE users;
 ```
 
-> To learn more about creating custom publication slots, see [managing your publication slot](https://www.prisma.io/docs/pulse/database-setup/general-database-instructions#manage-your-own-publication-slot).
+> To learn more about creating custom publication slots, see [managing your publication slot](/pulse/database-setup/general-database-instructions#manage-your-own-publication-slot).
 
 Your resulting subscription code would be: