fix a bunch of broken prisma client links

content/200-orm/050-overview/500-databases/900-turso.mdx

@@ -9,7 +9,7 @@ tocDepth: 3
 
 This guide discusses the concepts behind using Prisma and Turso, explains the commonalities and differences between Turso and other database providers, and leads you through the process for configuring your application to integrate with Turso.
 
-Prisma support for Turso is currently in [Early Access](/about/prisma/releases#early-access). We would appreciate your feedback in this [GitHub discussion](https://github.com/prisma/prisma/discussions/21345).
+Prisma support for Turso is currently in [Early Access](/orm/more/releases#early-access). We would appreciate your feedback in this [GitHub discussion](https://github.com/prisma/prisma/discussions/21345).
 
 </TopBlock>
 
@@ -25,7 +25,7 @@ Prisma support for Turso is currently in [Early Access](/about/prisma/releases#e
 
 <Admonition type="warning">
 
-Support for Turso is available in [Early Access](/about/prisma/releases#early-access) from Prisma versions 5.4.2 and later.
+Support for Turso is available in [Early Access](/orm/more/releases#early-access) from Prisma versions 5.4.2 and later.
 
 </Admonition>
 

content/200-orm/100-prisma-client/100-queries/030-crud.mdx

@@ -222,7 +222,7 @@ async function main() {
 main()
 ```
 
-For more information about working with generated types, see: [Generated types](advanced-type-safety).
+For more information about working with generated types, see: [Generated types](/orm/prisma-client/type-safety).
 
 ### Create multiple records
 

content/200-orm/100-prisma-client/100-queries/090-raw-database-access/050-raw-queries.mdx

@@ -368,7 +368,7 @@ Prisma maps any database values returned by `$queryRaw` and `$queryRawUnsafe`to
 
 **Feature availability:**
 
-- In v3.14.x and v3.15.x, raw query type mapping was available with the preview feature `improvedQueryRaw`. We made raw query type mapping [Generally Available](/about/prisma/releases#generally-available-ga) in version 4.0.0, so you do not need to use `improvedQueryRaw` in version 4.0.0 or later.
+- In v3.14.x and v3.15.x, raw query type mapping was available with the preview feature `improvedQueryRaw`. We made raw query type mapping [Generally Available](/orm/more/releases#generally-available-ga) in version 4.0.0, so you do not need to use `improvedQueryRaw` in version 4.0.0 or later.
 - Before version 4.0.0, raw query type mapping was not available for SQLite.
 
 </Admonition>
@@ -426,7 +426,7 @@ Prisma resolves a number of issues with typecasting in PostgreSQL.
 
 <Admonition type="info">
 
-**Feature availability:** In v3.14.x and v3.15.x, these PostgreSQL fixes were available with the preview feature `improvedQueryRaw`. We made these fixes [Generally Available](/about/prisma/releases#generally-available-ga) in version 4.0.0, so you do not need to use `improvedQueryRaw` in version 4.0.0 or later.
+**Feature availability:** In v3.14.x and v3.15.x, these PostgreSQL fixes were available with the preview feature `improvedQueryRaw`. We made these fixes [Generally Available](/orm/more/releases#generally-available-ga) in version 4.0.0, so you do not need to use `improvedQueryRaw` in version 4.0.0 or later.
 
 </Admonition>
 

content/200-orm/100-prisma-client/200-special-fields-and-types/057-composite-types.mdx

@@ -15,7 +15,7 @@ Composite types are only available with MongoDB.
 
 [Composite types](/orm/prisma-schema/data-model#defining-composite-types), known as [embedded documents](https://docs.mongodb.com/manual/core/data-model-design/#std-label-data-modeling-embedding) in MongoDB, allow you to embed records within other records.
 
-We made composite types [Generally Available](/about/prisma/releases#generally-available-ga) in v3.12.0. They were previously available in [Preview](/orm/reference/preview-features) from v3.10.0.
+We made composite types [Generally Available](/orm/more/releases#generally-available-ga) in v3.12.0. They were previously available in [Preview](/orm/reference/preview-features) from v3.10.0.
 
 This page explains how to:
 

content/200-orm/100-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx

@@ -114,7 +114,7 @@ From v2.23.0, you can filter rows by the data inside a `Json` type. We call this
 
 The availability of advanced `Json` filtering depends on your Prisma version:
 
-- V4.0.0 or later: advanced `Json` filtering is [generally available](/about/prisma/releases#generally-available-ga).
+- V4.0.0 or later: advanced `Json` filtering is [generally available](/orm/more/releases#generally-available-ga).
 - From v2.23.0, but before v4.0.0: advanced `Json` filtering is a [preview feature](/orm/reference/preview-features/client-preview-features). Add `previewFeatures = ["filterJson"]` to your schema. [Learn more](/orm/reference/preview-features/client-preview-features#enabling-a-prisma-client-preview-feature).
 - Before v2.23.0: you can [filter on the exact `Json` field value](#filter-on-exact-field-value), but you cannot use the other features described in this section.
 

content/200-orm/100-prisma-client/500-deployment/001-deploy-prisma.mdx

@@ -19,13 +19,13 @@ Moreover, the user traffic pattern of your application is also an important fact
 
 ### Traditional servers
 
-Your application is [traditionally deployed](/orm/prisma-client/deployment/orm/prisma-client/deployment/traditional) if a Node.js process is continuously running and handles multiple requests at the same time. Your application could be deployed to a Platform-as-a-Service (PaaS) like [Heroku](/orm/prisma-client/deployment/orm/prisma-client/deployment/traditiona/orm/prisma-client/deployment/traditional/deploy-to-heroku), [Koyeb](/orm/prisma-client/deployment/orm/prisma-client/deployment/traditiona/orm/prisma-client/deployment/traditional/deploy-to-koyeb), as a Docker container to Kubernetes, or as a Node.js process on a virtual machine, or good old bare metal server.
+Your application is [traditionally deployed](/orm/prisma-client/deployment/traditional) if a Node.js process is continuously running and handles multiple requests at the same time. Your application could be deployed to a Platform-as-a-Service (PaaS) like [Heroku](/orm/prisma-client/deployment/traditional/deploy-to-heroku), [Koyeb](/orm/prisma-client/deployment/traditional/deploy-to-koyeb), as a Docker container to Kubernetes, or as a Node.js process on a virtual machine, or good old bare metal server.
 
 See also: [Connection management in long-running processes](/orm/prisma-client/setup-and-configuration/databases-connections#long-running-processes)
 
 ### Serverless Functions
 
-Your application is [serverless](/orm/prisma-client/deployment/serverless) if the Node.js processes of your application (or subsets of it broken into functions) are started as requests come in, and each function only handles one request at a time. Your application would most likely be deployed to a Function-as-a-Service (FaaS) offering, such as [AWS Lambda](/orm/prisma-client/deployment/serverless/orm/prisma-client/deployment/serverless/deploy-to-aws-lambda) or [Azure Functions](/orm/prisma-client/deployment/serverless/deploy-to-azure-functions)
+Your application is [serverless](/orm/prisma-client/deployment/serverless) if the Node.js processes of your application (or subsets of it broken into functions) are started as requests come in, and each function only handles one request at a time. Your application would most likely be deployed to a Function-as-a-Service (FaaS) offering, such as [AWS Lambda](/orm/prisma-client/deployment/serverless/deploy-to-aws-lambda) or [Azure Functions](/orm/prisma-client/deployment/serverless//deploy-to-azure-functions)
 
 Serverless environments have the concept of warm starts, which means that for subsequent invocations of the same function, it may use an already existing container that has the allocated processes, memory, file system (`/tmp` is writable on AWS Lambda), and even DB connection still available.
 

content/200-orm/100-prisma-client/500-deployment/550-deploy-database-changes-with-prisma-migrate.mdx

@@ -19,7 +19,7 @@ Instead of `migrate deploy`, [`db push`](/orm/prisma-migrate/workflows/prototypi
 
 </Admonition>
 
-Exactly when to run `prisma migrate deploy` depends on your platform. For example, a simplified [Heroku](/orm/prisma-client/deployment/traditiona/orm/prisma-client/deployment/traditional/deploy-to-heroku) workflow includes:
+Exactly when to run `prisma migrate deploy` depends on your platform. For example, a simplified [Heroku](/orm/prisma-client/deployment/traditional/deploy-to-heroku) workflow includes:
 
 1. Ensuring the `./prisma/migration` folder is in source control
 2. Running `prisma migrate deploy` during the [release phase](https://devcenter.heroku.com/articles/release-phase)

content/200-orm/300-prisma-schema/20-data-model/40-views.mdx

@@ -11,7 +11,7 @@ tocDepth: 3
 
 <Admonition type="warning">
 
-Support for views is currently a very early [Preview](/about/prisma/releases#preview) feature. You can add a view to your Prisma schema with the `view` keyword or introspect the views in your database schema with `db pull`. You cannot yet apply views in your schema to your database with Prisma Migrate and `db push` unless the changes are added manually to your migration file using the `--create-only` flag. <br /><br />For updates on progress with this feature, follow [our GitHub issue](https://github.com/prisma/prisma/issues/17335).
+Support for views is currently a very early [Preview](/orm/more/releases#preview) feature. You can add a view to your Prisma schema with the `view` keyword or introspect the views in your database schema with `db pull`. You cannot yet apply views in your schema to your database with Prisma Migrate and `db push` unless the changes are added manually to your migration file using the `--create-only` flag. <br /><br />For updates on progress with this feature, follow [our GitHub issue](https://github.com/prisma/prisma/issues/17335).
 
 </Admonition>
 

content/200-orm/500-reference/500-preview-features/050-client-preview-features.mdx

@@ -14,7 +14,7 @@ For more information, see [ORM releases and maturity levels](/orm/more/releases)
 
 ## Currently active Preview features
 
-The following [Preview](/about/prisma/releases#preview) feature flags are available for Prisma Client and Prisma schema:
+The following [Preview](/orm/more/releases#preview) feature flags are available for Prisma Client and Prisma schema:
 
 | Feature                                                                                      | Released into Preview                                          |                          Feedback issue                          |
 | -------------------------------------------------------------------------------------------- | :------------------------------------------------------------- | :--------------------------------------------------------------: |

content/200-orm/500-reference/500-preview-features/080-cli-preview-features.mdx

@@ -15,10 +15,10 @@ For more information, see [ORM releases and maturity levels](/orm/more/releases)
 
 ## Currently active Preview features
 
-There are currently no [Preview](/about/prisma/releases#preview) features for Prisma CLI.
+There are currently no [Preview](/orm/more/releases#preview) features for Prisma CLI.
 
 <!--
-The following [Preview](/about/prisma/releases#preview) CLI features are available:
+The following [Preview](/orm/more/releases#preview) CLI features are available:
 
 - [`migrate diff`](/orm/reference/prisma-cli-reference#migrate-diff) since release [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) - [Submit feedback](https://github.com/prisma/prisma/issues/11514)
 - [`db execute`](/orm/reference/prisma-cli-reference#db-execute) since release [3.9.0](https://github.com/prisma/prisma/releases/tag/3.9.0) - [Submit feedback](https://github.com/prisma/prisma/issues/11514)

content/200-orm/500-reference/500-preview-features/index.mdx

@@ -7,7 +7,7 @@ hiddenPage: false
 
 <TopBlock>
 
-Some Prisma features are released as [Previews](/about/prisma/releases#preview). [Share your feedback on all Preview features on GitHub](https://github.com/prisma/prisma/issues/3108). For information about available preview features and how to enable them, see:
+Some Prisma features are released as [Previews](/orm/more/releases#preview). [Share your feedback on all Preview features on GitHub](https://github.com/prisma/prisma/issues/3108). For information about available preview features and how to enable them, see:
 
 - [Prisma Client and Prisma schema preview features](client-preview-features)
 - [Prisma CLI preview features](cli-preview-features)

content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/600-upgrading-to-prisma-5/index.mdx

@@ -346,7 +346,7 @@ package:
 <details>
 <summary>Serverless Framework pattern suggestion</summary>
 
-The [recommended rule from our documentation](/orm/prisma-client/deployment/serverless/orm/prisma-client/deployment/serverless/deploy-to-aws-lambda#lambda-functions-with-arm64-architectures) is not affected by this change as it excludes all non desired engine files.
+The [recommended rule from our documentation](/orm/prisma-client/deployment/serverless/deploy-to-aws-lambda#lambda-functions-with-arm64-architectures) is not affected by this change as it excludes all non desired engine files.
 
 ```yaml highlight=6;normal
 package: