fix broken links (#5720)

* fix broken links

* fix self-referencing links on transactions page

content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database.mdx

@@ -152,7 +152,7 @@ datasource db {
 }
 ```
 
-> **Note**: Since February 2024, you can alternatively [use foreign key constraints on a database-level in PlanetScale](/orm/overview/databases/planetscale#option-2-enable-foreign-key-constraints-in-the-planetscale-settings), which omits the need for setting `relationMode = "prisma"`.
+> **Note**: Since February 2024, you can alternatively [use foreign key constraints on a database-level in PlanetScale](/orm/overview/databases/planetscale#option-2-enable-foreign-key-constraints-in-the-planetscale-database-settings), which omits the need for setting `relationMode = "prisma"`.
 
 The `url` is [set via an environment variable](/orm/prisma-schema/overview#accessing-environment-variables-from-the-schema) which is defined in `.env`:
 

content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database.mdx

@@ -137,7 +137,7 @@ datasource db {
 }
 ```
 
-> **Note**: Since February 2024, you can alternatively [use foreign key constraints on a database-level in PlanetScale](/orm/overview/databases/planetscale#option-2-enable-foreign-key-constraints-in-the-planetscale-settings), which omits the need for setting `relationMode = "prisma"`.
+> **Note**: Since February 2024, you can alternatively [use foreign key constraints on a database-level in PlanetScale](/orm/overview/databases/planetscale#option-2-enable-foreign-key-constraints-in-the-planetscale-database-settings), which omits the need for setting `relationMode = "prisma"`.
 
 The `url` is [set via an environment variable](/orm/prisma-schema/overview#accessing-environment-variables-from-the-schema) which is defined in `.env`:
 

content/200-orm/200-prisma-client/100-queries/058-transactions.mdx

@@ -9,8 +9,6 @@ tocDepth: 3
 
 A database transaction refers to a sequence of read/write operations that are _guaranteed_ to either succeed or fail as a whole. This section describes the ways in which the Prisma Client API supports transactions.
 
-For more in-depth examples and use cases, refer to the 📖 [transactions guide](/orm/prisma-client/queries/transactions).
-
 </TopBlock>
 
 ## Transactions overview
@@ -90,8 +88,6 @@ const updatedPost: Post = await prisma.post.update({
 })
 ```
 
-> Refer to the 📖 [transactions guide](/orm/prisma-client/queries/transactions#nested-writes) for more examples.
-
 ## Batch/bulk operations
 
 The following bulk operations run as transactions:
@@ -100,7 +96,7 @@ The following bulk operations run as transactions:
 - `updateMany`
 - `createMany`
 
-> Refer to the 📖 [transactions guide](/orm/prisma-client/queries/transactions#bulk-operations) for more examples.
+> Refer to the section about [bulk operations](#bulk-operations) for more examples.
 
 ## The <inlinecode>$transaction</inlinecode> API
 
@@ -173,7 +169,7 @@ Instead of immediately awaiting the result of each operation when it's performed
 
 > **Note**: Operations are executed according to the order they are placed in the transaction. Using a query in a transaction does not influence the order of operations in the query itself.
 >
-> Refer to the 📖 [transactions guide](/orm/prisma-client/queries/transactions#transaction-api) for more examples.
+> Refer to the secction about the [transactions API](#transaction-api) for more examples.
 
 From version 4.4.0, the sequential operations transaction API has a second parameter. You can use the following optional configuration option in this parameter:
 
@@ -207,7 +203,7 @@ If you use interactive transactions in preview from version 2.29.0 to 4.6.1 (inc
 
 </Admonition>
 
-To use interactive transactions, you can pass an async function into [`$transaction`](/orm/prisma-client/queries/transactions#transaction-api).
+To use interactive transactions, you can pass an async function into [`$transaction`](#transaction-api).
 
 The first argument passed into this async function is an instance of Prisma Client. Below, we will call this instance `tx`. Any Prisma Client call invoked on this `tx` instance is encapsulated into the transaction.
 
@@ -816,7 +812,7 @@ await prisma.team.deleteMany({
 
 #### Can I use bulk operations with the `$transaction([])` API?
 
-Yes - for example, you can include multiple `deleteMany` operations inside a `$transaction([])`.
+Yes — for example, you can include multiple `deleteMany` operations inside a `$transaction([])`.
 
 ### <inlinecode>$transaction([])</inlinecode> API
 
@@ -1334,7 +1330,7 @@ In the example above, both `update` queries run within a database transaction. W
 
 If the application encounters an error along the way, the async function will throw an exception and automatically **rollback** the transaction.
 
-You can learn more about interactive transactions in our [Transactions and Batch Queries documentation](/orm/prisma-client/queries/transactions#interactive-transactions).
+You can learn more about interactive transactions in this [section](#interactive-transactions).
 
 <Admonition type="warning">
 

content/200-orm/500-reference/250-error-reference.mdx

@@ -498,7 +498,7 @@ Prisma Pulse-related errors start with <inlinecode>P61xx</inlinecode>.
 
 An unexpected server error occurred.
 This can happen due to a technical issue within the Prisma Pulse or its infrastructure.
-For any incidents related to Prisma Pulse, you can refer to our status page [here](https://www.prisma-status.com/) and reach out to our support team through one of our available [channels](https://www.prisma.io/docs/platform/support) to report your issue.
+For any incidents related to Prisma Pulse, you can refer to our status page [here](https://www.prisma-status.com/) and reach out to our support team through one of our available [channels](/platform/support) to report your issue.
 
 #### <inlinecode>P6101</inlinecode> (<inlinecode>DatasourceError</inlinecode>) – HTTP Status <inlinecode>400</inlinecode>
 
@@ -519,7 +519,7 @@ Prisma Pulse is not enabled for the configured API key.
 
 Your Prisma Data Platform account has been blocked, potentially due to exceeding the usage limit included in your current plan. Please review the error message for further information.
 
-If you require further assistance, please get in touch with us via one of our support [channels](https://www.prisma.io/docs/platform/support).
+If you require further assistance, please get in touch with us via one of our support [channels](/platform/support).
 
 #### <inlinecode>P6105</inlinecode> (<inlinecode>VersionNotSupported</inlinecode>) – HTTP Status <inlinecode>400</inlinecode>
 

content/400-pulse/600-faq.mdx

@@ -49,9 +49,7 @@ Throughput for Prisma Pulse will increase as the Database event size decreases a
 While ensuring Database event size can be tricky, we recommend some best practices, such as:
 
 - Avoid large fields in your model, such as storing base64 image strings in the database; Instead, consider storing them in popular file storage options such as AWS S3 or Cloudflare.
-
-- Creating publication slots for specific models rather than all the models in the database. You can learn more about managing your replication slots [here](/pulse/getting-started#configuring-replication-slots).
-
+- Creating publication slots for specific models rather than all the models in the database. You can learn more about managing your replication slots [here](/pulse/database-setup/general-database-instructions#max_replication_slots).
 - Upgrading to use modern versions of PostgreSQL due to performance optimizations.
   > ℹ️ Modern versions of PostgreSQL (`v15`+) allow you to create a publication slot for specific fields of a particular model.