From 133db47e455d023e6f6e4d71cb8c0319f30008ab Mon Sep 17 00:00:00 2001
From: carlagn <goncalves@prisma.io>
Date: Thu, 4 Apr 2024 17:22:20 +0100
Subject: [PATCH] Revert "Revert "Docusaurus: fix:DA-199 update code
 highlighting name"" (#5811)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* Revert "Revert "Docusaurus: fix:DA-199 update code highlighting name (#5794)"…"

This reverts commit 7e00317ebaef26b48c5e3c2147c3c86064415d1b.

* update colors
---
 content/100-getting-started/01-quickstart.mdx | 16 +++---
 ...-relational-databases-node-cockroachdb.mdx | 12 ----
 .../110-relational-databases-node-mysql.mdx   | 13 -----
 ...-relational-databases-node-planetscale.mdx | 13 -----
 ...0-relational-databases-node-postgresql.mdx | 13 -----
 ...10-relational-databases-node-sqlserver.mdx | 13 -----
 ...ional-databases-typescript-cockroachdb.mdx | 12 ----
 ...-relational-databases-typescript-mysql.mdx | 13 -----
 ...ional-databases-typescript-planetscale.mdx | 13 -----
 ...tional-databases-typescript-postgresql.mdx | 13 -----
 ...ational-databases-typescript-sqlserver.mdx | 13 -----
 ...connect-your-database-node-cockroachdb.mdx | 24 +-------
 .../100-connect-your-database-node-mysql.mdx  | 24 +-------
 ...connect-your-database-node-planetscale.mdx | 27 +--------
 ...-connect-your-database-node-postgresql.mdx | 26 +--------
 ...0-connect-your-database-node-sqlserver.mdx | 23 +-------
 ...t-your-database-typescript-cockroachdb.mdx | 24 +-------
 ...connect-your-database-typescript-mysql.mdx | 24 +-------
 ...t-your-database-typescript-planetscale.mdx | 30 ++--------
 ...ct-your-database-typescript-postgresql.mdx | 24 +-------
 ...ect-your-database-typescript-sqlserver.mdx | 24 +-------
 ...-using-prisma-migrate-node-cockroachdb.mdx | 24 +-------
 .../150-using-prisma-migrate-node-mysql.mdx   | 24 +-------
 ...-using-prisma-migrate-node-planetscale.mdx | 24 +-------
 ...0-using-prisma-migrate-node-postgresql.mdx | 24 +-------
 ...50-using-prisma-migrate-node-sqlserver.mdx | 24 +-------
 ...-prisma-migrate-typescript-cockroachdb.mdx | 24 +-------
 ...-using-prisma-migrate-typescript-mysql.mdx | 24 +-------
 ...-prisma-migrate-typescript-planetscale.mdx | 24 +-------
 ...g-prisma-migrate-typescript-postgresql.mdx | 24 +-------
 ...ng-prisma-migrate-typescript-sqlserver.mdx | 24 +-------
 ...install-prisma-client-node-cockroachdb.mdx | 22 -------
 .../200-install-prisma-client-node-mysql.mdx  | 21 -------
 ...install-prisma-client-node-planetscale.mdx | 22 -------
 ...-install-prisma-client-node-postgresql.mdx | 22 -------
 ...0-install-prisma-client-node-sqlserver.mdx | 22 -------
 ...l-prisma-client-typescript-cockroachdb.mdx | 22 -------
 ...install-prisma-client-typescript-mysql.mdx | 21 -------
 ...l-prisma-client-typescript-planetscale.mdx | 22 -------
 ...ll-prisma-client-typescript-postgresql.mdx | 22 -------
 ...all-prisma-client-typescript-sqlserver.mdx | 22 -------
 ...querying-the-database-node-cockroachdb.mdx | 33 +++--------
 .../250-querying-the-database-node-mysql.mdx  | 27 ++-------
 ...querying-the-database-node-planetscale.mdx | 35 +++---------
 ...-querying-the-database-node-postgresql.mdx | 33 +++--------
 ...0-querying-the-database-node-sqlserver.mdx | 33 +++--------
 ...ng-the-database-typescript-cockroachdb.mdx | 57 +++----------------
 ...querying-the-database-typescript-mysql.mdx | 34 +++--------
 ...ng-the-database-typescript-planetscale.mdx | 56 +++---------------
 ...ing-the-database-typescript-postgresql.mdx | 34 +++--------
 ...ying-the-database-typescript-sqlserver.mdx | 55 +++---------------
 .../120-mongodb-node-mongodb.mdx              | 13 -----
 .../120-mongodb-typescript-mongodb.mdx        | 13 -----
 ...100-connect-your-database-node-mongodb.mdx | 24 +-------
 ...nnect-your-database-typescript-mongodb.mdx | 24 +-------
 ...reating-the-prisma-schema-node-mongodb.mdx | 24 +-------
 ...g-the-prisma-schema-typescript-mongodb.mdx | 23 +-------
 ...200-install-prisma-client-node-mongodb.mdx | 22 -------
 ...stall-prisma-client-typescript-mongodb.mdx | 22 -------
 ...250-querying-the-database-node-mongodb.mdx | 28 +++------
 ...erying-the-database-typescript-mongodb.mdx | 35 +++---------
 ...-relational-databases-node-cockroachdb.mdx | 13 -----
 .../110-relational-databases-node-mysql.mdx   | 13 -----
 ...-relational-databases-node-planetscale.mdx | 13 -----
 ...0-relational-databases-node-postgresql.mdx | 12 ----
 ...10-relational-databases-node-sqlserver.mdx | 13 -----
 ...ional-databases-typescript-cockroachdb.mdx | 14 -----
 ...-relational-databases-typescript-mysql.mdx | 13 -----
 ...ional-databases-typescript-planetscale.mdx | 13 -----
 ...tional-databases-typescript-postgresql.mdx | 13 -----
 ...ational-databases-typescript-sqlserver.mdx | 13 -----
 ...connect-your-database-node-cockroachdb.mdx | 26 +--------
 .../100-connect-your-database-node-mysql.mdx  | 21 +------
 ...connect-your-database-node-planetscale.mdx | 29 ++--------
 ...-connect-your-database-node-postgresql.mdx | 24 +-------
 ...0-connect-your-database-node-sqlserver.mdx | 23 +-------
 ...t-your-database-typescript-cockroachdb.mdx | 27 +--------
 ...connect-your-database-typescript-mysql.mdx | 27 +--------
 ...t-your-database-typescript-planetscale.mdx | 30 ++--------
 ...ct-your-database-typescript-postgresql.mdx | 24 +-------
 ...ect-your-database-typescript-sqlserver.mdx | 24 +-------
 .../150-introspection-node-cockroachdb.mdx    | 29 ++--------
 .../150-introspection-node-mysql.mdx          | 30 ++--------
 .../150-introspection-node-planetscale.mdx    | 30 ++--------
 .../150-introspection-node-postgresql.mdx     | 30 ++--------
 .../150-introspection-node-sqlserver.mdx      | 30 ++--------
 ...0-introspection-typescript-cockroachdb.mdx | 30 ++--------
 .../150-introspection-typescript-mysql.mdx    | 30 ++--------
 ...0-introspection-typescript-planetscale.mdx | 30 ++--------
 ...50-introspection-typescript-postgresql.mdx | 30 ++--------
 ...150-introspection-typescript-sqlserver.mdx | 30 ++--------
 ...aseline-your-database-node-cockroachdb.mdx | 22 -------
 .../170-baseline-your-database-node-mysql.mdx | 22 -------
 ...baseline-your-database-node-postgresql.mdx | 22 -------
 ...-baseline-your-database-node-sqlserver.mdx | 22 -------
 ...e-your-database-typescript-cockroachdb.mdx | 22 -------
 ...aseline-your-database-typescript-mysql.mdx | 22 -------
 ...ne-your-database-typescript-postgresql.mdx | 22 -------
 ...ine-your-database-typescript-sqlserver.mdx | 22 -------
 ...install-prisma-client-node-cockroachdb.mdx | 22 -------
 .../200-install-prisma-client-node-mysql.mdx  | 22 -------
 ...install-prisma-client-node-planetscale.mdx | 22 -------
 ...-install-prisma-client-node-postgresql.mdx | 22 -------
 ...0-install-prisma-client-node-sqlserver.mdx | 22 -------
 ...l-prisma-client-typescript-cockroachdb.mdx | 22 -------
 ...install-prisma-client-typescript-mysql.mdx | 22 -------
 ...l-prisma-client-typescript-planetscale.mdx | 22 -------
 ...ll-prisma-client-typescript-postgresql.mdx | 22 -------
 ...all-prisma-client-typescript-sqlserver.mdx | 22 -------
 ...querying-the-database-node-cockroachdb.mdx | 22 -------
 .../250-querying-the-database-node-mysql.mdx  | 22 -------
 ...querying-the-database-node-planetscale.mdx | 21 -------
 ...-querying-the-database-node-postgresql.mdx | 22 -------
 ...0-querying-the-database-node-sqlserver.mdx | 22 -------
 ...ng-the-database-typescript-cockroachdb.mdx | 29 ++--------
 ...querying-the-database-typescript-mysql.mdx | 30 ++--------
 ...ng-the-database-typescript-planetscale.mdx | 30 ++--------
 ...ing-the-database-typescript-postgresql.mdx | 30 ++--------
 ...ying-the-database-typescript-sqlserver.mdx | 30 ++--------
 ...75-evolve-your-schema-node-cockroachdb.mdx | 27 ++-------
 .../275-evolve-your-schema-node-mysql.mdx     | 22 ++-----
 ...275-evolve-your-schema-node-postgresql.mdx | 22 -------
 .../275-evolve-your-schema-node-sqlserver.mdx | 27 ++-------
 ...lve-your-schema-typescript-cockroachdb.mdx | 26 ++-------
 ...75-evolve-your-schema-typescript-mysql.mdx | 27 ++-------
 ...olve-your-schema-typescript-postgresql.mdx | 27 ++-------
 ...volve-your-schema-typescript-sqlserver.mdx | 29 ++--------
 .../120-mongodb-node-mongodb.mdx              | 13 -----
 .../120-mongodb-typescript-mongodb.mdx        | 13 -----
 ...100-connect-your-database-node-mongodb.mdx | 24 +-------
 ...nnect-your-database-typescript-mongodb.mdx | 23 +-------
 .../125-introspection-node-mongodb.mdx        | 29 ++--------
 .../125-introspection-typescript-mongodb.mdx  | 30 ++--------
 ...200-install-prisma-client-node-mongodb.mdx | 22 -------
 ...stall-prisma-client-typescript-mongodb.mdx | 22 -------
 ...250-querying-the-database-node-mongodb.mdx | 16 ------
 ...erying-the-database-typescript-mongodb.mdx | 30 ++--------
 .../100-introduction/100-what-is-prisma.mdx   |  2 +-
 .../04-is-prisma-an-orm.mdx                   |  2 +
 .../500-databases/200-database-drivers.mdx    |  1 +
 .../500-databases/300-postgresql.mdx          |  4 +-
 .../050-overview/500-databases/400-mysql.mdx  |  4 +-
 .../050-overview/500-databases/500-sqlite.mdx |  8 +--
 .../500-databases/600-mongodb.mdx             | 18 +++---
 .../500-databases/800-sql-server/index.mdx    |  9 +--
 .../500-databases/850-planetscale.mdx         | 16 ++++--
 .../500-databases/880-supabase.mdx            |  7 ++-
 .../050-overview/500-databases/890-neon.mdx   |  7 ++-
 .../050-overview/500-databases/900-turso.mdx  |  3 +
 .../100-prisma-schema/10-overview/index.mdx   |  1 +
 .../20-data-model/10-models.mdx               | 51 ++++++++++++++---
 .../20-relations/100-one-to-one-relations.mdx |  1 +
 .../20-relations/400-self-relations.mdx       |  6 ++
 ...-special-rules-for-referential-actions.mdx | 14 +++++
 .../410-referential-actions/index.mdx         | 26 ++++++---
 .../20-relations/420-relation-mode.mdx        | 13 +++--
 .../500-troubleshooting-relations.mdx         | 12 ++++
 .../20-data-model/20-relations/index.mdx      |  8 +++
 .../20-data-model/30-indexes.mdx              | 30 +++++-----
 .../20-data-model/40-views.mdx                | 12 +++-
 .../20-data-model/50-database-mapping.mdx     | 14 +++++
 .../20-data-model/60-multi-schema.mdx         | 17 ++++--
 .../70-unsupported-database-features.mdx      |  5 +-
 .../20-data-model/80-table-inheritance.mdx    |  2 +-
 .../80-postgresql-extensions.mdx              |  7 ++-
 .../005-introduction.mdx                      |  2 +-
 .../050-databases-connections/index.mdx       |  7 ++-
 .../100-custom-model-and-field-names.mdx      |  2 +
 .../100-queries/030-crud.mdx                  |  5 ++
 .../100-queries/037-relation-queries.mdx      |  9 ++-
 .../100-queries/050-filtering-and-sorting.mdx |  3 +
 .../056-aggregation-grouping-summarizing.mdx  |  1 +
 .../100-queries/058-transactions.mdx          |  8 +++
 .../100-queries/060-full-text-search.mdx      |  7 ++-
 .../100-queries/064-custom-models.mdx         |  2 +-
 .../050-raw-queries.mdx                       |  1 +
 .../100-custom-and-type-safe-queries.mdx      |  8 +++
 .../100-query-optimization-performance.mdx    |  4 ++
 .../057-composite-types.mdx                   |  3 +-
 .../100-working-with-json-fields.mdx          |  6 +-
 .../200-working-with-scalar-lists-arrays.mdx  |  2 +
 ...ing-with-composite-ids-and-constraints.mdx |  2 +
 .../300-client-extensions/100-model.mdx       |  1 +
 .../300-client-extensions/110-client.mdx      |  1 +
 .../300-client-extensions/120-query.mdx       |  1 +
 .../300-client-extensions/130-result.mdx      |  1 +
 .../140-shared-extensions.mdx                 |  1 +
 .../100-soft-delete-middleware.mdx            |  4 ++
 .../300-client-extensions/index.mdx           |  1 +
 .../400-type-safety/050-prisma-validator.mdx  |  4 ++
 .../830-prisma-type-system.mdx                | 11 ++--
 .../450-testing/100-unit-testing.mdx          |  5 +-
 .../450-testing/150-integration-testing.mdx   |  2 +-
 .../150-deploy-to-azure-functions.mdx         |  3 +-
 .../201-serverless/300-deploy-to-vercel.mdx   |  6 +-
 .../400-deploy-to-aws-lambda.mdx              |  8 ++-
 .../450-deploy-to-cloudflare-workers.mdx      |  3 +-
 .../301-edge/550-deploy-to-deno-deploy.mdx    |  6 +-
 ...y-database-changes-with-prisma-migrate.mdx |  2 +-
 ...oy-migrations-from-a-local-environment.mdx |  4 +-
 .../240-metrics.mdx                           |  3 +
 .../250-opentelemetry-tracing.mdx             |  5 +-
 .../230-handling-exceptions-and-errors.mdx    |  2 +-
 .../050-getting-started.mdx                   |  5 +-
 .../010-mental-model.mdx                      |  1 +
 .../200-shadow-database.mdx                   |  2 +
 .../300-workflows/10-seeding.mdx              |  4 +-
 .../300-workflows/100-team-development.mdx    | 12 +++-
 .../120-native-database-functions.mdx         |  4 +-
 .../20-prototyping-your-schema.mdx            |  1 +
 .../40-customizing-migrations.mdx             |  5 ++
 .../300-workflows/45-data-migration.mdx       | 10 +++-
 .../60-generating-down-migrations.mdx         |  7 ++-
 .../70-patching-and-hotfixing.mdx             |  4 +-
 .../100-prisma-schema-reference.mdx           | 18 ++++++
 .../500-reference/380-connection-urls.mdx     | 14 ++---
 .../700-upgrading-to-prisma-4.mdx             |  6 +-
 .../100-named-constraints.mdx                 |  3 +
 .../150-referential-actions.mdx               |  6 +-
 .../02-schema-incompatibilities-mysql.mdx     | 51 ++++++++++-------
 ...02-schema-incompatibilities-postgresql.mdx | 47 +++++++++------
 .../03-upgrading-the-prisma-layer-mysql.mdx   | 12 ++--
 ...-upgrading-the-prisma-layer-postgresql.mdx | 12 ++--
 .../01-migrate-from-typeorm.mdx               | 36 ++++++------
 .../02-migrate-from-sequelize.mdx             |  8 +--
 .../03-migrate-from-mongoose.mdx              | 18 +++++-
 .../600-vercel-caching-issue.mdx              |  2 +
 .../700-netlify-caching-issue.mdx             |  2 +
 .../800-check-constraints.mdx                 |  6 +-
 .../300-accelerate/200-getting-started.mdx    |  3 +-
 content/400-pulse/400-api-reference.mdx       |  1 +
 content/500-platform/20-concepts/index.mdx    |  1 -
 .../20-style-guide/01-writing-style.mdx       |  1 +
 .../20-style-guide/02-word-choice.mdx         |  1 +
 .../03-spelling-punctuation-formatting.mdx    |  2 +
 .../05-prisma-product-names.mdx               |  1 +
 .../20-style-guide/06-image-guidelines.mdx    |  1 +
 .../20-style-guide/10-boilerplate-content.mdx |  1 +
 .../200-prisma-docs/20-style-guide/index.mdx  |  1 +
 .../30-docs-components/index.mdx              |  1 -
 docusaurus.config.ts                          | 11 +++-
 src/css/custom.css                            |  5 +-
 src/css/theming.css                           |  5 +-
 .../CodeBlock/Container/styles.module.scss    |  1 +
 src/theme/CodeBlock/Line/index.tsx            |  2 +-
 src/theme/CodeBlock/Line/styles.module.css    | 24 ++++----
 src/theme/TabItem/index.tsx                   |  2 +-
 247 files changed, 861 insertions(+), 3189 deletions(-)

diff --git a/content/100-getting-started/01-quickstart.mdx b/content/100-getting-started/01-quickstart.mdx
index 74ed41b245..79736b22b2 100644
--- a/content/100-getting-started/01-quickstart.mdx
+++ b/content/100-getting-started/01-quickstart.mdx
@@ -154,7 +154,7 @@ import { PrismaClient } from '@prisma/client'
 const prisma = new PrismaClient()
 
 async function main() {
-  // highlight-start
+  // add-start
   const user = await prisma.user.create({
     data: {
       name: 'Alice',
@@ -162,7 +162,7 @@ async function main() {
     },
   })
   console.log(user)
-  // highlight-end
+  // add-end
 }
 
 main()
@@ -210,10 +210,10 @@ import { PrismaClient } from '@prisma/client'
 const prisma = new PrismaClient()
 
 async function main() {
-  // highlight-start
+  // add-start
   const users = await prisma.user.findMany()
   console.log(users)
-  // highlight-end
+  // add-end
 }
 
 main()
@@ -263,7 +263,7 @@ import { PrismaClient } from '@prisma/client'
 const prisma = new PrismaClient()
 
 async function main() {
-  // highlight-start
+  // add-start
   const user = await prisma.user.create({
     data: {
       name: 'Bob',
@@ -276,7 +276,7 @@ async function main() {
     },
   })
   console.log(user)
-  // highlight-end
+  // add-end
 }
 
 main()
@@ -322,14 +322,14 @@ import { PrismaClient } from '@prisma/client'
 const prisma = new PrismaClient()
 
 async function main() {
-// highlight-start
+// add-start
   const usersWithPosts = await prisma.user.findMany({
     include: {
       posts: true,
     },
   })
   console.dir(usersWithPosts, { depth: null })
-  // highlight-end
+  // add-end
 }
 
 main()
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-cockroachdb.mdx
index 00bb760dcf..e5c5303236 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-cockroachdb.mdx
@@ -50,15 +50,3 @@ npm install prisma --save-dev
 
 This creates a `package.json` with an initial setup for a Node.js app.
 
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-node-cockroachdb"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx
index 42077a32f9..c7eaab65d9 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-mysql.mdx
@@ -73,16 +73,3 @@ This command does two things:
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
 
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-node-mysql"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx
index 429646b354..9df70e4bad 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-planetscale.mdx
@@ -65,16 +65,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-node-planetscale"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx
index 6ed30008c2..0af9b49876 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-postgresql.mdx
@@ -72,16 +72,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-node-postgresql"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx
index 7691502cd3..1238c5b813 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-node-sqlserver.mdx
@@ -75,16 +75,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-node-sqlserver"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-cockroachdb.mdx
index 5185fcdc7c..684f7deda6 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-cockroachdb.mdx
@@ -78,15 +78,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-typescript-cockroachdb"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-mysql.mdx
index f95248d983..0b97c35a7b 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-mysql.mdx
@@ -78,16 +78,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-typescript-mysql"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-planetscale.mdx
index 6fbc13c06f..adc567a7ad 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-planetscale.mdx
@@ -84,16 +84,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-typescript-planetscale"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-postgresql.mdx
index 7346a2d127..e6a296c5c4 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-postgresql.mdx
@@ -77,16 +77,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-typescript-postgresql"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-sqlserver.mdx
index 23584767a5..80298bdd93 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases-typescript-sqlserver.mdx
@@ -80,16 +80,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-typescript-sqlserver"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx
index 5b02b1e6e9..9ef16be4d7 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -69,25 +69,3 @@ DATABASE_URL="postgresql://root@localhost:26257?sslmode=disable"
 ```
 
 Your connection string is displayed as part of the welcome text when starting CockroachDB from the command line.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/relational-databases-node-cockroachdb"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-node-cockroachdb"
-  arrow
->
-  Using Prisma Migrate
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-mysql.mdx
index e504af145b..a1b84f6fe2 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-mysql.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -76,25 +76,3 @@ When running MySQL locally, your connection URL typically looks similar to this:
 ```bash file=.env
 DATABASE_URL="mysql://root:randompassword@localhost:3306/mydb"
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/relational-databases-node-mysql"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-node-mysql"
-  arrow
->
-  Using Prisma Migrate
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-planetscale.mdx
index 28bf68dd47..41a98ad7d2 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-planetscale.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -44,7 +44,7 @@ You will also need to set the relation mode type to `prisma` in order to [emulat
 datasource db {
   provider     = "mysql"
   url          = env("DATABASE_URL")
-  //highlight-next-line
+  //add-next-line
   relationMode = "prisma"
 }
 ```
@@ -104,26 +104,3 @@ pscale connect prisma-test branchname --port PORT
 The `--port` flag can be omitted if you are using the default port `3306`.
 
 </details>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/relational-databases-node-planetscale"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-node-planetscale"
-  arrow
->
-  Creating the database schema
-</ButtonLink>
-
-</NavigationLinksContainer>
-
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-postgresql.mdx
index 1817fc0d39..b94ea69560 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-postgresql.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -69,26 +69,4 @@ When running PostgreSQL locally on macOS, your user and password as well as the
 
 ```bash file=.env
 DATABASE_URL="postgresql://janedoe:janedoe@localhost:5432/janedoe?schema=hello-prisma"
-```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/relational-databases-node-postgresql"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-node-postgresql"
-  arrow
->
-  Using Prisma Migrate
-</ButtonLink>
-
-</NavigationLinksContainer>
+```
\ No newline at end of file
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-sqlserver.mdx
index bd38f626c7..694cb32284 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-node-sqlserver.mdx
@@ -20,7 +20,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 ## Connect your database
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "sqlserver"
   url      = env("DATABASE_URL")
@@ -45,24 +45,3 @@ Adjust the connection URL to match your setup - see [Microsoft SQL Server connec
 
 > Make sure TCP/IP connections are enabled via [SQL Server Configuration Manager](https://docs.microsoft.com/en-us/sql/relational-databases/sql-server-configuration-manager) to avoid `No connection could be made because the target machine actively refused it. (os error 10061)`
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/relational-databases-node-sqlserver"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-node-sqlserver"
-  arrow
->
-  Using Prisma Migrate
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx
index 7d56f86be7..71fc1cec0b 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -69,25 +69,3 @@ DATABASE_URL="postgresql://root@localhost:26257?sslmode=disable"
 ```
 
 Your connection string is displayed as part of the welcome text when starting CockroachDB from the command line.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/relational-databases-typescript-cockroachdb"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-typescript-cockroachdb"
-  arrow
->
-  Using Prisma Migrate
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-mysql.mdx
index 6f830685f9..9763de242b 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-mysql.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -76,25 +76,3 @@ When running MySQL locally, your connection URL typically looks similar to this:
 ```bash file=.env
 DATABASE_URL="mysql://root:randompassword@localhost:3306/mydb"
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/relational-databases-typescript-mysql"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-typescript-mysql"
-  arrow
->
-  Using Prisma Migrate
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx
index 485922e869..d2813c717a 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -30,8 +30,9 @@ datasource db {
 
 Note that the default schema created by `prisma init` uses PostgreSQL as the `provider`. For PlanetScale, you need to edit the `datasource` block to use the `mysql` provider instead:
 
-```prisma file=prisma/schema.prisma highlight=2;edit
+```prisma file=prisma/schema.prisma highlight=2;edit showLineNumbers
 datasource db {
+  //edit-next-line
   provider = "mysql"
   url      = env("DATABASE_URL")
 }
@@ -39,10 +40,11 @@ datasource db {
 
 You will also need to set the relation mode type to `prisma` in order to [emulate foreign key constraints](/orm/overview/databases/planetscale#option-1-emulate-relations-in-prisma-client) in the `datasource` block:
 
-```prisma file=schema.prisma highlight=4;add
+```prisma file=schema.prisma highlight=4;add showLineNumbers
 datasource db {
   provider     = "mysql"
   url          = env("DATABASE_URL")
+  //add-next-line
   relationMode = "prisma"
 }
 ```
@@ -102,25 +104,3 @@ pscale connect prisma-test branchname --port PORT
 The `--port` flag can be omitted if you are using the default port `3306`.
 
 </details>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/relational-databases-typescript-planetscale"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-typescript-planetscale"
-  arrow
->
-  Creating the database schema
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx
index 26062f3c99..b8f1ee888f 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx
@@ -19,7 +19,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -68,25 +68,3 @@ When running PostgreSQL locally on macOS, your user and password as well as the
 ```bash file=.env
 DATABASE_URL="postgresql://janedoe:janedoe@localhost:5432/janedoe?schema=hello-prisma"
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/relational-databases-typescript-postgresql"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-typescript-postgresql"
-  arrow
->
-  Using Prisma Migrate
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx
index 00bd27949f..bf7c6a589b 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx
@@ -20,7 +20,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "sqlserver"
   url      = env("DATABASE_URL")
@@ -45,25 +45,3 @@ Adjust the connection URL to match your setup - see [Microsoft SQL Server connec
 
 > Make sure TCP/IP connections are enabled via [SQL Server Configuration Manager](https://docs.microsoft.com/en-us/sql/relational-databases/sql-server-configuration-manager) to avoid `No connection could be made because the target machine actively refused it. (os error 10061)`
 
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/relational-databases-typescript-sqlserver"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-typescript-sqlserver"
-  arrow
->
-  Using Prisma Migrate
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-cockroachdb.mdx
index 210495980c..d1b1da1182 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-cockroachdb.mdx
@@ -20,7 +20,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 In this guide, you'll use [Prisma Migrate](/orm/prisma-migrate) to create the tables in your database. Add the following Prisma data model to your Prisma schema in `prisma/schema.prisma`:
 
-```prisma file=prisma/schema.prisma copy
+```prisma file=prisma/schema.prisma copy showLineNumbers
 model Post {
   id        BigInt   @id @default(sequence())
   createdAt DateTime @default(now())
@@ -64,25 +64,3 @@ This command does two things:
 :::
 
 Great, you now created three tables in your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-node-cockroachdb"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-cockroachdb"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-mysql.mdx
index 484baf1878..aaf8a67e76 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-mysql.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 In this guide, you'll use [Prisma Migrate](/orm/prisma-migrate) to create the tables in your database. Add the following Prisma data model to your Prisma schema in `prisma/schema.prisma`:
 
-```prisma file=prisma/schema.prisma copy
+```prisma file=prisma/schema.prisma copy showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -63,25 +63,3 @@ This command does two things:
 > **Note**: `generate` is called under the hood by default, after running `prisma migrate dev`. If the `prisma-client-js` generator is defined in your schema, this will check if `@prisma/client` is installed and install it if it's missing.
 
 Great, you now created three tables in your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-node-mysql"
-  arrowRight
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-mysql"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-planetscale.mdx
index b6e490d7d4..e360769618 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-planetscale.mdx
@@ -20,7 +20,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 In this guide, you'll use Prisma's [`db push` command](/orm/prisma-migrate/workflows/prototyping-your-schema) to create the tables in your database. Add the following Prisma data model to your Prisma schema in `prisma/schema.prisma`:
 
-```prisma file=prisma/schema.prisma copy
+```prisma file=prisma/schema.prisma copy showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -61,25 +61,3 @@ npx prisma db push
 ```
 
 Great, you now created three tables in your database with Prisma's `db push` command 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-node-planetscale"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-planetscale"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-postgresql.mdx
index d31a36bcc3..fa19622a5d 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-postgresql.mdx
@@ -20,7 +20,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 In this guide, you'll use [Prisma Migrate](/orm/prisma-migrate) to create the tables in your database. Add the following data model to your [Prisma schema](/orm/prisma-schema) in `prisma/schema.prisma`:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -64,25 +64,3 @@ This command does two things:
 :::
 
 Great, you now created three tables in your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-node-postgresql"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-postgresql"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-sqlserver.mdx
index 79231ef6b6..38ebccb4be 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-node-sqlserver.mdx
@@ -20,7 +20,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 In this guide, you'll use [Prisma Migrate](/orm/prisma-migrate) to create the tables in your database. Add the following Prisma data model to your Prisma schema in `prisma/schema.prisma`:
 
-```prisma file=prisma/schema.prisma copy
+```prisma file=prisma/schema.prisma copy showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -62,25 +62,3 @@ This command does two things:
 > **Note**: `generate` is called under the hood by default, after running `prisma migrate dev`. If the `prisma-client-js` generator is defined in your schema, this will check if `@prisma/client` is installed and install it if it's missing.
 
 Great, you now created three tables in your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-node-sqlserver"
-  arrowRight
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-sqlserver"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-cockroachdb.mdx
index 167f0cc667..07106fc469 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-cockroachdb.mdx
@@ -20,7 +20,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 In this guide, you'll use [Prisma Migrate](/orm/prisma-migrate) to create the tables in your database. Add the following Prisma data model to your Prisma schema in `prisma/schema.prisma`:
 
-```prisma file=prisma/schema.prisma copy
+```prisma file=prisma/schema.prisma copy showLineNumbers
 model Post {
   id        BigInt   @id @default(sequence())
   createdAt DateTime @default(now())
@@ -64,25 +64,3 @@ This command does two things:
 :::
 
 Great, you now created three tables in your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-typescript-cockroachdb"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-cockroachdb"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-mysql.mdx
index f35a855f8f..7ccbda5ebf 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-mysql.mdx
@@ -20,7 +20,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 In this guide, you'll use [Prisma Migrate](/orm/prisma-migrate) to create the tables in your database. Add the following Prisma data model to your Prisma schema in `prisma/schema.prisma`:
 
-```prisma file=prisma/schema.prisma copy
+```prisma file=prisma/schema.prisma copy showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -62,25 +62,3 @@ This command does two things:
 > **Note**: `generate` is called under the hood by default, after running `prisma migrate dev`. If the `prisma-client-js` generator is defined in your schema, this will check if `@prisma/client` is installed and install it if it's missing.
 
 Great, you now created three tables in your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-typescript-mysql"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-mysql"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-planetscale.mdx
index 5d7346fbb4..937ab9f84b 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-planetscale.mdx
@@ -20,7 +20,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 In this guide, you'll use Prisma's [`db push` command](/orm/prisma-migrate/workflows/prototyping-your-schema) to create the tables in your database. Add the following Prisma data model to your Prisma schema in `prisma/schema.prisma`:
 
-```prisma file=prisma/schema.prisma copy
+```prisma file=prisma/schema.prisma copy showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -61,25 +61,3 @@ npx prisma db push
 ```
 
 Great, you now created three tables in your database with Prisma's `db push` command 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-typescript-planetscale"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-planetscale"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-postgresql.mdx
index 1cbca4807a..bbf2012726 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-postgresql.mdx
@@ -19,7 +19,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 In this guide, you'll use [Prisma Migrate](/orm/prisma-migrate) to create the tables in your database. Add the following data model to your [Prisma schema](/orm/prisma-schema) in `prisma/schema.prisma`:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -63,25 +63,3 @@ This command does two things:
 :::
 
 Great, you now created three tables in your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-typescript-postgresql"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-postgresql"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-sqlserver.mdx
index 54d0279ca9..24b3a62f89 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/150-using-prisma-migrate-typescript-sqlserver.mdx
@@ -20,7 +20,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/relational-data
 
 In this guide, you'll use [Prisma Migrate](/orm/prisma-migrate) to create the tables in your database. Add the following Prisma data model to your Prisma schema in `prisma/schema.prisma`:
 
-```prisma file=prisma/schema.prisma copy
+```prisma file=prisma/schema.prisma copy showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -62,25 +62,3 @@ This command does two things:
 > **Note**: `generate` is called under the hood by default, after running `prisma migrate dev`. If the `prisma-client-js` generator is defined in your schema, this will check if `@prisma/client` is installed and install it if it's missing.
 
 Great, you now created three tables in your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-typescript-sqlserver"
-  arrowRight
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-sqlserver"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx
index 2e965b2a51..569e44d131 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx
@@ -29,25 +29,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png)
 
 Whenever you update your Prisma schema, you will have to update your database schema using either `prisma migrate dev` or `prisma db push`. This will keep your database schema in sync with your Prisma schema. The commands will also regenerate Prisma Client.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-node-cockroachdb"
-  arrowLeft
->
-  Using Prisma Migrate
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-cockroachdb"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-mysql.mdx
index 42136dbfba..be1955d45c 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-mysql.mdx
@@ -30,24 +30,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 
 Whenever you update your Prisma schema, you will have to update your database schema using either `prisma migrate dev` or `prisma db push`. This will keep your database schema in sync with your Prisma schema. The commands will also regenerate Prisma Client.
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-node-mysql"
-  arrowLeft
->
-  Using Prisma Migrate
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-mysql"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-planetscale.mdx
index 850420a9b0..73cc171ca9 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-planetscale.mdx
@@ -30,25 +30,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png)
 
 Whenever you update your Prisma schema, you will have to update your database schema using either `prisma migrate dev` or `prisma db push`. This will keep your database schema in sync with your Prisma schema. The commands will also regenerate Prisma Client.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-node-planetscale"
-  arrowLeft
->
-  Using Prisma Migrate
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-planetscale"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-postgresql.mdx
index 8b26685183..8d6920284a 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-postgresql.mdx
@@ -30,25 +30,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png)
 
 Whenever you update your Prisma schema, you will have to update your database schema using either `prisma migrate dev` or `prisma db push`. This will keep your database schema in sync with your Prisma schema. The commands will also regenerate Prisma Client.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-node-postgresql"
-  arrowLeft
->
-  Using Prisma Migrate
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-postgresql"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx
index e6b348edcb..0785440c62 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx
@@ -30,25 +30,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png)
 
 Whenever you update your Prisma schema, you will have to update your database schema using either `prisma migrate dev` or `prisma db push`. This will keep your database schema in sync with your Prisma schema. The commands will also regenerate Prisma Client.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-node-sqlserver"
-  arrowLeft
->
-  Using Prisma Migrate
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-sqlserver"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx
index 01295f010c..f606da4a8b 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx
@@ -30,25 +30,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png)
 
 Whenever you update your Prisma schema, you will have to update your database schema using either `prisma migrate dev` or `prisma db push`. This will keep your database schema in sync with your Prisma schema. The commands will also regenerate Prisma Client.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-typescript-cockroachdb"
-  arrowLeft
->
-  Using Prisma Migrate
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-cockroachdb"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx
index 1c606f2648..6865105554 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx
@@ -31,24 +31,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 
 Whenever you update your Prisma schema, you will have to update your database schema using either `prisma migrate dev` or `prisma db push`. This will keep your database schema in sync with your Prisma schema. The commands will also regenerate Prisma Client.
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-typescript-mysql"
-  arrowLeft
->
-  Using Prisma Migrate
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-mysql"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
\ No newline at end of file
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx
index ac1d8b9847..48b7b875fd 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx
@@ -30,25 +30,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png)
 
 Whenever you update your Prisma schema, you will have to update your database schema using either `prisma migrate dev` or `prisma db push`. This will keep your database schema in sync with your Prisma schema. The commands will also regenerate Prisma Client.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-typescript-planetscale"
-  arrowLeft
->
-  Creating the database schema
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-planetscale"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx
index b3022b9a7d..0fc9c187ba 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx
@@ -29,25 +29,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png)
 
 Whenever you update your Prisma schema, you will have to update your database schema using either `prisma migrate dev` or `prisma db push`. This will keep your database schema in sync with your Prisma schema. The commands will also regenerate Prisma Client.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-typescript-postgresql"
-  arrowLeft
->
-  Using Prisma Migrate
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-postgresql"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx
index 4330e3a897..00f38caeca 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx
@@ -30,25 +30,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png)
 
 Whenever you update your Prisma schema, you will have to update your database schema using either `prisma migrate dev` or `prisma db push`. This will keep your database schema in sync with your Prisma schema. The commands will also regenerate Prisma Client.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./using-prisma-migrate-typescript-sqlserver"
-  arrowLeft
->
-  Using Prisma Migrate
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-sqlserver"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx
index e4f21a86f8..02bdd431a9 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx
@@ -22,7 +22,7 @@ Now that you have generated [Prisma Client](/orm/prisma-client), you can start w
 
 Create a new file named `index.js` and add the following code to it:
 
-```js file=index.js copy
+```js file=index.js copy showLineNumbers
 const { PrismaClient } = require('@prisma/client')
 
 const prisma = new PrismaClient()
@@ -52,11 +52,14 @@ Here's a quick overview of the different parts of the code snippet:
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```js file=index.js highlight=2;delete|3,4;add
+```js file=index.js highlight=2;delete|3,4;add showLineNumbers
 async function main() {
+  //delete-next-line
   // ... you will write your Prisma Client queries here
+  //add-start
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
+  //add-end
 }
 ```
 
@@ -78,8 +81,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```js file=index.js highlight=2-21;add copy
+```js file=index.js highlight=2-21;add copy showLineNumbers
 async function main() {
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Alice',
@@ -100,6 +104,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
+  //add-end
 }
 ```
 
@@ -202,25 +207,3 @@ The `Post` record with an `id` of `1` now got updated in the database:
 | `1`    | `"Hello World"` | `null`      | `true`        | `1`          |
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-cockroachdb"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-node-cockroachdb"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-mysql.mdx
index a699ad138d..5f44d6e771 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-mysql.mdx
@@ -22,7 +22,7 @@ Now that you have generated [Prisma Client](/orm/prisma-client), you can start w
 
 Create a new file named `index.js` and add the following code to it:
 
-```js file=index.js copy
+```js file=index.js copy showLineNumbers
 const { PrismaClient } = require('@prisma/client')
 
 const prisma = new PrismaClient()
@@ -56,10 +56,10 @@ Inside the `main` function, add the following query to read all `User` records f
 async function main() {
   //delete-next-line
   // ... you will write your Prisma Client queries here
-  //highlight-start
+  //add-start
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
-  //highlight-end
+  //add-end
 }
 ```
 
@@ -81,8 +81,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```js file=index.js highlight=2-21;add copy
+```js file=index.js highlight=2-21;add copy showLineNumbers
 async function main() {
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Alice',
@@ -103,6 +104,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
+  //add-end
 }
 ```
 
@@ -205,20 +207,3 @@ The `Post` record with an `id` of `1` now got updated in the database:
 | `1`    | `"Hello World"` | `null`      | `true`        | `1`          |
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-mysql"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink color="dark" type="primary" href="./next-steps-node-mysql" arrow>
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-planetscale.mdx
index 35229b1b0a..11b53496c6 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-planetscale.mdx
@@ -22,7 +22,7 @@ Now that you have generated [Prisma Client](/orm/prisma-client), you can start w
 
 Create a new file named `index.js` and add the following code to it:
 
-```js file=index.js copy
+```js file=index.js copy showLineNumbers
 const { PrismaClient } = require('@prisma/client')
 
 const prisma = new PrismaClient()
@@ -52,11 +52,14 @@ Here's a quick overview of the different parts of the code snippet:
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```js file=index.js highlight=2;delete|3,4;add
+```js file=index.js highlight=2;delete|3,4;add showLineNumbers
 async function main() {
+  //delete-next-line
   // ... you will write your Prisma Client queries here
+  //add-start
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
+  //add-end
 }
 ```
 
@@ -78,9 +81,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```js file=index.js highlight=2-21;add copy
+```js file=index.js highlight=2-21;add copy showLineNumbers
 async function main() {
-  //highlight-start
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Alice',
@@ -101,7 +104,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
-  //highlight-end
+  //add-end
 }
 ```
 
@@ -205,25 +208,3 @@ The `Post` record with an `id` of `1` now got updated in the database:
 | `1`    | `"Hello World"` | `null`      | `true`        | `1`          |
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-planetscale"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-node-planetscale"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-postgresql.mdx
index 4d35eec13e..c8ba0068a7 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-postgresql.mdx
@@ -22,7 +22,7 @@ Now that you have generated [Prisma Client](/orm/prisma-client), you can start w
 
 Create a new file named `index.js` and add the following code to it:
 
-```js file=index.js copy
+```js file=index.js copy showLineNumbers
 const { PrismaClient } = require('@prisma/client')
 
 const prisma = new PrismaClient()
@@ -53,11 +53,14 @@ Here's a quick overview of the different parts of the code snippet:
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
 
-```js file=index.js highlight=2;delete|3,4;add
+```js file=index.js highlight=2;delete|3,4;add showLineNumbers
 async function main() {
+  //delete-next-line
   // ... you will write your Prisma Client queries here
+  //add-start
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
+  //add-end
 }
 ```
 
@@ -79,8 +82,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```js file=index.js highlight=2-21;add copy
+```js file=index.js highlight=2-21;add copy showLineNumbers
 async function main() {
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Alice',
@@ -101,6 +105,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
+  //add-end
 }
 ```
 
@@ -203,25 +208,3 @@ The `Post` record with an `id` of `1` now got updated in the database:
 | `1`    | `"Hello World"` | `null`      | `true`        | `1`          |
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-postgresql"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-node-postgresql"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-sqlserver.mdx
index 7ab1e17666..5cbb1829c9 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-node-sqlserver.mdx
@@ -22,7 +22,7 @@ Now that you have generated [Prisma Client](/orm/prisma-client), you can start w
 
 Create a new file named `index.js` and add the following code to it:
 
-```js file=index.js copy
+```js file=index.js copy showLineNumbers
 const { PrismaClient } = require('@prisma/client')
 
 const prisma = new PrismaClient()
@@ -52,11 +52,14 @@ Here's a quick overview of the different parts of the code snippet:
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```js file=index.js highlight=2;delete|3,4;add
+```js file=index.js highlight=2;delete|3,4;add showLineNumbers
 async function main() {
+  //delete-next-line
   // ... you will write your Prisma Client queries here
+  //add-start
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
+  //add-end
 }
 ```
 
@@ -78,8 +81,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```js file=index.js highlight=2-21;add copy
+```js file=index.js highlight=2-21;add copy showLineNumbers
 async function main() {
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Alice',
@@ -100,6 +104,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
+  //add-end
 }
 ```
 
@@ -202,25 +207,3 @@ The `Post` record with an `id` of `1` now got updated in the database:
 | `1`    | `"Hello World"` | `null`      | `true`        | `1`          |
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-sqlserver"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-node-sqlserver"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx
index bee5d29fd2..4962bda8bd 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx
@@ -22,7 +22,7 @@ Now that you have generated [Prisma Client](/orm/prisma-client), you can start w
 
 Create a new file named `index.ts` and add the following code to it:
 
-```js file=index.ts copy
+```js file=index.ts copy showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 const prisma = new PrismaClient()
@@ -52,11 +52,13 @@ Here's a quick overview of the different parts of the code snippet:
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts highlight=3,4;add
+```ts file=index.ts highlight=3,4;add showLineNumbers
 async function main() {
   // ... you will write your Prisma Client queries here
+  //add-start
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
+  //add-end
 }
 ```
 
@@ -78,8 +80,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts highlight=2-21;add copy
+```ts file=index.ts highlight=2-21;add copy showLineNumbers
 async function main() {
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Alice',
@@ -100,6 +103,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
+  //add-end
 }
 ```
 
@@ -181,7 +185,7 @@ The query added new records to the `User` and the `Post` tables:
 
 Before moving on to the next section, you'll "publish" the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts copy
+```ts file=index.ts copy showLineNumbers
 async function main() {
   const post = await prisma.post.update({
     where: { id: 1 },
@@ -218,48 +222,3 @@ The `Post` record with an `id` of `1` now got updated in the database:
 | `1`    | `"Hello World"` | `null`      | `true`        | `1`          |
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
-
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-postgresql"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-node-postgresql"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-cockroachdb"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-cockroachdb"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-mysql.mdx
index 66c53f89cb..4962bda8bd 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-mysql.mdx
@@ -22,7 +22,7 @@ Now that you have generated [Prisma Client](/orm/prisma-client), you can start w
 
 Create a new file named `index.ts` and add the following code to it:
 
-```js file=index.ts copy
+```js file=index.ts copy showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 const prisma = new PrismaClient()
@@ -52,11 +52,13 @@ Here's a quick overview of the different parts of the code snippet:
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts highlight=3,4;add
+```ts file=index.ts highlight=3,4;add showLineNumbers
 async function main() {
   // ... you will write your Prisma Client queries here
+  //add-start
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
+  //add-end
 }
 ```
 
@@ -78,8 +80,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts highlight=2-21;add copy
+```ts file=index.ts highlight=2-21;add copy showLineNumbers
 async function main() {
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Alice',
@@ -100,6 +103,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
+  //add-end
 }
 ```
 
@@ -181,7 +185,7 @@ The query added new records to the `User` and the `Post` tables:
 
 Before moving on to the next section, you'll "publish" the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts copy
+```ts file=index.ts copy showLineNumbers
 async function main() {
   const post = await prisma.post.update({
     where: { id: 1 },
@@ -218,25 +222,3 @@ The `Post` record with an `id` of `1` now got updated in the database:
 | `1`    | `"Hello World"` | `null`      | `true`        | `1`          |
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-mysql"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-mysql"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx
index f96f4360f4..91db459fb9 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx
@@ -22,7 +22,7 @@ Now that you have generated [Prisma Client](/orm/prisma-client), you can start w
 
 Create a new file named `index.ts` and add the following code to it:
 
-```js file=index.ts copy
+```js file=index.ts copy showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 const prisma = new PrismaClient()
@@ -52,11 +52,13 @@ Here's a quick overview of the different parts of the code snippet:
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts highlight=3,4;add
+```ts file=index.ts highlight=3,4;add showLineNumbers
 async function main() {
   // ... you will write your Prisma Client queries here
+  //add-start
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
+  //add-end
 }
 ```
 
@@ -78,8 +80,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts highlight=2-21;add copy
+```ts file=index.ts highlight=2-21;add copy showLineNumbers
 async function main() {
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Alice',
@@ -100,6 +103,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
+  //add-end
 }
 ```
 
@@ -181,7 +185,7 @@ The query added new records to the `User` and the `Post` tables:
 
 Before moving on to the next section, you'll "publish" the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts copy
+```ts file=index.ts copy showLineNumbers
 async function main() {
   const post = await prisma.post.update({
     where: { id: 1 },
@@ -219,47 +223,3 @@ The `Post` record with an `id` of `1` now got updated in the database:
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
 
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-postgresql"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-node-postgresql"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-planetscale"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-planetscale"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx
index 4c9323f97e..611acc2b9f 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx
@@ -21,7 +21,7 @@ Now that you have generated [Prisma Client](/orm/prisma-client), you can start w
 
 Create a new file named `index.ts` and add the following code to it:
 
-```js file=index.ts copy
+```js file=index.ts copy showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 const prisma = new PrismaClient()
@@ -51,11 +51,13 @@ Here's a quick overview of the different parts of the code snippet:
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts highlight=3,4;add
+```ts file=index.ts highlight=3,4;add showLineNumbers
 async function main() {
   // ... you will write your Prisma Client queries here
+  //add-start
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
+  //add-end
 }
 ```
 
@@ -77,8 +79,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts highlight=2-21;add copy
+```ts file=index.ts highlight=2-21;add copy showLineNumbers
 async function main() {
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Alice',
@@ -99,6 +102,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
+  //add-end
 }
 ```
 
@@ -180,7 +184,7 @@ The query added new records to the `User` and the `Post` tables:
 
 Before moving on to the next section, you'll "publish" the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts copy
+```ts file=index.ts copy showLineNumbers
 async function main() {
   const post = await prisma.post.update({
     where: { id: 1 },
@@ -217,25 +221,3 @@ The `Post` record with an `id` of `1` now got updated in the database:
 | `1`    | `"Hello World"` | `null`      | `true`        | `1`          |
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-postgresql"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-postgresql"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx
index 71b516a0c0..d555d63552 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx
@@ -22,7 +22,7 @@ Now that you have generated [Prisma Client](/orm/prisma-client), you can start w
 
 Create a new file named `index.ts` and add the following code to it:
 
-```js file=index.ts copy
+```js file=index.ts copy showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 const prisma = new PrismaClient()
@@ -52,11 +52,13 @@ Here's a quick overview of the different parts of the code snippet:
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts highlight=3,4;add
+```ts file=index.ts highlight=3,4;add showLineNumbers
 async function main() {
   // ... you will write your Prisma Client queries here
+  //add-start
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
+  //add-end
 }
 ```
 
@@ -78,8 +80,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts highlight=2-21;add copy
+```ts file=index.ts highlight=2-21;add copy showLineNumbers
 async function main() {
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Alice',
@@ -100,6 +103,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
+  //add-end
 }
 ```
 
@@ -181,7 +185,7 @@ The query added new records to the `User` and the `Post` tables:
 
 Before moving on to the next section, you'll "publish" the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts copy
+```ts file=index.ts copy showLineNumbers
 async function main() {
   const post = await prisma.post.update({
     where: { id: 1 },
@@ -220,46 +224,3 @@ The `Post` record with an `id` of `1` now got updated in the database:
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
 
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-postgresql"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-node-postgresql"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-sqlserver"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-sqlserver"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
\ No newline at end of file
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-node-mongodb.mdx
index 6d8c291307..c449204456 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-node-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-node-mongodb.mdx
@@ -72,16 +72,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./mongodb/connect-your-database-node-mongodb"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-typescript-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-typescript-mongodb.mdx
index 24d7077696..c5d24af3d7 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-typescript-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb-typescript-mongodb.mdx
@@ -77,16 +77,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./mongodb/connect-your-database-typescript-mongodb"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-node-mongodb.mdx
index 9c2268a7b8..98f4df0438 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-node-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-node-mongodb.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/mongodb/creatin
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -49,25 +49,3 @@ Here's a short explanation of each component:
 - `HOST`: The host where a [`mongod`](https://docs.mongodb.com/manual/reference/program/mongod/#mongodb-binary-bin.mongod) (or [`mongos`](https://docs.mongodb.com/manual/reference/program/mongos/#mongodb-binary-bin.mongos)) instance is running
 - `PORT`: The port where your database server is running (typically `27017` for MongoDB)
 - `DATABASE`: The name of the database
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/mongodb-node-mongodb"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./creating-the-prisma-schema-node-mongodb"
-  arrow
->
-  Creating the Prisma schema
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-typescript-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-typescript-mongodb.mdx
index b9af15f1ac..53233ae2b9 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-typescript-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/100-connect-your-database-typescript-mongodb.mdx
@@ -19,7 +19,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/mongodb/creatin
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -47,25 +47,3 @@ Here's a short explanation of each component:
 - `HOST`: The host where a [`mongod`](https://docs.mongodb.com/manual/reference/program/mongod/#mongodb-binary-bin.mongod) (or [`mongos`](https://docs.mongodb.com/manual/reference/program/mongos/#mongodb-binary-bin.mongos)) instance is running
 - `PORT`: The port where your database server is running (typically `27017` for MongoDB)
 - `DATABASE`: The name of the database
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/start-from-scratch/mongodb-typescript-mongodb"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./creating-the-prisma-schema-typescript-mongodb"
-  arrow
->
-  Creating the Prisma schema
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-node-mongodb.mdx
index 43b36a19fd..3b4b9b0c6d 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-node-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-node-mongodb.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/mongodb/install
 
 Open the `prisma/schema.prisma` file and replace the default contents with the following:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -70,25 +70,3 @@ There are also a number of subtle differences in how the schema is setup when co
 For example, the underlying `ID` field name is always `_id` and must be mapped with `@map("_id")`.
 
 For more information check out the [MongoDB schema reference](/orm/reference/prisma-schema-reference#mongodb-2).
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-node-mongodb"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-mongodb"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-typescript-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-typescript-mongodb.mdx
index c05a7759f9..4a8e7fa41d 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-typescript-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/125-creating-the-prisma-schema-typescript-mongodb.mdx
@@ -19,7 +19,7 @@ pagination_next: getting-started/setup-prisma/start-from-scratch/mongodb/install
 
 Open the `prisma/schema.prisma` file and replace the default contents with the following:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -69,24 +69,3 @@ For example, the underlying `ID` field name is always `_id` and must be mapped w
 
 For more information check out the [MongoDB schema reference](/orm/reference/prisma-schema-reference#mongodb-2).
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-typescript-mongodb"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-mongodb"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-node-mongodb.mdx
index 06a77e1f6c..64712a04ee 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-node-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-node-mongodb.mdx
@@ -29,25 +29,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png)
 
 Whenever you update your Prisma schema, you will need to run the `prisma db push` command to create new indexes and regenerate Prisma Client.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./creating-the-prisma-schema-node-mongodb"
-  arrowLeft
->
-  Creating the Prisma schema
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-mongodb"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx
index 666b47630b..d755165a72 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx
@@ -28,25 +28,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png)
 
 Whenever you update your Prisma schema, you will need to run the `prisma db push` command to create new indexes and regenerate Prisma Client.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./creating-the-prisma-schema-typescript-mongodb"
-  arrowLeft
->
-  Creating the Prisma schema
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-mongodb"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-node-mongodb.mdx
index 3e3acf1775..d4d16b4df3 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-node-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-node-mongodb.mdx
@@ -22,7 +22,7 @@ Now that you have generated Prisma Client, you can start writing queries to read
 
 Create a new file named `index.js` and add the following code to it:
 
-```js file=index.js copy
+```js file=index.js copy showLineNumbers
 const { PrismaClient } = require('@prisma/client')
 
 const prisma = new PrismaClient()
@@ -55,9 +55,12 @@ Inside the `main` function, add the following query to read all `User` records f
 
 ```js file=index.js
 async function main() {
+  //delete-next-line
 -  // ... you will write your Prisma Client queries here
+//add-start
 +  const allUsers = await prisma.user.findMany()
 +  console.log(allUsers)
+//add-end
 }
 ```
 
@@ -79,8 +82,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```js file=index.js highlight=2-21;add copy
+```js file=index.js highlight=2-21;add copy showLineNumbers
 async function main() {
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Rich',
@@ -101,6 +105,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
+  //add-end
 }
 ```
 
@@ -154,7 +159,7 @@ The query added new records to the `User` and the `Post` tables:
 
 Before moving on to the next section, you'll add a couple of comments to the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```js file=index.js copy
+```js file=index.js copy showLineNumbers
 async function main() {
   await prisma.post.update({
     where: {
@@ -214,20 +219,3 @@ You will see the following output:
 ```
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-mongodb"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink color="dark" type="primary" href="./next-steps-node-mongodb" arrow>
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-typescript-mongodb.mdx b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-typescript-mongodb.mdx
index d0e73e19cb..5ccb308ffc 100644
--- a/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-typescript-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/100-start-from-scratch/120-mongodb/250-querying-the-database-typescript-mongodb.mdx
@@ -21,7 +21,7 @@ Now that you have generated Prisma Client, you can start writing queries to read
 
 Create a new file named `index.ts` and add the following code to it:
 
-```js file=index.ts copy
+```js file=index.ts copy showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 const prisma = new PrismaClient()
@@ -51,15 +51,16 @@ Here's a quick overview of the different parts of the code snippet:
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   // ... you will write your Prisma Client queries here
+//add-start
 +  const allUsers = await prisma.user.findMany()
 +  console.log(allUsers)
+//add-end
 }
 ```
 
-
 Now run the code with this command:
 
 ```terminal copy
@@ -78,8 +79,9 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts highlight=2-21;add copy
+```ts file=index.ts highlight=2-21;add copy showLineNumbers
 async function main() {
+  //add-start
   await prisma.user.create({
     data: {
       name: 'Rich',
@@ -100,6 +102,7 @@ async function main() {
     },
   })
   console.dir(allUsers, { depth: null })
+  //add-end
 }
 ```
 
@@ -169,7 +172,7 @@ The query added new records to the `User` and the `Post` tables:
 
 Before moving on to the next section, you'll add a couple of comments to the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts copy
+```ts file=index.ts copy showLineNumbers
 async function main() {
   await prisma.post.update({
     where: {
@@ -229,25 +232,3 @@ You will see the following output:
 ```
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-mongodb"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-mongodb"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-cockroachdb.mdx
index 233c76c3f6..3e4b389631 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-cockroachdb.mdx
@@ -75,16 +75,3 @@ This command does two things:
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
 
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-node-cockroachdb"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-mysql.mdx
index 60c4aa99b4..d6f89f9585 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-mysql.mdx
@@ -76,16 +76,3 @@ This command does two things:
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
 
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-node-mysql"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-planetscale.mdx
index 03e2436057..fdf2981664 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-planetscale.mdx
@@ -74,16 +74,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-node-planetscale"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-postgresql.mdx
index f8c4cc888f..df24231dac 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-postgresql.mdx
@@ -76,15 +76,3 @@ This command does two things:
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
 
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-node-postgresql"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-sqlserver.mdx
index 42895ca978..49936ac223 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-node-sqlserver.mdx
@@ -69,16 +69,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-node-sqlserver"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-cockroachdb.mdx
index 4282c7b1f8..e04c347c20 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-cockroachdb.mdx
@@ -75,17 +75,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-typescript-cockroachdb"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
-
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-mysql.mdx
index b69ff27df1..1372a0ae99 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-mysql.mdx
@@ -74,16 +74,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-typescript-mysql"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-planetscale.mdx
index 1a27f0b2c8..bc4df8e87d 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-planetscale.mdx
@@ -74,16 +74,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-typescript-planetscale"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-postgresql.mdx
index 31d0d05fe0..8262062e74 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-postgresql.mdx
@@ -71,16 +71,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-typescript-postgresql"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-sqlserver.mdx
index dc2a3e7d5f..7e26b4c46c 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases-typescript-sqlserver.mdx
@@ -75,16 +75,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./relational-databases/connect-your-database-typescript-sqlserver"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx
index f2ed2a2b73..2c3c6dadd8 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-cockroachdb.mdx
@@ -22,7 +22,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/relational
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -31,8 +31,9 @@ datasource db {
 
 Note that the default schema created by `prisma init` uses PostgreSQL as the `provider`. For CockroachDB, you need to edit the `datasource` block to use the `cockroachdb` provider instead:
 
-```prisma file=prisma/schema.prisma highlight=2;edit
+```prisma file=prisma/schema.prisma highlight=2;edit showLineNumbers
 datasource db {
+  //edit-next-line
   provider = "cockroachdb"
   url      = env("DATABASE_URL")
 }
@@ -72,24 +73,3 @@ DATABASE_URL="postgresql://root@localhost:26257?sslmode=disable"
 
 Your connection string is displayed as part of the welcome text when starting CockroachDB from the command line.
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/relational-databases-node-cockroachdb"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-node-cockroachdb"
-  arrow
->
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-mysql.mdx
index 380a7aa73c..759249a0a6 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-mysql.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/relational
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -30,8 +30,9 @@ datasource db {
 
 Note that the default schema created by `prisma init` uses PostgreSQL, so you first need to switch the `provider` to `mysql`:
 
-```prisma file=prisma/schema.prisma highlight=2;edit
+```prisma file=prisma/schema.prisma highlight=2;edit showLineNumbers
 datasource db {
+  //edit-next-line
   provider = "mysql"
   url      = env("DATABASE_URL")
 }
@@ -72,19 +73,3 @@ When running MySQL locally, your connection URL typically looks similar to this:
 DATABASE_URL="mysql://root:randompassword@localhost:3306/mydb"
 ```
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/relational-databases-node-mysql"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink color="dark" type="primary" href="./introspection-node-mysql" arrow>
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-planetscale.mdx
index bf31328bd8..9597067c06 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-planetscale.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/relational
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -30,8 +30,9 @@ datasource db {
 
 Note that the default schema created by `prisma init` uses PostgreSQL as the `provider`. For PlanetScale, you need to edit the `datasource` block to use the `mysql` provider instead:
 
-```prisma file=prisma/schema.prisma highlight=2;edit
+```prisma file=prisma/schema.prisma highlight=2;edit showLineNumbers
 datasource db {
+  //edit-next-line
   provider = "mysql"
   url      = env("DATABASE_URL")
 }
@@ -39,10 +40,11 @@ datasource db {
 
 You will also need to [set the relation mode type to `prisma`](/orm/prisma-schema/data-model/relations/relation-mode#emulate-relations-in-prisma-orm-with-the-prisma-relation-mode) in the `datasource` block:
 
-```prisma file=schema.prisma highlight=4;add
+```prisma file=schema.prisma highlight=4;add showLineNumbers
 datasource db {
   provider     = "mysql"
   url          = env("DATABASE_URL")
+  //add-next-line
   relationMode = "prisma"
 }
 ```
@@ -97,24 +99,3 @@ The `--port` flag can be omitted if you are using the default port `3306`.
 
 </details>
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/relational-databases-node-planetscale"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-node-planetscale"
-  arrow
->
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-postgresql.mdx
index ebeaf9a662..54eef0eda3 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-postgresql.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/relational
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -59,25 +59,3 @@ When running PostgreSQL locally on macOS, your user and password as well as the
 ```bash file=.env
 DATABASE_URL="postgresql://janedoe:janedoe@localhost:5432/janedoe?schema=hello-prisma"
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/relational-databases-node-postgresql"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-node-postgresql"
-  arrow
->
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-sqlserver.mdx
index c485325a56..4e4b7ada2b 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-node-sqlserver.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/relational
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "sqlserver"
   url      = env("DATABASE_URL")
@@ -38,24 +38,3 @@ Adjust the connection URL to match your setup - see [Microsoft SQL Server connec
 
 > Make sure TCP/IP connections are enabled via [SQL Server Configuration Manager](https://docs.microsoft.com/en-us/sql/relational-databases/sql-server-configuration-manager) to avoid `No connection could be made because the target machine actively refused it. (os error 10061)`
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/relational-databases-node-sqlserver"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-node-sqlserver"
-  arrow
->
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
\ No newline at end of file
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx
index 2b59c9683d..61888658e6 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-cockroachdb.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/relational
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -30,8 +30,9 @@ datasource db {
 
 Note that the default schema created by `prisma init` uses PostgreSQL as the `provider`. For CockroachDB, you need to edit the `datasource` block to use the `cockroachdb` provider instead:
 
-```prisma file=prisma/schema.prisma highlight=2;edit
+```prisma file=prisma/schema.prisma highlight=2;edit showLineNumbers
 datasource db {
+  //edit-next-line
   provider = "cockroachdb"
   url      = env("DATABASE_URL")
 }
@@ -70,25 +71,3 @@ DATABASE_URL="postgresql://root@localhost:26257?sslmode=disable"
 ```
 
 Your connection string is displayed as part of the welcome text when starting CockroachDB from the command line.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/relational-databases-typescript-cockroachdb"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-cockroachdb"
-  arrow
->
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-mysql.mdx
index ab0ad0b1ac..9078c46b8c 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-mysql.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/relational
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -30,8 +30,9 @@ datasource db {
 
 Note that the default schema created by `prisma init` uses PostgreSQL, so you first need to switch the `provider` to `mysql`:
 
-```prisma file=prisma/schema.prisma highlight=2;edit
+```prisma file=prisma/schema.prisma highlight=2;edit showLineNumbers
 datasource db {
+  //edit-next-line
   provider = "mysql"
   url      = env("DATABASE_URL")
 }
@@ -72,25 +73,3 @@ When running MySQL locally, your connection URL typically looks similar to this:
 DATABASE_URL="mysql://root:randompassword@localhost:3306/mydb"
 ```
 
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/relational-databases-typescript-mysql"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-mysql"
-  arrow
->
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx
index e4bac40306..eb2ff05a1c 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-planetscale.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/relational
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -30,8 +30,9 @@ datasource db {
 
 Note that the default schema created by `prisma init` uses PostgreSQL as the `provider`. For PlanetScale, you need to edit the `datasource` block to use the `mysql` provider instead:
 
-```prisma file=prisma/schema.prisma highlight=2;edit
+```prisma file=prisma/schema.prisma highlight=2;edit showLineNumbers
 datasource db {
+  //edit-next-line
   provider = "mysql"
   url      = env("DATABASE_URL")
 }
@@ -39,10 +40,11 @@ datasource db {
 
 You will also need to [set the relation mode type to `prisma`](/orm/prisma-schema/data-model/relations/relation-mode#emulate-relations-in-prisma-orm-with-the-prisma-relation-mode) in the `datasource` block:
 
-```prisma file=schema.prisma highlight=4;add
+```prisma file=schema.prisma highlight=4;add showLineNumbers
 datasource db {
   provider     = "mysql"
   url          = env("DATABASE_URL")
+  //add-next-line
   relationMode = "prisma"
 }
 ```
@@ -96,25 +98,3 @@ pscale connect prisma-test branchname --port PORT
 The `--port` flag can be omitted if you are using the default port `3306`.
 
 </details>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/relational-databases-typescript-planetscale"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-planetscale"
-  arrow
->
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx
index 2d45ba1ee3..e2d2be1c2d 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-postgresql.mdx
@@ -20,7 +20,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/relational
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -58,25 +58,3 @@ When running PostgreSQL locally on macOS, your user and password as well as the
 ```bash file=.env
 DATABASE_URL="postgresql://janedoe:janedoe@localhost:5432/janedoe?schema=hello-prisma"
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/relational-databases-typescript-postgresql"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-postgresql"
-  arrow
->
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx
index c727af30d6..8ca29dfcf9 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/100-connect-your-database-typescript-sqlserver.mdx
@@ -22,7 +22,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/relational
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "sqlserver"
   url      = env("DATABASE_URL")
@@ -38,25 +38,3 @@ DATABASE_URL="sqlserver://localhost:1433;database=mydb;user=sa;password=r@ndomP@
 Adjust the connection URL to match your setup - see [Microsoft SQL Server connection URL](/orm/overview/databases/sql-server) for more information.
 
 > Make sure TCP/IP connections are enabled via [SQL Server Configuration Manager](https://docs.microsoft.com/en-us/sql/relational-databases/sql-server-configuration-manager) to avoid `No connection could be made because the target machine actively refused it. (os error 10061)`
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/relational-databases-typescript-sqlserver"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-sqlserver"
-  arrow
->
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
\ No newline at end of file
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-cockroachdb.mdx
index 2a493957a1..b7b9c447d9 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-cockroachdb.mdx
@@ -97,7 +97,7 @@ After the introspection is complete, your Prisma schema file was updated:
 
 The data model now looks similar to this:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        BigInt   @id @default(autoincrement())
   title     String   @unique @db.String(255)
@@ -136,7 +136,7 @@ These changes are relevant for the generated Prisma Client API where using lower
 
 Because [relation fields](/orm/prisma-schema/data-model/relations#relation-fields) are _virtual_ (i.e. they _do not directly manifest in the database_), you can manually rename them in your Prisma schema without touching the database:
 
-```prisma file=prisma/schema.prisma highlight=8,15,22,23;edit
+```prisma file=prisma/schema.prisma highlight=8,15,22,23;edit showLineNumbers
 model Post {
   id        BigInt   @id @default(autoincrement())
   title     String   @unique @db.String(255)
@@ -144,6 +144,7 @@ model Post {
   content   String?
   published Boolean  @default(false)
   authorId  BigInt
+  //edit-next-line
   author    User     @relation(fields: [authorId], references: [id], onDelete: NoAction, onUpdate: NoAction)
 }
 
@@ -151,6 +152,7 @@ model Profile {
   id     BigInt  @id @default(autoincrement())
   bio    String?
   userId BigInt  @unique
+  //edit-next-line
   user   User    @relation(fields: [userId], references: [id], onDelete: NoAction, onUpdate: NoAction)
 }
 
@@ -158,8 +160,10 @@ model User {
   id      BigInt   @id @default(autoincrement())
   name    String?  @db.String(255)
   email   String   @unique @db.String(255)
+  //edit-start
   posts   Post[]
   profile Profile?
+  //edit-end
 }
 ```
 
@@ -218,24 +222,3 @@ Learn more about this on the [Configuring your Prisma Client API](/orm/prisma-cl
 
 </details>
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-node-cockroachdb"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-node-cockroachdb"
-  arrow
->
-  Baseline your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-mysql.mdx
index a68db39c3f..70315959b0 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-mysql.mdx
@@ -94,7 +94,7 @@ After the introspection is complete, your Prisma schema file was updated:
 
 The data model now looks similar to this (note that the fields on the models have been reordered for better readability):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -141,7 +141,7 @@ These changes are relevant for the generated Prisma Client API where using lower
 
 Because [relation fields](/orm/prisma-schema/data-model/relations#relation-fields) are _virtual_ (i.e. they _do not directly manifest in the database_), you can manually rename them in your Prisma schema without touching the database:
 
-```prisma file=prisma/schema.prisma highlight=8,17,24,25;edit
+```prisma file=prisma/schema.prisma highlight=8,17,24,25;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -149,6 +149,7 @@ model Post {
   content   String?  @db.Text
   published Boolean  @default(false)
   authorId  Int
+  //edit-next-line
   author    User     @relation(fields: [authorId], references: [id], onDelete: NoAction, onUpdate: NoAction, map: "Post_ibfk_1")
 
   @@index([authorId], map: "authorId")
@@ -158,6 +159,7 @@ model Profile {
   id     Int     @id @default(autoincrement())
   bio    String? @db.Text
   userId Int     @unique(map: "userId")
+  //edit-next-line
   user   User    @relation(fields: [userId], references: [id], onDelete: NoAction, onUpdate: NoAction, map: "Profile_ibfk_1")
 }
 
@@ -165,8 +167,10 @@ model User {
   id      Int      @id @default(autoincrement())
   name    String?  @db.VarChar(255)
   email   String   @unique(map: "email") @db.VarChar(255)
+  //edit-start
   posts   Post[]
   profile Profile?
+  //edit-end
 }
 ```
 
@@ -219,25 +223,3 @@ const user = await prisma.myUser.create({
 ```
 
 Learn more about this on the [Configuring your Prisma Client API](/orm/prisma-client/setup-and-configuration/custom-model-and-field-names) page.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-node-mysql"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-node-mysql"
-  arrow
->
-  Baseline your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-planetscale.mdx
index c71d29d2b8..96821fd322 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-planetscale.mdx
@@ -101,7 +101,7 @@ After the introspection is complete, your Prisma schema file was updated:
 
 The data model now looks similar to this:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -139,7 +139,7 @@ Prisma's data model is a declarative representation of your database schema and
 
 You will then need to add in any missing relations between your data using [relation fields](/orm/prisma-schema/data-model/relations#relation-fields):
 
-```prisma file=prisma/schema.prisma highlight=8,17,27,28;add
+```prisma file=prisma/schema.prisma highlight=8,17,27,28;add showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -147,6 +147,7 @@ model Post {
   title     String   @db.VarChar(255)
   content   String?
   published Boolean  @default(false)
+  //add-next-line
   author    User     @relation(fields: [authorId], references: [id])
   authorId  Int
 
@@ -156,6 +157,7 @@ model Post {
 model Profile {
   id     Int     @id @default(autoincrement())
   bio    String?
+  //add-next-line
   user   User    @relation(fields: [userId], references: [id])
   userId Int     @unique
 
@@ -166,8 +168,10 @@ model User {
   id      Int      @id @default(autoincrement())
   email   String   @unique
   name    String?
+  //add-start
   posts   Post[]
   profile Profile?
+  //add-end
 }
 ```
 
@@ -235,25 +239,3 @@ const user = await prisma.myUser.create({
 Learn more about this on the [Configuring your Prisma Client API](/orm/prisma-client/setup-and-configuration/custom-model-and-field-names) page.
 
 </details>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-node-planetscale"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-planetscale"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-postgresql.mdx
index edbc355727..f41225d3fb 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-postgresql.mdx
@@ -96,7 +96,7 @@ After the introspection is complete, your Prisma schema file was updated:
 
 The data model now looks similar to this (note that the fields on the models have been reordered for better readability):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -135,7 +135,7 @@ These changes are relevant for the generated Prisma Client API where using lower
 
 Because [relation fields](/orm/prisma-schema/data-model/relations#relation-fields) are _virtual_ (i.e. they _do not directly manifest in the database_), you can manually rename them in your Prisma schema without touching the database:
 
-```prisma file=prisma/schema.prisma highlight=8,15,22,23;edit
+```prisma file=prisma/schema.prisma highlight=8,15,22,23;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -143,6 +143,7 @@ model Post {
   content   String?
   published Boolean  @default(false)
   authorId  Int
+  //edit-next-line
   author    User     @relation(fields: [authorId], references: [id], onDelete: NoAction, onUpdate: NoAction)
 }
 
@@ -150,6 +151,7 @@ model Profile {
   id     Int     @id @default(autoincrement())
   bio    String?
   userId Int     @unique
+  //edit-next-line
   user   User    @relation(fields: [userId], references: [id], onDelete: NoAction, onUpdate: NoAction)
 }
 
@@ -157,8 +159,10 @@ model User {
   id      Int      @id @default(autoincrement())
   name    String?  @db.VarChar(255)
   email   String   @unique @db.VarChar(255)
+  //edit-add
   posts   Post[]
   profile Profile?
+  //edit-end
 }
 ```
 
@@ -216,25 +220,3 @@ const user = await prisma.myUser.create({
 Learn more about this on the [Configuring your Prisma Client API](/orm/prisma-client/setup-and-configuration/custom-model-and-field-names) page.
 
 </details>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-node-postgresql"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-node-postgresql"
-  arrow
->
-  Baseline your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-sqlserver.mdx
index 2700562b1b..6ef75594c7 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-node-sqlserver.mdx
@@ -103,7 +103,7 @@ After the introspection is complete, your Prisma schema file was updated:
 
 The data model now looks similar to this (note that the fields on the models have been reordered for better readability):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -142,13 +142,14 @@ These changes are relevant for the generated Prisma Client API where using lower
 
 Because [relation fields](/orm/prisma-schema/data-model/relations#relation-fields) are _virtual_ (i.e. they _do not directly manifest in the database_), you can manually rename them in your Prisma schema without touching the database:
 
-```prisma file=prisma/schema.prisma highlight=7,14,22,23;edit
+```prisma file=prisma/schema.prisma highlight=7,14,22,23;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
   createdAt DateTime @default(now()) @db.Timestamp(6)
   content   String?
   published Boolean  @default(false)
+  //edit-next-line
   author    User     @relation(fields: [authorId], references: [id])
   authorId  Int
 }
@@ -156,6 +157,7 @@ model Post {
 model Profile {
   id     Int     @id @default(autoincrement())
   bio    String?
+  //edit-next-line
   user   User    @relation(fields: [userId], references: [id])
   userId Int     @unique
 }
@@ -164,8 +166,10 @@ model User {
   id      Int      @id @default(autoincrement())
   email   String   @unique @db.VarChar(255)
   name    String?  @db.VarChar(255)
+  //edit-start
   posts   Post[]
   profile Profile?
+  //edit-end
 }
 ```
 
@@ -223,25 +227,3 @@ const user = await prisma.myUser.create({
 Learn more about this on the [Configuring your Prisma Client API](/orm/prisma-client/setup-and-configuration/custom-model-and-field-names) page.
 
 </details>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-node-sqlserver"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-node-sqlserver"
-  arrow
->
-  Baseline your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-cockroachdb.mdx
index d3ecb6b2a7..7827c8c6a9 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-cockroachdb.mdx
@@ -96,7 +96,7 @@ After the introspection is complete, your Prisma schema file was updated:
 
 The data model now looks similar to this:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        BigInt   @id @default(autoincrement())
   title     String   @unique @db.String(255)
@@ -135,7 +135,7 @@ These changes are relevant for the generated Prisma Client API where using lower
 
 Because [relation fields](/orm/prisma-schema/data-model/relations#relation-fields) are _virtual_ (i.e. they _do not directly manifest in the database_), you can manually rename them in your Prisma schema without touching the database:
 
-```prisma file=prisma/schema.prisma highlight=8,15,22,23;edit
+```prisma file=prisma/schema.prisma highlight=8,15,22,23;edit showLineNumbers
 model Post {
   id        BigInt   @id @default(autoincrement())
   title     String   @unique @db.String(255)
@@ -143,6 +143,7 @@ model Post {
   content   String?
   published Boolean  @default(false)
   authorId  BigInt
+  //edit-next-line
   author    User     @relation(fields: [authorId], references: [id], onDelete: NoAction, onUpdate: NoAction)
 }
 
@@ -150,6 +151,7 @@ model Profile {
   id     BigInt  @id @default(autoincrement())
   bio    String?
   userId BigInt  @unique
+  //edit-next-line
   user   User    @relation(fields: [userId], references: [id], onDelete: NoAction, onUpdate: NoAction)
 }
 
@@ -157,8 +159,10 @@ model User {
   id      BigInt   @id @default(autoincrement())
   name    String?  @db.String(255)
   email   String   @unique @db.String(255)
+  //edit-start
   posts   Post[]
   profile Profile?
+  //edit-end
 }
 ```
 
@@ -216,25 +220,3 @@ const user = await prisma.myUser.create({
 Learn more about this on the [Configuring your Prisma Client API](/orm/prisma-client/setup-and-configuration/custom-model-and-field-names) page.
 
 </details>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-typescript-cockroachdb"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-typescript-cockroachdb"
-  arrow
->
-  Baseline your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-mysql.mdx
index 138c1a963b..209275468f 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-mysql.mdx
@@ -94,7 +94,7 @@ After the introspection is complete, your Prisma schema file was updated:
 
 The data model now looks similar to this (note that the fields on the models have been reordered for better readability):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -141,7 +141,7 @@ These changes are relevant for the generated Prisma Client API where using lower
 
 Because [relation fields](/orm/prisma-schema/data-model/relations#relation-fields) are _virtual_ (i.e. they _do not directly manifest in the database_), you can manually rename them in your Prisma schema without touching the database:
 
-```prisma file=prisma/schema.prisma highlight=8,17,24,25;edit
+```prisma file=prisma/schema.prisma highlight=8,17,24,25;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -149,6 +149,7 @@ model Post {
   content   String?  @db.Text
   published Boolean  @default(false)
   authorId  Int
+  //edit-next-line
   author    User     @relation(fields: [authorId], references: [id], onDelete: NoAction, onUpdate: NoAction, map: "Post_ibfk_1")
 
   @@index([authorId], map: "authorId")
@@ -158,6 +159,7 @@ model Profile {
   id     Int     @id @default(autoincrement())
   bio    String? @db.Text
   userId Int     @unique(map: "userId")
+  //edit-next-line
   user   User    @relation(fields: [userId], references: [id], onDelete: NoAction, onUpdate: NoAction, map: "Profile_ibfk_1")
 }
 
@@ -165,8 +167,10 @@ model User {
   id      Int      @id @default(autoincrement())
   name    String?  @db.VarChar(255)
   email   String   @unique(map: "email") @db.VarChar(255)
+  //edit-start
   posts   Post[]
   profile Profile?
+  //edit-end
 }
 ```
 
@@ -219,25 +223,3 @@ const user = await prisma.myUser.create({
 ```
 
 Learn more about this on the [Configuring your Prisma Client API](/orm/prisma-client/setup-and-configuration/custom-model-and-field-names) page.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-typescript-mysql"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-typescript-mysql"
-  arrow
->
-  Baseline your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-planetscale.mdx
index 4fa3fccad1..ce7917ff4e 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-planetscale.mdx
@@ -101,7 +101,7 @@ After the introspection is complete, your Prisma schema file was updated:
 
 The data model now looks similar to this:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -139,7 +139,7 @@ Prisma's data model is a declarative representation of your database schema and
 
 You will then need to add in any missing relations between your data using [relation fields](/orm/prisma-schema/data-model/relations#relation-fields):
 
-```prisma file=prisma/schema.prisma highlight=8,17,27,28;add
+```prisma file=prisma/schema.prisma highlight=8,17,27,28;add showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -147,6 +147,7 @@ model Post {
   title     String   @db.VarChar(255)
   content   String?
   published Boolean  @default(false)
+  //add-next-line
   author    User     @relation(fields: [authorId], references: [id])
   authorId  Int
 
@@ -156,6 +157,7 @@ model Post {
 model Profile {
   id     Int     @id @default(autoincrement())
   bio    String?
+  //add-next-line
   user   User    @relation(fields: [userId], references: [id])
   userId Int     @unique
 
@@ -166,8 +168,10 @@ model User {
   id      Int      @id @default(autoincrement())
   email   String   @unique
   name    String?
+  //add-start
   posts   Post[]
   profile Profile?
+  //add-end
 }
 ```
 
@@ -235,25 +239,3 @@ const user = await prisma.myUser.create({
 Learn more about this on the [Configuring your Prisma Client API](/orm/prisma-client/setup-and-configuration/custom-model-and-field-names) page.
 
 </details>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-typescript-planetscale"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-planetscale"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-postgresql.mdx
index 1f1330c7d4..fa88cadfdc 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-postgresql.mdx
@@ -95,7 +95,7 @@ After the introspection is complete, your Prisma schema file was updated:
 
 The data model now looks similar to this (note that the fields on the models have been reordered for better readability):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -134,7 +134,7 @@ These changes are relevant for the generated Prisma Client API where using lower
 
 Because [relation fields](/orm/prisma-schema/data-model/relations#relation-fields) are _virtual_ (i.e. they _do not directly manifest in the database_), you can manually rename them in your Prisma schema without touching the database:
 
-```prisma file=prisma/schema.prisma highlight=8,15,22,23;edit
+```prisma file=prisma/schema.prisma highlight=8,15,22,23;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -142,6 +142,7 @@ model Post {
   content   String?
   published Boolean  @default(false)
   authorId  Int
+  //edit-next-line
   author    User     @relation(fields: [authorId], references: [id], onDelete: NoAction, onUpdate: NoAction)
 }
 
@@ -149,6 +150,7 @@ model Profile {
   id     Int     @id @default(autoincrement())
   bio    String?
   userId Int     @unique
+  //edit-next-line
   user   User    @relation(fields: [userId], references: [id], onDelete: NoAction, onUpdate: NoAction)
 }
 
@@ -156,8 +158,10 @@ model User {
   id      Int      @id @default(autoincrement())
   name    String?  @db.VarChar(255)
   email   String   @unique @db.VarChar(255)
+  //edit-start
   posts   Post[]
   profile Profile?
+  //edit-end
 }
 ```
 
@@ -215,25 +219,3 @@ const user = await prisma.myUser.create({
 Learn more about this on the [Configuring your Prisma Client API](/orm/prisma-client/setup-and-configuration/custom-model-and-field-names) page.
 
 </details>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-typescript-postgresql"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-typescript-postgresql"
-  arrow
->
-  Baseline your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-sqlserver.mdx
index f2d7978b17..e4a3cb008d 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/150-introspection-typescript-sqlserver.mdx
@@ -103,7 +103,7 @@ After the introspection is complete, your Prisma schema file was updated:
 
 The data model now looks similar to this (note that the fields on the models have been reordered for better readability):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -142,13 +142,14 @@ These changes are relevant for the generated Prisma Client API where using lower
 
 Because [relation fields](/orm/prisma-schema/data-model/relations#relation-fields) are _virtual_ (i.e. they _do not directly manifest in the database_), you can manually rename them in your Prisma schema without touching the database:
 
-```prisma file=prisma/schema.prisma highlight=7,14,22,23;edit
+```prisma file=prisma/schema.prisma highlight=7,14,22,23;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
   createdAt DateTime @default(now()) @db.Timestamp(6)
   content   String?
   published Boolean  @default(false)
+  //edit-next-line
   author    User     @relation(fields: [authorId], references: [id])
   authorId  Int
 }
@@ -156,6 +157,7 @@ model Post {
 model Profile {
   id     Int     @id @default(autoincrement())
   bio    String?
+  //edit-next-line
   user   User    @relation(fields: [userId], references: [id])
   userId Int     @unique
 }
@@ -164,8 +166,10 @@ model User {
   id      Int      @id @default(autoincrement())
   email   String   @unique @db.VarChar(255)
   name    String?  @db.VarChar(255)
+  //edit-start
   posts   Post[]
   profile Profile?
+  //edit-end
 }
 ```
 
@@ -223,25 +227,3 @@ const user = await prisma.myUser.create({
 Learn more about this on the [Configuring your Prisma Client API](/orm/prisma-client/setup-and-configuration/custom-model-and-field-names) page.
 
 </details>
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./connect-your-database-typescript-sqlserver"
-  arrowLeft
->
-  Connect your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-typescript-sqlserver"
-  arrow
->
-  Baseline your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-cockroachdb.mdx
index cd6b3abcec..469b434da2 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-cockroachdb.mdx
@@ -87,25 +87,3 @@ npx prisma migrate resolve --applied 0_init
 The command will mark `0_init` as applied by adding it to the `_prisma_migrations` table.
 
 You now have a baseline for your current database schema. To make further changes to your database schema, you can update your Prisma schema and use `prisma migrate dev` to apply the changes to your database.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-node-cockroachdb"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-cockroachdb"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-mysql.mdx
index 78cf5af3c7..c77a86da0e 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-mysql.mdx
@@ -103,25 +103,3 @@ npx prisma migrate resolve --applied 0_init
 The command will mark `0_init` as applied by adding it to the `_prisma_migrations` table.
 
 You now have a baseline for your current database schema. To make further changes to your database schema, you can update your Prisma schema and use `prisma migrate dev` to apply the changes to your database.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-node-mysql"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-mysql"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-postgresql.mdx
index b877ec6014..d3896f99e6 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-postgresql.mdx
@@ -106,25 +106,3 @@ npx prisma migrate resolve --applied 0_init
 The command will mark `0_init` as applied by adding it to the `_prisma_migrations` table.
 
 You now have a baseline for your current database schema. To make further changes to your database schema, you can update your Prisma schema and use `prisma migrate dev` to apply the changes to your database.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-node-postgresql"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-postgresql"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-sqlserver.mdx
index 1880d78e90..9c420fb013 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-node-sqlserver.mdx
@@ -95,25 +95,3 @@ npx prisma migrate resolve --applied 0_init
 The command will mark `0_init` as applied by adding it to the `_prisma_migrations` table.
 
 You now have a baseline for your current database schema. To make further changes to your database schema, you can update your Prisma schema and use `prisma migrate dev` to apply the changes to your database.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-node-sqlserver"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-sqlserver"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-cockroachdb.mdx
index a7f3054a50..fe1ffc329a 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-cockroachdb.mdx
@@ -76,25 +76,3 @@ CREATE TABLE "Profile" (
   FOREIGN KEY ("userId") REFERENCES "User"(id)
 );
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-cockroachdb"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-cockroachdb"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-mysql.mdx
index 9596922f89..f85a99dc6e 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-mysql.mdx
@@ -104,25 +104,3 @@ npx prisma migrate resolve --applied 0_init
 The command will mark `0_init` as applied by adding it to the `_prisma_migrations` table.
 
 You now have a baseline for your current database schema. To make further changes to your database schema, you can update your Prisma schema and use `prisma migrate dev` to apply the changes to your database.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-mysql"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-mysql"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-postgresql.mdx
index cc34251443..30ebd5b36e 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-postgresql.mdx
@@ -105,25 +105,3 @@ npx prisma migrate resolve --applied 0_init
 The command will mark `0_init` as applied by adding it to the `_prisma_migrations` table.
 
 You now have a baseline for your current database schema. To make further changes to your database schema, you can update your Prisma schema and use `prisma migrate dev` to apply the changes to your database.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-postgresql"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-postgresql"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-sqlserver.mdx
index a0dd6ff651..10a1ad3b95 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/170-baseline-your-database-typescript-sqlserver.mdx
@@ -95,25 +95,3 @@ npx prisma migrate resolve --applied 0_init
 The command will mark `0_init` as applied by adding it to the `_prisma_migrations` table.
 
 You now have a baseline for your current database schema. To make further changes to your database schema, you can update your Prisma schema and use `prisma migrate dev` to apply the changes to your database.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-sqlserver"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-sqlserver"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx
index 82c24ee31b..5278a26d08 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-cockroachdb.mdx
@@ -39,25 +39,3 @@ This command reads your Prisma schema and generates your Prisma Client library:
 The `@prisma/client` node module references a folder named `.prisma/client`, which contains your unique, generated Prisma Client:
 
 ![The .prisma and @prisma folders](/img/getting-started/prisma-client-node-module.png)
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-node-cockroachdb"
-  arrowLeft
->
-  Baseline your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-cockroachdb"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-mysql.mdx
index 68ccc7d952..bb26346072 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-mysql.mdx
@@ -39,25 +39,3 @@ This command reads your Prisma schema and generates your Prisma Client library:
 The `@prisma/client` node module references a folder named `.prisma/client`, which contains your unique, generated Prisma Client:
 
 ![The .prisma and @prisma folders](/img/getting-started/prisma-client-node-module.png)
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-node-mysql"
-  arrowLeft
->
-  Baseline your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-mysql"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-planetscale.mdx
index 121ee41c17..f4373e2e7d 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-planetscale.mdx
@@ -39,25 +39,3 @@ This command reads your Prisma schema and generates your Prisma Client library:
 The `@prisma/client` node module references a folder named `.prisma/client`, which contains your unique, generated Prisma Client:
 
 ![The .prisma and @prisma folders](/img/getting-started/prisma-client-node-module.png)
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-node-planetscale"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-planetscale"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-postgresql.mdx
index d5aa0734be..66c63dc180 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-postgresql.mdx
@@ -39,25 +39,3 @@ This command reads your Prisma schema and generates your Prisma Client library:
 The `@prisma/client` node module references a folder named `.prisma/client`, which contains your unique, generated Prisma Client:
 
 ![The .prisma and @prisma folders](/img/getting-started/prisma-client-node-module.png)
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-node-postgresql"
-  arrowLeft
->
-  Baseline your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-postgresql"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx
index 823cbc6445..a7a2c199af 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-node-sqlserver.mdx
@@ -39,25 +39,3 @@ This command reads your Prisma schema and generates your Prisma Client library:
 The `@prisma/client` node module references a folder named `.prisma/client`, which contains your unique, generated Prisma Client:
 
 ![The .prisma and @prisma folders](/img/getting-started/prisma-client-node-module.png)
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-node-sqlserver"
-  arrowLeft
->
-  Baseline your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-sqlserver"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx
index f32edf80ce..dd042bd4be 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-cockroachdb.mdx
@@ -39,25 +39,3 @@ This command reads your Prisma schema and generates your Prisma Client library:
 The `@prisma/client` node module references a folder named `.prisma/client`, which contains your unique, generated Prisma Client:
 
 ![The .prisma and @prisma folders](/img/getting-started/prisma-client-node-module.png)
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-typescript-cockroachdb"
-  arrowLeft
->
-  Baseline your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-cockroachdb"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx
index d2fb1c3205..750bce1e10 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-mysql.mdx
@@ -39,25 +39,3 @@ This command reads your Prisma schema and generates your Prisma Client library:
 The `@prisma/client` node module references a folder named `.prisma/client`, which contains your unique, generated Prisma Client:
 
 ![The .prisma and @prisma folders](/img/getting-started/prisma-client-node-module.png)
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-typescript-mysql"
-  arrowLeft
->
-  Baseline your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-mysql"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx
index c24085b441..784cc64398 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-planetscale.mdx
@@ -39,25 +39,3 @@ This command reads your Prisma schema and generates your Prisma Client library:
 The `@prisma/client` node module references a folder named `.prisma/client`, which contains your unique, generated Prisma Client:
 
 ![The .prisma and @prisma folders](/img/getting-started/prisma-client-node-module.png)
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-planetscale"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-planetscale"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx
index 67291084cc..6a69d01eb2 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-postgresql.mdx
@@ -38,25 +38,3 @@ This command reads your Prisma schema and generates your Prisma Client library:
 The `@prisma/client` node module references a folder named `.prisma/client`, which contains your unique, generated Prisma Client:
 
 ![The .prisma and @prisma folders](/img/getting-started/prisma-client-node-module.png)
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-typescript-postgresql"
-  arrowLeft
->
-  Baseline your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-postgresql"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx
index cfe36d32d6..26f3ace659 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/200-install-prisma-client-typescript-sqlserver.mdx
@@ -39,25 +39,3 @@ This command reads your Prisma schema and generates your Prisma Client library:
 The `@prisma/client` node module references a folder named `.prisma/client`, which contains your unique, generated Prisma Client:
 
 ![The .prisma and @prisma folders](/img/getting-started/prisma-client-node-module.png)
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./baseline-your-database-typescript-sqlserver"
-  arrowLeft
->
-  Baseline your database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-sqlserver"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx
index ee304dfffc..b4359c92a6 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-cockroachdb.mdx
@@ -125,25 +125,3 @@ Now run the code using the same command as before:
 ```terminal copy
 node index.js
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-cockroachdb"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./evolve-your-schema-node-cockroachdb"
-  arrow
->
-  Evolve your schema
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-mysql.mdx
index 347acc1e1b..fd188aaeb3 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-mysql.mdx
@@ -127,25 +127,3 @@ Now run the code using the same command as before:
 ```terminal copy
 node index.js
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-mysql"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./evolve-your-schema-node-mysql"
-  arrow
->
-  Evolve your schema
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-planetscale.mdx
index c404c19dc9..7fc2523431 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-planetscale.mdx
@@ -139,24 +139,3 @@ Now run the code using the same command as before:
 ```terminal copy
 node index.js
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-planetscale"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-node-planetscale"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-postgresql.mdx
index 4188a3ec2b..b66725fe9e 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-postgresql.mdx
@@ -126,25 +126,3 @@ Now run the code using the same command as before:
 ```terminal copy
 node index.js
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-postgresql"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./evolve-your-schema-node-postgresql"
-  arrow
->
-  Evolve your schema
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-sqlserver.mdx
index 6f0d0783b1..dd75e69f68 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-node-sqlserver.mdx
@@ -134,25 +134,3 @@ async function main() {
   console.log(post)
 }
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-sqlserver"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./evolve-your-schema-node-sqlserver"
-  arrow
->
-  Evolve your schema
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx
index 314b54596b..41f7d44449 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-cockroachdb.mdx
@@ -27,7 +27,7 @@ For the purpose of this guide however, you'll just create a plain Node.js script
 
 Create a new file named `index.ts` and add the following code to it:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 const prisma = new PrismaClient()
@@ -61,7 +61,7 @@ The following examples are all based on the models in the Prisma schema.
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
@@ -88,7 +88,7 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   await prisma.user.create({
     data: {
@@ -125,7 +125,7 @@ npx ts-node index.ts
 
 Before moving on to the next section, you'll "publish" the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   const post = await prisma.post.update({
     where: { title: 'Hello World' },
@@ -141,24 +141,3 @@ Run the code with your current TypeScript setup. If you're using `ts-node`, you
 npx ts-node index.ts
 ```
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-cockroachdb"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./evolve-your-schema-typescript-cockroachdb"
-  arrow
->
-  Evolve your schema
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-mysql.mdx
index 3d92093ffb..3ffa92e88b 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-mysql.mdx
@@ -27,7 +27,7 @@ For the purpose of this guide however, you'll just create a plain Node.js script
 
 Create a new file named `index.ts` and add the following code to it:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 const prisma = new PrismaClient()
@@ -61,7 +61,7 @@ The following examples are all based on the models in the Prisma schema.
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
@@ -88,7 +88,7 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   await prisma.user.create({
     data: {
@@ -125,7 +125,7 @@ npx ts-node index.ts
 
 Before moving on to the next section, you'll "publish" the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   const post = await prisma.post.update({
     where: { id: 1 },
@@ -140,25 +140,3 @@ Run the code with your current TypeScript setup. If you're using `ts-node`, you
 ```terminal copy
 npx ts-node index.ts
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-mysql"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./evolve-your-schema-typescript-mysql"
-  arrow
->
-  Evolve your schema
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx
index 4e76a5ed4e..4b827006fd 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-planetscale.mdx
@@ -27,7 +27,7 @@ For the purpose of this guide however, you'll just create a plain Node.js script
 
 Create a new file named `index.ts` and add the following code to it:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 const prisma = new PrismaClient()
@@ -61,7 +61,7 @@ The following examples are all based on the models in the Prisma schema.
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
@@ -89,7 +89,7 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   await prisma.user.create({
     data: {
@@ -126,7 +126,7 @@ npx ts-node index.ts
 
 Before moving on to the next section, you'll "publish" the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   const post = await prisma.post.update({
     where: { id: 1 },
@@ -141,25 +141,3 @@ Run the code with your current TypeScript setup. If you're using `ts-node`, you
 ```terminal copy
 npx ts-node index.ts
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-planetscale"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-planetscale"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx
index 9ebe6e76ac..678dedb82a 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-postgresql.mdx
@@ -26,7 +26,7 @@ For the purpose of this guide however, you'll just create a plain Node.js script
 
 Create a new file named `index.ts` and add the following code to it:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 const prisma = new PrismaClient()
@@ -60,7 +60,7 @@ The following examples are all based on the models in the Prisma schema.
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
@@ -87,7 +87,7 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   await prisma.user.create({
     data: {
@@ -124,7 +124,7 @@ npx ts-node index.ts
 
 Before moving on to the next section, you'll "publish" the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   const post = await prisma.post.update({
     where: { id: 1 },
@@ -139,25 +139,3 @@ Run the code with your current TypeScript setup. If you're using `ts-node`, you
 ```terminal copy
 npx ts-node index.ts
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-postgresql"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./evolve-your-schema-typescript-postgresql"
-  arrow
->
-  Evolve your schema
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx
index b2d511f105..fd3d714f91 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/250-querying-the-database-typescript-sqlserver.mdx
@@ -27,7 +27,7 @@ For the purpose of this guide however, you'll just create a plain Node.js script
 
 Create a new file named `index.ts` and add the following code to it:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 const prisma = new PrismaClient()
@@ -61,7 +61,7 @@ The following examples are all based on the models in the Prisma schema.
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   const allUsers = await prisma.user.findMany()
   console.log(allUsers)
@@ -88,7 +88,7 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   await prisma.user.create({
     data: {
@@ -125,7 +125,7 @@ npx ts-node index.ts
 
 Before moving on to the next section, you'll "publish" the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   const post = await prisma.post.update({
     where: { id: 1 },
@@ -140,25 +140,3 @@ Run the code with your current TypeScript setup. If you're using `ts-node`, you
 ```terminal copy
 npx ts-node index.ts
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-sqlserver"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./evolve-your-schema-typescript-sqlserver"
-  arrow
->
-  Evolve your schema
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-cockroachdb.mdx
index 63ffecec8b..679a8312cb 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-cockroachdb.mdx
@@ -30,7 +30,7 @@ For the purpose of this guide, we'll make the following changes to the Prisma sc
 
 Once you've made the changes to your schema, your schema should resemble the one below:
 
-```prisma file=prisma/schema.prisma highlight=9,27-31;edit
+```prisma file=prisma/schema.prisma highlight=9,27-31;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -39,6 +39,7 @@ model Post {
   published Boolean  @default(false)
   authorId  Int
   user      User     @relation(fields: [authorId], references: [id])
+  //edit-next-line
   tags      Tag[]
 }
 
@@ -57,11 +58,13 @@ model User {
   profile Profile?
 }
 
+//edit-start
 model Tag {
   id    Int    @id @default(autoincrement())
   name  String
   posts Post[]
 }
+//edit-end
 ```
 
 To apply your Prisma schema changes to your database, use the `prisma migrate dev` CLI command:
@@ -105,25 +108,3 @@ ALTER TABLE "_PostToTag" ADD CONSTRAINT "_PostToTag_A_fkey" FOREIGN KEY ("A") RE
 -- AddForeignKey
 ALTER TABLE "_PostToTag" ADD CONSTRAINT "_PostToTag_B_fkey" FOREIGN KEY ("B") REFERENCES "Tag"("id") ON DELETE CASCADE ON UPDATE CASCADE;
 ```
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-cockroachdb"
-  arrowLeft
->
-  Querying the database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-node-cockroachdb"
-  arrow
->
-  Next steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-mysql.mdx
index 50775eba3b..00b2d97ca6 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-mysql.mdx
@@ -30,7 +30,7 @@ For the purpose of this guide, we'll make the following changes to the Prisma sc
 
 Once you've made the changes to your schema, your schema should resemble the one below:
 
-```prisma file=prisma/schema.prisma highlight=9,27-31;edit
+```prisma file=prisma/schema.prisma highlight=9,27-31;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -39,6 +39,7 @@ model Post {
   published Boolean  @default(false)
   authorId  Int
   user      User     @relation(fields: [authorId], references: [id])
+  //edit-next-line
   tags      Tag[]
 }
 
@@ -57,11 +58,13 @@ model User {
   profile Profile?
 }
 
+//edit-start
 model Tag {
   id    Int    @id @default(autoincrement())
   name  String
   posts Post[]
 }
+//edit-end
 ```
 
 To apply your Prisma schema changes to your database, use the `prisma migrate dev` CLI command:
@@ -107,20 +110,3 @@ ALTER TABLE _PostToTag ADD CONSTRAINT _PostToTag_B_fkey FOREIGN KEY (B) REFERENC
 ```
 
 Congratulations, you just evolved your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-mysql"
-  arrowLeft
->
-  Querying the database
-</ButtonLink>
-
-<ButtonLink color="dark" type="primary" href="./next-steps-node-mysql" arrow>
-  Next steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-postgresql.mdx
index 411a8df224..0efa8fe4f8 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-postgresql.mdx
@@ -107,25 +107,3 @@ ALTER TABLE "_PostToTag" ADD CONSTRAINT "_PostToTag_B_fkey" FOREIGN KEY ("B") RE
 ```
 
 Congratulations, you just evolved your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-postgresql"
-  arrowLeft
->
-  Querying the database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-node-postgresql"
-  arrow
->
-  Next steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-sqlserver.mdx
index c5bd2dc5ff..86fcef8b84 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-node-sqlserver.mdx
@@ -30,7 +30,7 @@ For the purpose of this guide, we'll make the following changes to the Prisma sc
 
 Once you've made the changes to your schema, your schema should resemble the one below:
 
-```prisma file=prisma/schema.prisma highlight=9,27-31;edit
+```prisma file=prisma/schema.prisma highlight=9,27-31;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -39,6 +39,7 @@ model Post {
   published Boolean  @default(false)
   authorId  Int
   user      User     @relation(fields: [authorId], references: [id])
+  //edit-next-line
   tags      Tag[]
 }
 
@@ -57,11 +58,13 @@ model User {
   profile Profile?
 }
 
+//edit-start
 model Tag {
   id    Int    @id @default(autoincrement())
   name  String
   posts Post[]
 }
+//edit-end
 ```
 
 To apply your Prisma schema changes to your database, use the `prisma migrate dev` CLI command:
@@ -107,25 +110,3 @@ ALTER TABLE [dbo].[_PostToTag] ADD CONSTRAINT [_PostToTag_B_fkey] FOREIGN KEY ([
 ```
 
 Congratulations
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-sqlserver"
-  arrowLeft
->
-  Querying the database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-node-sqlserver"
-  arrow
->
-  Next steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-cockroachdb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-cockroachdb.mdx
index 9456260cb6..4296a08275 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-cockroachdb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-cockroachdb.mdx
@@ -30,7 +30,7 @@ For the purpose of this guide, we'll make the following changes to the Prisma sc
 
 Once you've made the changes to your schema, your schema should resemble the one below:
 
-```prisma file=prisma/schema.prisma highlight=9,27-31;edit
+```prisma file=prisma/schema.prisma highlight=9,27-31;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -39,6 +39,7 @@ model Post {
   published Boolean  @default(false)
   authorId  Int
   user      User     @relation(fields: [authorId], references: [id])
+  //edit-next-line
   tags      Tag[]
 }
 
@@ -57,11 +58,13 @@ model User {
   profile Profile?
 }
 
+//edit-start
 model Tag {
   id    Int    @id @default(autoincrement())
   name  String
   posts Post[]
 }
+//edit-end
 ```
 
 To apply your Prisma schema changes to your database, use the `prisma migrate dev` CLI command:
@@ -108,24 +111,3 @@ ALTER TABLE "_PostToTag" ADD CONSTRAINT "_PostToTag_B_fkey" FOREIGN KEY ("B") RE
 
 Congratulations, you just evolved your database with Prisma Migrate 🚀
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-cockroachdb"
-  arrowLeft
->
-  Querying the database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-cockroachdb"
-  arrow
->
-  Next steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-mysql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-mysql.mdx
index 84a7e03ce7..00b2d97ca6 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-mysql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-mysql.mdx
@@ -30,7 +30,7 @@ For the purpose of this guide, we'll make the following changes to the Prisma sc
 
 Once you've made the changes to your schema, your schema should resemble the one below:
 
-```prisma file=prisma/schema.prisma highlight=9,27-31;edit
+```prisma file=prisma/schema.prisma highlight=9,27-31;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -39,6 +39,7 @@ model Post {
   published Boolean  @default(false)
   authorId  Int
   user      User     @relation(fields: [authorId], references: [id])
+  //edit-next-line
   tags      Tag[]
 }
 
@@ -57,11 +58,13 @@ model User {
   profile Profile?
 }
 
+//edit-start
 model Tag {
   id    Int    @id @default(autoincrement())
   name  String
   posts Post[]
 }
+//edit-end
 ```
 
 To apply your Prisma schema changes to your database, use the `prisma migrate dev` CLI command:
@@ -107,25 +110,3 @@ ALTER TABLE _PostToTag ADD CONSTRAINT _PostToTag_B_fkey FOREIGN KEY (B) REFERENC
 ```
 
 Congratulations, you just evolved your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-mysql"
-  arrowLeft
->
-  Querying the database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-mysql"
-  arrow
->
-  Next steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-postgresql.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-postgresql.mdx
index edf01530c3..6a95a6d23e 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-postgresql.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-postgresql.mdx
@@ -29,7 +29,7 @@ For the purpose of this guide, we'll make the following changes to the Prisma sc
 
 Once you've made the changes to your schema, your schema should resemble the one below:
 
-```prisma file=prisma/schema.prisma highlight=9,27-31;edit
+```prisma file=prisma/schema.prisma highlight=9,27-31;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -38,6 +38,7 @@ model Post {
   published Boolean  @default(false)
   authorId  Int
   user      User     @relation(fields: [authorId], references: [id])
+  //edit-next-line
   tags      Tag[]
 }
 
@@ -56,11 +57,13 @@ model User {
   profile Profile?
 }
 
+//edit-start
 model Tag {
   id    Int    @id @default(autoincrement())
   name  String
   posts Post[]
 }
+//edit-end
 ```
 
 To apply your Prisma schema changes to your database, use the `prisma migrate dev` CLI command:
@@ -108,25 +111,3 @@ ALTER TABLE "_PostToTag" ADD CONSTRAINT "_PostToTag_B_fkey" FOREIGN KEY ("B") RE
 
 
 Congratulations, you just evolved your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-postgresql"
-  arrowLeft
->
-  Querying the database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-postgresql"
-  arrow
->
-  Next steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-sqlserver.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-sqlserver.mdx
index 42840697d6..3d51bcafaf 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-sqlserver.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/110-relational-databases/275-evolve-your-schema-typescript-sqlserver.mdx
@@ -30,7 +30,7 @@ For the purpose of this guide, we'll make the following changes to the Prisma sc
 
 Once you've made the changes to your schema, your schema should resemble the one below:
 
-```prisma file=prisma/schema.prisma highlight=9,27-31;edit
+```prisma file=prisma/schema.prisma highlight=9,27-31;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String   @db.VarChar(255)
@@ -39,6 +39,7 @@ model Post {
   published Boolean  @default(false)
   authorId  Int
   user      User     @relation(fields: [authorId], references: [id])
+  //edit-next-line
   tags      Tag[]
 }
 
@@ -57,11 +58,13 @@ model User {
   profile Profile?
 }
 
+//edit-start
 model Tag {
   id    Int    @id @default(autoincrement())
   name  String
   posts Post[]
 }
+//edit-end
 ```
 
 To apply your Prisma schema changes to your database, use the `prisma migrate dev` CLI command:
@@ -78,7 +81,7 @@ This command will:
 
 The following migration will be generated and saved in your `prisma/migrations` folder:
 
-```sql file=prisma/migrations/TIMESTAMP_tags_model.sql
+```sql file=prisma/migrations/TIMESTAMP_tags_model.sql 
  -- CreateTable
 CREATE TABLE [dbo].[Tag] (
     [id] SERIAL NOT NULL,
@@ -107,25 +110,3 @@ ALTER TABLE [dbo].[_PostToTag] ADD CONSTRAINT [_PostToTag_B_fkey] FOREIGN KEY ([
 ```
 
 Congratulations, you just evolved your database with Prisma Migrate 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-sqlserver"
-  arrowLeft
->
-  Querying the database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-sqlserver"
-  arrow
->
-  Next steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-node-mongodb.mdx
index 9f5d41a541..16c076d967 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-node-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-node-mongodb.mdx
@@ -73,16 +73,3 @@ This command does two things:
 
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./mongodb/connect-your-database-node-mongodb"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-typescript-mongodb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-typescript-mongodb.mdx
index f33980c619..9aef7d576f 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-typescript-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb-typescript-mongodb.mdx
@@ -74,16 +74,3 @@ This command does two things:
 - creates a new directory called `prisma` that contains a file called `schema.prisma`, which contains the Prisma schema with your database connection variable and schema models
 - creates the [`.env` file](/orm/more/development-environment/environment-variables/env-files) in the root directory of the project, which is used for defining environment variables (such as your database connection)
 
-
-<NavigationLinksContainer isFirstLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./mongodb/connect-your-database-typescript-mongodb"
-  arrow
->
-  Connect your database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-node-mongodb.mdx
index 3e487ef8ad..f526779fe1 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-node-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-node-mongodb.mdx
@@ -21,7 +21,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/mongodb/in
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -51,25 +51,3 @@ Here's a short explanation of each component:
 - `DATABASE`: The name of the database
 
 > If you see the following error: `Error in connector: SCRAM failure: Authentication failed.`, you can specify the source database for the authentication by [adding](https://github.com/prisma/prisma/discussions/9994#discussioncomment-1562283) `?authSource=admin` to the end of the connection string.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/mongodb-node-mongodb"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-node-mongodb"
-  arrow
->
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-typescript-mongodb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-typescript-mongodb.mdx
index 758425efe7..348771fc99 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-typescript-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/100-connect-your-database-typescript-mongodb.mdx
@@ -19,7 +19,7 @@ pagination_next: getting-started/setup-prisma/add-to-existing-project/mongodb/in
 
 To connect your database, you need to set the `url` field of the `datasource` block in your Prisma schema to your database [connection URL](/orm/reference/connection-urls):
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -50,24 +50,3 @@ Here's a short explanation of each component:
 
 > If you see the following error: `Error in connector: SCRAM failure: Authentication failed.`, you can specify the source database for the authentication by [adding](https://github.com/prisma/prisma/discussions/9994#discussioncomment-1562283) `?authSource=admin` to the end of the connection string.
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/mongodb-typescript-mongodb"
-  arrowLeft
->
-  Installation
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-mongodb"
-  arrow
->
-  Introspection
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-node-mongodb.mdx
index e29de21457..c0149ac14a 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-node-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-node-mongodb.mdx
@@ -50,7 +50,7 @@ npx prisma init
 
 Initializing Prisma ORM will create a `prisma/schema.prisma` file. Edit this file to use MongoDB:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -73,7 +73,7 @@ npx prisma db pull
 
 This command introspects our database and writes the inferred schema into your `prisma/schema.prisma` file:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -99,7 +99,7 @@ model User {
 
 To be able to join data using Prisma Client, you can add the [`@relation`](/orm/reference/prisma-schema-reference#relation) attributes to our models:
 
-```prisma file=prisma/schema.prisma highlight=14;add|20;add
+```prisma file=prisma/schema.prisma highlight=14;add|20;add showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -113,12 +113,14 @@ model Post {
   id     String @id @default(auto()) @map("_id") @db.ObjectId
   title  String
   userId String @db.ObjectId
+  //add-next-line
   user   User   @relation(fields: [userId], references: [id])
 }
 
 model User {
   id    String @id @default(auto()) @map("_id") @db.ObjectId
   email String
+  //add-next-line
   posts Post[]
 }
 ```
@@ -131,24 +133,3 @@ We're actively working on MongoDB introspection. Provide feedback for this featu
 
 And with that, you're ready to generate Prisma Client.
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/mongodb-node-mongodb"
-  arrowLeft
->
-  Connect to your Database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-mongodb"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-typescript-mongodb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-typescript-mongodb.mdx
index 4407f4439b..27932758cf 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-typescript-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/125-introspection-typescript-mongodb.mdx
@@ -49,7 +49,7 @@ npx prisma init
 
 Initializing Prisma ORM will create a `prisma/schema.prisma` file. Edit this file to use MongoDB:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -72,7 +72,7 @@ npx prisma db pull
 
 This command introspects our database and writes the inferred schema into your `prisma/schema.prisma` file:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -98,7 +98,7 @@ model User {
 
 To be able to join data using Prisma Client, you can add the [`@relation`](/orm/reference/prisma-schema-reference#relation) attributes to our models:
 
-```prisma file=prisma/schema.prisma highlight=14;add|20;add
+```prisma file=prisma/schema.prisma highlight=14;add|20;add showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -112,12 +112,14 @@ model Post {
   id     String @id @default(auto()) @map("_id") @db.ObjectId
   title  String
   userId String @db.ObjectId
+  //add-next-line
   user   User   @relation(fields: [userId], references: [id])
 }
 
 model User {
   id    String @id @default(auto()) @map("_id") @db.ObjectId
   email String
+  //add-next-line
   posts Post[]
 }
 ```
@@ -129,25 +131,3 @@ We're actively working on MongoDB introspection. Provide feedback for this featu
 :::
 
 And with that, you're ready to generate Prisma Client.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="/getting-started/setup-prisma/add-to-existing-project/mongodb-typescript-mongodb"
-  arrowLeft
->
-  Connect to your Database
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-mongodb"
-  arrow
->
-  Install Prisma Client
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-node-mongodb.mdx
index 03bbab4bee..01042e9488 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-node-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-node-mongodb.mdx
@@ -30,25 +30,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 
 Whenever you make changes to your Prisma schema in the future, you manually need to invoke `prisma generate` in order to accommodate the changes in your Prisma Client API.
 
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-node-mongodb"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-node-mongodb"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx
index 6c1e9c39c7..eb32fd3794 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/200-install-prisma-client-typescript-mongodb.mdx
@@ -28,25 +28,3 @@ The install command invokes `prisma generate` for you which reads your Prisma sc
 ![Install and generate Prisma Client](/img/getting-started/prisma-client-install-and-generate.png)
 
 Whenever you make changes to your Prisma schema in the future, you manually need to invoke `prisma generate` in order to accommodate the changes in your Prisma Client API.
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./introspection-typescript-mongodb"
-  arrowLeft
->
-  Introspection
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./querying-the-database-typescript-mongodb"
-  arrow
->
-  Querying the database
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-node-mongodb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-node-mongodb.mdx
index ae69e13aa1..699284a996 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-node-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-node-mongodb.mdx
@@ -220,19 +220,3 @@ You will see the following output:
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
 
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-node-mongodb"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink color="dark" type="primary" href="./next-steps-node-mongodb" arrow>
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-typescript-mongodb.mdx b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-typescript-mongodb.mdx
index 93c8adba26..7bb9ade094 100644
--- a/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-typescript-mongodb.mdx
+++ b/content/100-getting-started/02-setup-prisma/200-add-to-existing-project/120-mongodb/250-querying-the-database-typescript-mongodb.mdx
@@ -56,7 +56,7 @@ Here's a quick overview of the different parts of the code snippet:
 
 Inside the `main` function, add the following query to read all `User` records from the database and print the result:
 
-```ts file=index.ts
+```ts file=index.ts showLineNumbers
 async function main() {
   // ... you will write your Prisma Client queries here
 +  const allUsers = await prisma.user.findMany()
@@ -78,7 +78,7 @@ The `findMany` query you used in the previous section only _reads_ data from the
 
 Adjust the `main` function to send a `create` query to the database:
 
-```ts file=index.ts copy
+```ts file=index.ts copy showLineNumbers
 async function main() {
   await prisma.user.create({
     data: {
@@ -136,7 +136,7 @@ The output should look similar to this:
 
 Also note that `allUsers` is _statically typed_ thanks to [Prisma Client's generated types](/orm/prisma-client/type-safety/operating-against-partial-structures-of-model-types). You can observe the type by hovering over the `allUsers` variable in your editor. It should be typed as follows:
 
-```ts no-lines
+```ts no-lines showLineNumbers
 const allUsers: (User & {
   posts: Post[]
 })[]
@@ -174,7 +174,7 @@ The `id` field in the Prisma schema maps to `_id` in the underlying MongoDB data
 
 Before moving on to the next section, you'll add a couple of comments to the `Post` record you just created using an `update` query. Adjust the `main` function as follows:
 
-```ts file=index.ts copy
+```ts file=index.ts copy showLineNumbers
 async function main() {
   await prisma.post.update({
     where: {
@@ -234,25 +234,3 @@ You will see the following output:
 ```
 
 Fantastic, you just wrote new data into your database for the first time using Prisma Client 🚀
-
-<NavigationLinksContainer>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./install-prisma-client-typescript-mongodb"
-  arrowLeft
->
-  Install Prisma Client
-</ButtonLink>
-
-<ButtonLink
-  color="dark"
-  type="primary"
-  href="./next-steps-typescript-mongodb"
-  arrow
->
-  Next Steps
-</ButtonLink>
-
-</NavigationLinksContainer>
diff --git a/content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx b/content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx
index bce26c7719..74c1a6db21 100644
--- a/content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx
+++ b/content/200-orm/050-overview/100-introduction/100-what-is-prisma.mdx
@@ -20,7 +20,7 @@ Prisma ORM is an [open-source](https://github.com/prisma/prisma) next-generation
 
 Prisma Client can be used in _any_ Node.js (supported versions) or TypeScript backend application (including serverless applications and microservices). This can be a [REST API](/orm/overview/prisma-in-your-stack/rest), a [GraphQL API](/orm/overview/prisma-in-your-stack/graphql), a gRPC API, or anything else that needs a database.
 
-<div style={{ textAlign: 'center', margin: '2em auto' }}>
+<div style={{ textAlign: 'center', margin: '2em auto' }} class="videoWrapper">
   <iframe
     width="560"
     height="315"
diff --git a/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx b/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx
index 40489e461e..a8d8d9f958 100644
--- a/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx
+++ b/content/200-orm/050-overview/300-prisma-in-your-stack/04-is-prisma-an-orm.mdx
@@ -135,8 +135,10 @@ export class User {
   @Column({ unique: true })
   email: string
 
+  //highlight-start
   @Column()
   salutation: string
+  //highlight-end
 }
 ```
 
diff --git a/content/200-orm/050-overview/500-databases/200-database-drivers.mdx b/content/200-orm/050-overview/500-databases/200-database-drivers.mdx
index 9faf298826..fee924c691 100644
--- a/content/200-orm/050-overview/500-databases/200-database-drivers.mdx
+++ b/content/200-orm/050-overview/500-databases/200-database-drivers.mdx
@@ -3,6 +3,7 @@ title: 'Database drivers'
 metaTitle: 'Database drivers'
 metaDescription: 'Learn how Prisma connects to your database using the built-in drivers and how you can use Prisma along with other JavaScript database drivers using driver adapters (Preview)'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 ## Default built-in drivers
diff --git a/content/200-orm/050-overview/500-databases/300-postgresql.mdx b/content/200-orm/050-overview/500-databases/300-postgresql.mdx
index 8308a7e932..7d864b4391 100644
--- a/content/200-orm/050-overview/500-databases/300-postgresql.mdx
+++ b/content/200-orm/050-overview/500-databases/300-postgresql.mdx
@@ -17,7 +17,7 @@ By default, the PostgreSQL connector contains a database driver responsible for
 
 To connect to a PostgreSQL database server, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema file](/orm/prisma-schema):
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -270,7 +270,7 @@ The PostgreSQL connector maps the [scalar types](/orm/prisma-schema/data-model/m
 
 [Introspection](/orm/prisma-schema/introspection) adds native database types that are **not yet supported** as [`Unsupported`](/orm/reference/prisma-schema-reference#unsupported) fields:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Device {
   id   Int                   @id @default(autoincrement())
   name String
diff --git a/content/200-orm/050-overview/500-databases/400-mysql.mdx b/content/200-orm/050-overview/500-databases/400-mysql.mdx
index 6f91ed88d7..8f28e423df 100644
--- a/content/200-orm/050-overview/500-databases/400-mysql.mdx
+++ b/content/200-orm/050-overview/500-databases/400-mysql.mdx
@@ -17,7 +17,7 @@ By default, the MySQL connector contains a database driver responsible for conne
 
 To connect to a MySQL database server, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema file](/orm/prisma-schema):
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "mysql"
   url      = env("DATABASE_URL")
@@ -193,7 +193,7 @@ When introspecting a MySQL database, the database types are mapped to Prisma ORM
 
 [Introspection](/orm/prisma-schema/introspection) adds native database types that are **not yet supported** as [`Unsupported`](/orm/reference/prisma-schema-reference#unsupported) fields:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Device {
   id   Int                   @id @default(autoincrement())
   name String
diff --git a/content/200-orm/050-overview/500-databases/500-sqlite.mdx b/content/200-orm/050-overview/500-databases/500-sqlite.mdx
index cc8887a7d8..35f8c90f51 100644
--- a/content/200-orm/050-overview/500-databases/500-sqlite.mdx
+++ b/content/200-orm/050-overview/500-databases/500-sqlite.mdx
@@ -17,7 +17,7 @@ By default, the SQLite connector contains a database driver responsible for conn
 
 To connect to a SQLite database file, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [schema file](/orm/prisma-schema):
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "sqlite"
   url      = "file:./dev.db"
@@ -67,7 +67,7 @@ try migrating the 'int' column type to BIGINT
 
 The connection URL of a SQLite connector points to a file on your file system. For example, the following two paths are equivalent because the `.db` is in the same directory:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "sqlite"
   url      = "file:./dev.db"
@@ -76,7 +76,7 @@ datasource db {
 
 is the same as:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "sqlite"
   url      = "file:dev.db"
@@ -85,7 +85,7 @@ datasource db {
 
 You can also target files from the root or any other place in your file system:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "sqlite"
   url      = "file:/Users/janedoe/dev.db"
diff --git a/content/200-orm/050-overview/500-databases/600-mongodb.mdx b/content/200-orm/050-overview/500-databases/600-mongodb.mdx
index 49378ae0c4..b47fd100a4 100644
--- a/content/200-orm/050-overview/500-databases/600-mongodb.mdx
+++ b/content/200-orm/050-overview/500-databases/600-mongodb.mdx
@@ -67,7 +67,7 @@ These iterative tasks of updating the schema and the database can result in inco
 
 **Scenario**: you need to include a phone number for users, as well as an email. You currently have the following `User` model in your `schema.prisma` file:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model User {
   id    String @id @default(auto()) @map("_id") @db.ObjectId
   email String
@@ -80,10 +80,11 @@ There are a number of strategies you could use for migrating this schema:
 
   In our scenario above, you can add an optional `phoneNumber` field to the `User` model in your Prisma schema:
 
-  ```prisma file=prisma/schema.prisma highlight=4;add
+  ```prisma file=prisma/schema.prisma highlight=4;add showLineNumbers
   model User {
     id          String  @id @default(auto()) @map("_id") @db.ObjectId
     email       String
+    //add-next-line
     phoneNumber String?
   }
   ```
@@ -94,10 +95,11 @@ There are a number of strategies you could use for migrating this schema:
 
   Another option is to add a default value on a required field, for example:
 
-  ```prisma file=prisma/schema.prisma highlight=4;add
+  ```prisma file=prisma/schema.prisma highlight=4;add showLineNumbers
   model User {
     id          String @id @default(auto()) @map("_id") @db.ObjectId
     email       String
+    //add-next-line
     phoneNumber String @default("000-000-0000")
   }
   ```
@@ -127,7 +129,7 @@ As an example, take a MongoDB database with two collections, `User` and `Post`.
 
 On introspection with `db pull`, this is pulled in to the Prisma schema file as follows:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Post {
   id     String @id @default(auto()) @map("_id") @db.ObjectId
   title  String
@@ -142,17 +144,19 @@ model User {
 
 This is missing the relation between the `User` and `Post` models. To fix this, manually add a `user` field to the `Post` model with a `@relation` attribute using `userId` as the `fields` value, linking it to the `User` model, and a `posts` field to the `User` model as the back relation:
 
-```prisma file=prisma/schema.prisma highlight=5;add|11;add
+```prisma file=prisma/schema.prisma highlight=5;add|11;add showLineNumbers
 model Post {
   id     String @id @default(auto()) @map("_id") @db.ObjectId
   title  String
   userId String @db.ObjectId
+  //add-next-line
   user   User   @relation(fields: [userId], references: [id])
 }
 
 model User {
   id    String @id @default(auto()) @map("_id") @db.ObjectId
   email String
+  //add-next-line
   posts Post[]
 }
 ```
@@ -354,7 +358,7 @@ For more information on how to set up and manage a MongoDB database, see the [Pr
 
 To connect to a MongoDB server, configure the [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema file](/orm/prisma-schema):
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -564,7 +568,7 @@ When introspecting a MongoDB database, Prisma ORM uses the relevant [scalar type
 
 [Introspection](/orm/prisma-schema/introspection) adds native database types that are **not yet supported** as [`Unsupported`](/orm/reference/prisma-schema-reference#unsupported) fields:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Example {
   id    String                           @id @default(auto()) @map("_id") @db.ObjectId
   name  String
diff --git a/content/200-orm/050-overview/500-databases/800-sql-server/index.mdx b/content/200-orm/050-overview/500-databases/800-sql-server/index.mdx
index 720b5da105..2bbfd20209 100644
--- a/content/200-orm/050-overview/500-databases/800-sql-server/index.mdx
+++ b/content/200-orm/050-overview/500-databases/800-sql-server/index.mdx
@@ -3,6 +3,7 @@ title: 'Microsoft SQL Server'
 metaTitle: 'Microsoft SQL Server'
 metaDescription: 'This page explains how Prisma can connect to a Microsoft SQL Server database using the Microsoft SQL Server database connector.'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
@@ -15,7 +16,7 @@ The Microsoft SQL Server data source connector connects Prisma ORM to a [Microso
 
 To connect to a Microsoft SQL Server database, you need to configure a [`datasource`](/orm/prisma-schema/overview/data-sources) block in your [Prisma schema file](/orm/prisma-schema):
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "sqlserver"
   url      = env("DATABASE_URL")
@@ -143,7 +144,7 @@ sp_bindefault 'catcat', 'dbo.cats.name';
 
 Using the stored procedure `sp_bindefault`, the default value `catcat` can be used in more than one table. The way Prisma ORM manages default values is per table:
 
-```sql file=default_per_table.sql
+```sql file=default_per_table.sql showLineNumbers
 CREATE TABLE cats (
     id INT IDENTITY PRIMARY KEY,
     name NVARCHAR(1000) CONSTRAINT DF_cat_name DEFAULT 'musti'
@@ -152,7 +153,7 @@ CREATE TABLE cats (
 
 The last example, when introspected, leads to the following model:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model cats {
   id   Int     @id @default(autoincrement())
   name String? @default("musti")
@@ -161,7 +162,7 @@ model cats {
 
 And the first doesn't get the default value introspected:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model cats {
   id   Int     @id @default(autoincrement())
   name String?
diff --git a/content/200-orm/050-overview/500-databases/850-planetscale.mdx b/content/200-orm/050-overview/500-databases/850-planetscale.mdx
index 8d81d063c1..0e11507771 100644
--- a/content/200-orm/050-overview/500-databases/850-planetscale.mdx
+++ b/content/200-orm/050-overview/500-databases/850-planetscale.mdx
@@ -69,7 +69,7 @@ PlanetScale does not allow foreign keys in its database schema. By default, Pris
 
 To enable emulation of relations in Prisma Client, set the `relationMode` field to `"prisma"` in the `datasource` block:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider     = "mysql"
   url          = env("DATABASE_URL")
@@ -89,7 +89,7 @@ If you use relations in your Prisma schema with the default `"foreignKeys"` opti
 
 When [you emulate relations in Prisma Client](#how-to-emulate-relations-in-prisma-client), you need to create your own indexes. As an example of a situation where you would want to add an index, take this schema for a blog with posts and comments:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id       Int       @id @default(autoincrement())
   title    String
@@ -110,7 +110,7 @@ The `postId` field in the `Comment` model refers to the corresponding `id` field
 
 To avoid this, you can define an index on the `postId` field using [Prisma ORM's `@@index` argument](/orm/reference/prisma-schema-reference#index):
 
-```prisma file=schema.prisma highlight=15;add
+```prisma file=schema.prisma highlight=15;add showLineNumbers
 model Post {
   id       Int       @id @default(autoincrement())
   title    String
@@ -125,6 +125,7 @@ model Comment {
   postId  Int
   post    Post   @relation(fields: [postId], references: [id], onDelete: Cascade)
 
+  //add-next-line
   @@index([postId])
 }
 ```
@@ -147,11 +148,12 @@ As an example, let's say you decide to decide to add a new `excerpt` field to th
 
 Next, add the following to your `schema.prisma` file:
 
-```prisma file=schema.prisma highlight=5;edit
+```prisma file=schema.prisma highlight=5;edit showLineNumbers
 model Post {
   id       Int       @id @default(autoincrement())
   title    String
   content  String
+  //edit-next-line
   excerpt  String?
   likes    Int       @default(0)
   comments Comment[]
@@ -181,7 +183,7 @@ For more examples, see PlanetScale's tutorial on [automatic migrations with Pris
 
 After introspecting with `npx prisma db pull`, the schema you get may be missing some relations. For example, the following schema is missing a relation between the `User` and `Post` models:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
@@ -201,12 +203,13 @@ model User {
 
 In this case you need to add the relation in manually:
 
-```prisma file=schema.prisma highlight=6,16;add
+```prisma file=schema.prisma highlight=6,16;add showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   createdAt DateTime @default(now())
   title     String   @db.VarChar(255)
   content   String?
+  //add-next-line
   author    User     @relation(fields: [authorId], references: [id])
   authorId  Int
 
@@ -217,6 +220,7 @@ model User {
   id    Int     @id @default(autoincrement())
   email String  @unique
   name  String?
+  //add-next-line
   posts Post[]
 }
 ```
diff --git a/content/200-orm/050-overview/500-databases/880-supabase.mdx b/content/200-orm/050-overview/500-databases/880-supabase.mdx
index 18fe8b7fb6..8a29604879 100644
--- a/content/200-orm/050-overview/500-databases/880-supabase.mdx
+++ b/content/200-orm/050-overview/500-databases/880-supabase.mdx
@@ -39,20 +39,23 @@ DATABASE_URL="postgres://postgres.[your-supabase-project]:[password]@aws-0-eu-ce
 
 If you would like to use the Prisma CLI in order to perform other actions on your database (e.g. migrations) you will need to add a `DIRECT_URL` environment variable to use in the `datasource.directUrl` property so that the CLI can bypass Supavisor:
 
-```env file=.env highlight=4-5;add
+```env file=.env highlight=4-5;add showLineNumbers
 # Connect to Supabase via connection pooling with Supavisor.
 DATABASE_URL="postgres://postgres.[your-supabase-project]:[password]@aws-0-eu-central-1.pooler.supabase.com:6543/postgres?pgbouncer=true"
 
+//add-start
 # Direct connection to the database. Used for migrations.
 DIRECT_URL="postgres://postgres:[password]@db.[your-supabase-project].supabase.co:5432/postgres"
+//add-end
 ```
 
 You can then update your `schema.prisma` to use the new direct URL:
 
-```prisma file=schema.prisma highlight=4;add
+```prisma file=schema.prisma highlight=4;add showLineNumbers
 datasource db {
   provider  = "postgresql"
   url       = env("DATABASE_URL")
+  //add-next-line
   directUrl = env("DIRECT_URL")
 }
 ```
diff --git a/content/200-orm/050-overview/500-databases/890-neon.mdx b/content/200-orm/050-overview/500-databases/890-neon.mdx
index 50397b191d..616805398c 100644
--- a/content/200-orm/050-overview/500-databases/890-neon.mdx
+++ b/content/200-orm/050-overview/500-databases/890-neon.mdx
@@ -66,20 +66,23 @@ DATABASE_URL=postgres://daniel:<password>@ep-mute-rain-952417-pooler.us-east-2.a
 
 If you would like to use Prisma CLI in order to perform other actions on your database (e.g. for migrations) you will need to add a `DIRECT_URL` environment variable to use in the `directUrl` property of the `datasource` block of your Prisma schema so that the CLI will use a direct connection string (without PgBouncer):
 
-```env file=.env highlight=4-5;add
+```env file=.env highlight=4-5;add showLineNumbers
 # Connect to Neon with PgBouncer.
 DATABASE_URL=postgres://daniel:<password>@ep-mute-rain-952417-pooler.us-east-2.aws.neon.tech/neondb?pgbouncer=true
 
+//add-start
 # Direct connection to the database used by Prisma CLI for e.g. migrations.
 DIRECT_URL="postgres://daniel:<password>@ep-mute-rain-952417.us-east-2.aws.neon.tech/neondb"
+//add-end
 ```
 
 You can then update your `schema.prisma` to use the new direct URL:
 
-```prisma file=schema.prisma highlight=4;add
+```prisma file=schema.prisma highlight=4;add showLineNumbers
 datasource db {
   provider  = "postgresql"
   url       = env("DATABASE_URL")
+  //add-next-line
   directUrl = env("DIRECT_URL")
 }
 ```
diff --git a/content/200-orm/050-overview/500-databases/900-turso.mdx b/content/200-orm/050-overview/500-databases/900-turso.mdx
index af5e0b336c..e06d53d906 100644
--- a/content/200-orm/050-overview/500-databases/900-turso.mdx
+++ b/content/200-orm/050-overview/500-databases/900-turso.mdx
@@ -108,6 +108,7 @@ To get started, enable the `driverAdapters` Preview feature flag:
 ```prisma highlight=3;add
 generator client {
   provider        = "prisma-client-js"
+  //add-next-line
   previewFeatures = ["driverAdapters"]
 }
 
@@ -212,10 +213,12 @@ import express from 'express'
 const app = express()
 
 // ... the rest of your application code
+//add-start
 app.use(async (req, res, next) => {
   await libsql.sync()
   next()
 })
+//add-end
 
 app.listen(3000, () => console.log(`Server ready at http://localhost:3000`))
 ```
diff --git a/content/200-orm/100-prisma-schema/10-overview/index.mdx b/content/200-orm/100-prisma-schema/10-overview/index.mdx
index 812af68eb1..9c237a4df8 100644
--- a/content/200-orm/100-prisma-schema/10-overview/index.mdx
+++ b/content/200-orm/100-prisma-schema/10-overview/index.mdx
@@ -171,6 +171,7 @@ The Prisma CLI outputs the path of the schema file that will be used. The follow
 
 ```no-lines
 Environment variables loaded from .env
+//highlight-next-line
 |Prisma Schema loaded from prisma/schema.prisma
 
 Introspecting based on datasource defined in prisma/schema.prisma …
diff --git a/content/200-orm/100-prisma-schema/20-data-model/10-models.mdx b/content/200-orm/100-prisma-schema/20-data-model/10-models.mdx
index 61813d4797..ca6fa88b53 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/10-models.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/10-models.mdx
@@ -28,7 +28,7 @@ datasource db {
 generator client {
   provider = "prisma-client-js"
 }
-
+//highlight-start
 model User {
   id      Int      @id @default(autoincrement())
   email   String   @unique
@@ -66,12 +66,13 @@ enum Role {
   USER
   ADMIN
 }
+//highlight-end
 ```
 
 </TabItem>
 <TabItem value="MongoDB">
 
-```prisma highlight=10-45;normal
+```prisma highlight=10-45;normal 
 datasource db {
   provider = "mongodb"
   url      = env("DATABASE_URL")
@@ -81,6 +82,7 @@ generator client {
   provider = "prisma-client-js"
 }
 
+//highlight-start
 model User {
   id      String   @id @default(auto()) @map("_id") @db.ObjectId
   email   String   @unique
@@ -117,6 +119,7 @@ model Category {
 
 enum Role {
   USER
+//highlight-end
   ADMIN
 }
 ```
@@ -352,12 +355,15 @@ The following example extends the `Comment` and `Tag` models with several scalar
 
 ```prisma highlight=2-4,8;normal
 model Comment {
+  //highlight-start
   id      Int    @id @default(autoincrement())
   title   String
   content String
+  //highlight-end
 }
 
 model Tag {
+  //highlight-next-line
   name String @id
 }
 ```
@@ -367,12 +373,15 @@ model Tag {
 
 ```prisma highlight=2-4,8;normal
 model Comment {
+  //highlight-start
   id      String @id @default(auto()) @map("_id") @db.ObjectId
   title   String
   content String
+  //highlight-end
 }
 
 model Tag {
+  //highlight-next-line
   name String @id @map("_id")
 }
 ```
@@ -393,12 +402,14 @@ A relation field's type is another model - for example, a post (`Post`) can have
 model Post {
   id       Int       @id @default(autoincrement())
   // Other fields
+  //highlight-next-line
   comments Comment[] // A post can have many comments
 }
 
 model Comment {
   id     Int
   // Other fields
+  //highlight-next-line
   Post   Post? @relation(fields: [postId], references: [id]) // A comment can have one post
   postId Int?
 }
@@ -411,12 +422,14 @@ model Comment {
 model Post {
   id       String    @id @default(auto()) @map("_id") @db.Objectid
   // Other fields
+  //highlight-next-line
   comments Comment[] // A post can have many comments
 }
 
 model Comment {
   id     String  @id @default(auto()) @map("_id") @db.Objectid
   // Other fields
+  //highlight-next-line
   Post   Post?   @relation(fields: [postId], references: [id]) // A comment can have one post
   postId String? @db.ObjectId
 }
@@ -434,6 +447,7 @@ Version [2.17.0](https://github.com/prisma/prisma/releases/tag/2.17.0) and later
 ```prisma highlight=3;normal
 model Post {
   id      Int    @id
+  //highlight-next-line
   title   String @db.VarChar(200)
   content String
 }
@@ -474,8 +488,10 @@ The following example includes a scalar list and a list of related models:
 model Post {
   id       Int       @id @default(autoincrement())
   // Other fields
+  //highlight-start
   comments Comment[] // A list of comments
   keywords String[] // A scalar list
+  //highlight-end
 }
 ```
 
@@ -486,8 +502,10 @@ model Post {
 model Post {
   id       String    @id @default(auto()) @map("_id") @db.ObjectId
   // Other fields
+  //highlight-start
   comments Comment[] // A list of comments
   keywords String[] // A scalar list
+  //highlight-end
 }
 ```
 
@@ -505,6 +523,7 @@ model Post {
 model Comment {
   id      Int     @id @default(autoincrement())
   title   String
+  //highlight-next-line
   content String?
 }
 
@@ -520,6 +539,7 @@ model Tag {
 model Comment {
   id      String  @id @default(auto()) @map("_id") @db.ObjectId
   title   String
+  //highlight-next-line
   content String?
 }
 
@@ -618,6 +638,7 @@ In the following example, the `User` ID is represented by the `id` integer field
 
 ```prisma highlight=2;normal
 model User {
+  //highlight-next-line
   id      Int      @id @default(autoincrement())
   email   String   @unique
   name    String?
@@ -638,6 +659,7 @@ model User {
   email     String  @unique
   isAdmin   Boolean @default(false)
 
+  //highlight-next-line
   @@id([firstName, lastName])
 }
 ```
@@ -653,6 +675,7 @@ model User {
   email     String  @unique
   isAdmin   Boolean @default(false)
 
+  //highlight-next-line
   @@id(name: "fullName", fields: [firstName, lastName])
 }
 ```
@@ -671,6 +694,7 @@ In the following example, users are uniquely identified by a `@unique` field. Be
 
 ```prisma highlight=2;normal
 model User {
+  //highlight-next-line
   email   String   @unique
   name    String?
   role    Role     @default(USER)
@@ -694,6 +718,7 @@ In the following example, the `User` ID is represented by the `id` string field
 
 ```prisma highlight=2;normal
 model User {
+  //highlight-next-line
   id      String   @id @default(auto()) @map("_id") @db.ObjectId
   email   String   @unique
   name    String?
@@ -707,6 +732,7 @@ In the following example, the `User` ID is represented by the `id` string field
 
 ```prisma highlight=2;normal
 model User {
+  //highlight-next-line
   id      String   @id @map("_id")
   email   String   @unique
   name    String?
@@ -733,8 +759,10 @@ You can define default values for scalar fields of your models using the [`@defa
 ```prisma highlight=3,5;normal
 model Post {
   id         Int        @id @default(autoincrement())
+  //highlight-next-line
   createdAt  DateTime   @default(now())
   title      String
+  //highlight-next-line
   published  Boolean    @default(false)
   author     User       @relation(fields: [authorId], references: [id])
   authorId   Int
@@ -823,6 +851,7 @@ model Post {
   authorId   Int
   categories Category[] @relation(references: [id])
 
+  //highlight-next-line
   @@unique([authorId, title])
 }
 ```
@@ -840,6 +869,7 @@ model Post {
   authorId   String     @db.ObjectId
   categories Category[] @relation(references: [id])
 
+  //highlight-next-line
   @@unique([authorId, title])
 }
 ```
@@ -868,6 +898,7 @@ model Post {
   authorId   String     @db.ObjectId
   categories Category[] @relation(references: [id])
 
+  //highlight-next-line
   @@unique(name: "authorTitle", [authorId, title])
 }
 ```
@@ -886,7 +917,7 @@ When using the MongoDB provider in version `3.12.0` and later, you can define a
 
 The following example defines a multi-column unique constraint based on the `email` field of the `User` model and the `number` field of the `Address` composite type which is used in `User.address`:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 type Address {
   street String
   number Int
@@ -903,7 +934,7 @@ model User {
 
 This notation can be chained if there is more than one nested composite type:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 type City {
   name String
 }
@@ -948,7 +979,7 @@ When using the MongoDB provider in version `3.12.0` and later, you can define an
 
 The following example defines a multi-column index based on the `email` field of the `User` model and the `number` field of the `Address` composite type:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 type Address {
   street String
   number Int
@@ -965,7 +996,7 @@ model User {
 
 This notation can be chained if there is more than one nested composite type:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 type City {
   name String
 }
@@ -999,13 +1030,16 @@ model User {
   id    Int     @id @default(autoincrement())
   email String  @unique
   name  String?
+  //highlight-next-line
   role  Role    @default(USER)
 }
 
+//highlight-start
 enum Role {
   USER
   ADMIN
 }
+//highlight-end
 ```
 
 </TabItem>
@@ -1016,13 +1050,16 @@ model User {
   id    String  @id @default(auto()) @map("_id") @db.ObjectId
   email String  @unique
   name  String?
+  //highlight-next-line
   role  Role    @default(USER)
 }
 
+//highlight-start
 enum Role {
   USER
   ADMIN
 }
+//highlight-end
 ```
 
 </TabItem>
@@ -1046,7 +1083,7 @@ Composite types (known as [embedded documents](https://docs.mongodb.com/manual/c
 
 To define a composite type, use the `type` block. As an example, take the following schema:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Product {
   id     String  @id @default(auto()) @map("_id") @db.ObjectId
   name   String
diff --git a/content/200-orm/100-prisma-schema/20-data-model/20-relations/100-one-to-one-relations.mdx b/content/200-orm/100-prisma-schema/20-data-model/20-relations/100-one-to-one-relations.mdx
index 8b449d79e5..5132292af3 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/20-relations/100-one-to-one-relations.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/20-relations/100-one-to-one-relations.mdx
@@ -185,6 +185,7 @@ In a one-to-one relation, the side of the relation _without_ a relation scalar (
 ```prisma highlight=3;normal
 model User {
   id      Int      @id @default(autoincrement())
+  //highlight-next-line
   profile Profile? // No relation scalar - must be optional
 }
 ```
diff --git a/content/200-orm/100-prisma-schema/20-data-model/20-relations/400-self-relations.mdx b/content/200-orm/100-prisma-schema/20-data-model/20-relations/400-self-relations.mdx
index a01909dfac..d13eff7f78 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/20-relations/400-self-relations.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/20-relations/400-self-relations.mdx
@@ -68,6 +68,7 @@ Either side of the relation can be backed by a foreign key. In the previous exam
 model User {
   id          Int     @id @default(autoincrement())
   name        String?
+  //highlight-next-line
   successorId Int?    @unique
   successor   User?   @relation("BlogOwnerHistory", fields: [successorId], references: [id])
   predecessor User?   @relation("BlogOwnerHistory")
@@ -81,6 +82,7 @@ model User {
 model User {
   id          String  @id @default(auto()) @map("_id") @db.ObjectId
   name        String?
+  //highlight-next-line
   successorId String? @unique @db.ObjectId
   successor   User?   @relation("BlogOwnerHistory", fields: [successorId], references: [id])
   predecessor User?   @relation("BlogOwnerHistory")
@@ -100,8 +102,10 @@ model User {
   id            Int     @id @default(autoincrement())
   name          String?
   successor     User?   @relation("BlogOwnerHistory")
+  //highlight-start
   predecessorId Int?    @unique
   predecessor   User?   @relation("BlogOwnerHistory", fields: [predecessorId], references: [id])
+  //highlight-end
 }
 ```
 
@@ -113,8 +117,10 @@ model User {
   id            String  @id @default(auto()) @map("_id") @db.ObjectId
   name          String?
   successor     User?   @relation("BlogOwnerHistory")
+  //highlight-start
   predecessorId String? @unique @db.ObjectId
   predecessor   User?   @relation("BlogOwnerHistory", fields: [predecessorId], references: [id])
+  //highlight-end
 }
 ```
 
diff --git a/content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/100-special-rules-for-referential-actions.mdx b/content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/100-special-rules-for-referential-actions.mdx
index e14fe78723..29d06c758c 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/100-special-rules-for-referential-actions.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/20-relations/410-referential-actions/100-special-rules-for-referential-actions.mdx
@@ -69,7 +69,9 @@ Since the default referential action for `onUpdate` in the above relation would
 ```prisma highlight=3;delete|4;add
 model Employee {
   id        Int        @id @default(autoincrement())
+  //delete-next-line
   manager   Employee   @relation(name: "management", fields: [managerId], references: [id])
+  //add-next-line
   manager   Employee   @relation(name: "management", fields: [managerId], references: [id], onDelete: NoAction, onUpdate: NoAction)
   managees  Employee[] @relation(name: "management")
   managerId Int
@@ -128,7 +130,9 @@ As the relation fields are required, the default referential action for `onDelet
 ```prisma highlight=3;delete|4;add
 model Chicken {
   id        Int   @id @default(autoincrement())
+  //delete-next-line
   egg       Egg   @relation(fields: [eggId], references: [id])
+  //add-next-line
   egg       Egg   @relation(fields: [eggId], references: [id], onUpdate: NoAction)
   eggId     Int
   predators Fox[]
@@ -140,7 +144,9 @@ or
 ```prisma highlight=3;delete|4;add
 model Egg {
   id         Int       @id @default(autoincrement())
+  //delete-next-line
   predator   Fox       @relation(fields: [predatorId], references: [id])
+  //add-next-line
   predator   Fox       @relation(fields: [predatorId], references: [id], onUpdate: NoAction)
   predatorId Int
   parents    Chicken[]
@@ -152,7 +158,9 @@ or
 ```prisma highlight=3;delete|4;add
 model Fox {
   id        Int     @id @default(autoincrement())
+  //delete-next-line
   meal      Chicken @relation(fields: [mealId], references: [id])
+  //add-next-line
   meal      Chicken @relation(fields: [mealId], references: [id], onUpdate: NoAction)
   mealId    Int
   foodStore Egg[]
@@ -209,7 +217,9 @@ model Comment {
   id          Int  @id @default(autoincrement())
   writtenById Int
   postId      Int
+  //delete-next-line
   writtenBy   User @relation(fields: [writtenById], references: [id])
+  //add-next-line
   writtenBy   User @relation(fields: [writtenById], references: [id], onUpdate: NoAction)
   post        Post @relation(fields: [postId], references: [id])
 }
@@ -223,7 +233,9 @@ model Comment {
   writtenById Int
   postId      Int
   writtenBy   User @relation(fields: [writtenById], references: [id])
+  //delete-next-line
   post        Post @relation(fields: [postId], references: [id])
+  //add-next-line
   post        Post @relation(fields: [postId], references: [id], onUpdate: NoAction)
 }
 ```
@@ -234,7 +246,9 @@ or
 model Post {
   id       Int       @id @default(autoincrement())
   authorId Int
+  //delete-next-line
   author   User      @relation(fields: [authorId], references: [id])
+  //add-next-line
   author   User      @relation(fields: [authorId], references: [id], onUpdate: NoAction)
   comments Comment[]
 }
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 bac4d23680..2e22396732 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
@@ -23,7 +23,7 @@ From version 2.26.0, you can define referential actions on the relation fields i
 
 In the following example, adding `onDelete: Cascade` to the `author` field on the `Post` model means that deleting the `User` record will also delete all related `Post` records.
 
-```prisma file=schema.prisma highlight=4;normal
+```prisma file=schema.prisma highlight=4;normal showLineNumbers
 model Post {
   id       Int    @id @default(autoincrement())
   title    String
@@ -72,7 +72,7 @@ Referential actions are defined in the [`@relation`](/orm/reference/prisma-schem
 
 The following model defines a one-to-many relation between `User` and `Post` and a many-to-many relation between `Post` and `Tag`, with explicitly defined referential actions:
 
-```prisma file=schema.prisma highlight=10,16-17;normal
+```prisma file=schema.prisma highlight=10,16-17;normal showLineNumbers
 model User {
   id    Int    @id @default(autoincrement())
   posts Post[]
@@ -129,6 +129,7 @@ For example, in the following schema all `Post` records must be connected to a `
 model Post {
   id       Int    @id @default(autoincrement())
   title    String
+  //highlight-next-line
   author   User   @relation(fields: [authorId], references: [id])
   authorId Int
 }
@@ -196,10 +197,11 @@ For this reason, when you set `postgres` as the database provider in the (defaul
 
 #### Example usage
 
-```prisma file=schema.prisma highlight=4;add
+```prisma file=schema.prisma highlight=4;add showLineNumbers
 model Post {
   id       Int    @id @default(autoincrement())
   title    String
+  //add-next-line
   author   User   @relation(fields: [authorId], references: [id], onDelete: Cascade, onUpdate: Cascade)
   authorId Int
 }
@@ -235,10 +237,11 @@ If a `User` record is deleted, then their posts are deleted too. If the user's `
 
 #### Example usage
 
-```prisma file=schema.prisma highlight=4;add
+```prisma file=schema.prisma highlight=4;add showLineNumbers
 model Post {
   id       Int    @id @default(autoincrement())
   title    String
+  //add-next-line
   author   User   @relation(fields: [authorId], references: [id], onDelete: Restrict, onUpdate: Restrict)
   authorId Int
 }
@@ -277,10 +280,11 @@ If you are [managing relations in Prisma Client](/orm/prisma-schema/data-model/r
 
 #### Example usage
 
-```prisma file=schema.prisma highlight=4;add
+```prisma file=schema.prisma highlight=4;add showLineNumbers
 model Post {
   id       Int    @id @default(autoincrement())
   title    String
+  //add-next-line
   author   User   @relation(fields: [authorId], references: [id], onDelete: NoAction, onUpdate: NoAction)
   authorId Int
 }
@@ -303,10 +307,11 @@ model User {
 
 `SetNull` will only work on optional relations. On required relations, a runtime error will be thrown since the scalar fields cannot be null.
 
-```prisma file=schema.prisma highlight=4;add
+```prisma file=schema.prisma highlight=4;add showLineNumbers
 model Post {
   id       Int    @id @default(autoincrement())
   title    String
+  //add-next-line
   author   User?  @relation(fields: [authorId], references: [id], onDelete: SetNull, onUpdate: SetNull)
   authorId Int?
 }
@@ -331,12 +336,14 @@ When changing a `User`'s `id`, the `authorId` will be set to `NULL` for all its
 
 These require setting a default for the relation scalar field with [`@default`](/orm/reference/prisma-schema-reference#default). If no defaults are provided for any of the scalar fields, a runtime error will be thrown.
 
-```prisma file=schema.prisma highlight=4,5;add
+```prisma file=schema.prisma highlight=4,5;add showLineNumbers
 model Post {
   id             Int     @id @default(autoincrement())
   title          String
+  //add-start
   authorUsername String? @default("anonymous")
   author         User?   @relation(fields: [authorUsername], references: [username], onDelete: SetDefault, onUpdate: SetDefault)
+  //add-end
 }
 
 model User {
@@ -391,10 +398,11 @@ The following example would result in a cascading delete, if the `User` is delet
 
 #### A blog schema example
 
-```prisma highlight=4;add
+```prisma highlight=4;add showLineNumbers
 model Post {
   id       Int    @id @default(autoincrement())
   title    String
+  //add-next-line
   author   User   @relation(fields: [authorId], references: [id], onDelete: Cascade)
   authorId Int
 }
@@ -436,7 +444,7 @@ The following example uses the below blog schema with a one-to-many relationship
 
 This means that if a user has a post, that user (and their posts) **cannot** be deleted.
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id       Int    @id @default(autoincrement())
   title    String
diff --git a/content/200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdx b/content/200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdx
index dd67587d1f..8d45cb4483 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/20-relations/420-relation-mode.mdx
@@ -9,16 +9,19 @@ tocDepth: 3
 
 In Prisma schema, relations between records are defined with the [`@relation`](/orm/reference/prisma-schema-reference#relation) attribute. For example, in the following schema there is a one-to-many relation between the `User` and `Post` models:
 
-```prisma file=schema.prisma highlight=4,5,10;normal
+```prisma file=schema.prisma highlight=4,5,10;normal showLineNumbers
 model Post {
   id       Int    @id @default(autoincrement())
   title    String
+  //highlight-start
   author   User   @relation(fields: [authorId], references: [id], onDelete: Cascade, onUpdate: Cascade)
   authorId Int
+  //highlight-end
 }
 
 model User {
   id    Int    @id @default(autoincrement())
+  //highlight-next-line
   posts Post[]
 }
 ```
@@ -75,10 +78,11 @@ Some databases, such as MongoDB or [PlanetScale](/orm/overview/databases/planets
 
 To set the relation mode, add the `relationMode` field in the `datasource` block:
 
-```prisma file=schema.prisma highlight=4,9;add
+```prisma file=schema.prisma highlight=4,9;add showLineNumbers
 datasource db {
   provider     = "mysql"
   url          = env("DATABASE_URL")
+  //add-next-line
   relationMode = "prisma"
 }
 ```
@@ -199,7 +203,7 @@ The `prisma` relation mode does not use foreign keys, so no indexes are created
 
 If you do not add the index manually, queries might require full table scans. This can be slow, and also expensive on database providers that bill per accessed row. To help avoid this, Prisma ORM warns you when your schema contains fields that are used in a `@relation` that does not have an index defined. For example, take the following schema with a relation between the `User` and `Post` models:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider     = "mysql"
   url          = env("DATABASE_URL")
@@ -226,12 +230,13 @@ With `relationMode = "prisma"`, no foreign keys are used, so relation fields wil
 
 To fix this, add an index to your `Post` model:
 
-```prisma file=schema.prisma highlight=6;add
+```prisma file=schema.prisma highlight=6;add showLineNumbers
 model Post {
   id     Int  @id
   userId Int
   user   User @relation(fields: [userId], references: [id])
 
+  //add-next-line
   @@index([userId])
 }
 ```
diff --git a/content/200-orm/100-prisma-schema/20-data-model/20-relations/500-troubleshooting-relations.mdx b/content/200-orm/100-prisma-schema/20-data-model/20-relations/500-troubleshooting-relations.mdx
index 4a1e53d403..acb644a34d 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/20-relations/500-troubleshooting-relations.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/20-relations/500-troubleshooting-relations.mdx
@@ -19,8 +19,10 @@ In the following implicit many-to-many self-relation, the lexicographic order of
 model Animal {
   id        Int      @id @default(autoincrement())
   name      String
+  //highlight-start
   a_eats    Animal[] @relation(name: "FoodChain")
   b_eatenBy Animal[] @relation(name: "FoodChain")
+  //highlight-end
 }
 ```
 
@@ -79,8 +81,10 @@ Now change the order of the relation fields:
 model Animal {
   id        Int      @id @default(autoincrement())
   name      String
+  //highlight-start
   b_eats    Animal[] @relation(name: "FoodChain")
   a_eatenBy Animal[] @relation(name: "FoodChain")
+  //highlight-end
 }
 ```
 
@@ -181,7 +185,9 @@ This is because the relation model forms a 1-to-many relationship with the other
 model Post {
   id             Int              @id @default(autoincrement())
   title          String
+  //delete-next-line
   categories     Category[]
+  //add-next-line
   postCategories PostCategories[]
 }
 
@@ -197,7 +203,9 @@ model PostCategories {
 model Category {
   id             Int              @id @default(autoincrement())
   name           String
+  //delete-next-line
   posts          Post[]
+  //add-next-line
   postCategories PostCategories[]
 }
 ```
@@ -232,14 +240,18 @@ The following example is the correct way to define an implicit many-to-many rela
 model Post {
   id         Int        @id @default(autoincrement())
   title      String
+  //delete-next-line
   categories Category[] @relation("Category")
+  //add-next-line
   categories Category[]
 }
 
 model Category {
   id    Int    @id @default(autoincrement())
   name  String
+  //delete-next-line
   posts Post[] @relation("Post")
+  //add-next-line
   posts Post[]
 }
 ```
diff --git a/content/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdx b/content/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdx
index fa4a0cc1d8..6e8661e724 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/20-relations/index.mdx
@@ -19,13 +19,16 @@ The following Prisma schema defines a one-to-many relation between the `User` an
 ```prisma highlight=3,8,9;normal
 model User {
   id    Int    @id @default(autoincrement())
+  //highlight-next-line
   posts Post[]
 }
 
 model Post {
   id       Int  @id @default(autoincrement())
+  //highlight-start
   author   User @relation(fields: [authorId], references: [id])
   authorId Int // relation scalar field  (used in the `@relation` attribute above)
+  //highlight-end
 }
 ```
 
@@ -35,13 +38,16 @@ model Post {
 ```prisma highlight=3,8,9;normal
 model User {
   id    String @id @default(auto()) @map("_id") @db.ObjectId
+  //highlight-next-line
   posts Post[]
 }
 
 model Post {
   id       String @id @default(auto()) @map("_id") @db.ObjectId
+  //highlight-start
   author   User   @relation(fields: [authorId], references: [id])
   authorId String @db.ObjectId // relation scalar field  (used in the `@relation` attribute above)
+  //highlight-end
 }
 ```
 
@@ -125,12 +131,14 @@ If your model's ID is an `ObjectId` (represented by a `String` field), you must
 ```prisma highlight=3,9;normal
 model User {
   id    String @id @default(auto()) @map("_id") @db.ObjectId
+  //highlight-next-line
   posts Post[]
 }
 
 model Post {
   id       String @id @default(auto()) @map("_id") @db.ObjectId
   author   User   @relation(fields: [authorId], references: [id])
+  //highlight-next-line
   authorId String @db.ObjectId // relation scalar field  (used in the `@relation` attribute above)
 }
 ```
diff --git a/content/200-orm/100-prisma-schema/20-data-model/30-indexes.mdx b/content/200-orm/100-prisma-schema/20-data-model/30-indexes.mdx
index 832b7ac92f..6af9ed95b3 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/30-indexes.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/30-indexes.mdx
@@ -52,7 +52,7 @@ The `length` argument is available on the `@id`, `@@id`, `@unique`, `@@unique` a
 
 As an example, the following data model declares an `id` field with a maximum length of 3000 characters:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Id {
   id String @id @db.VarChar(3000)
 }
@@ -68,7 +68,7 @@ CREATE TABLE `Id` (
 
 The `length` argument allows you to specify that only a subpart of the `id` value represents the primary key. In the example below, the first 100 characters are used:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Id {
   id String @id(length: 100) @db.VarChar(3000)
 }
@@ -80,7 +80,7 @@ Introspection will fetch these limits where they are present in your existing da
 
 The `length` argument can also be used on compound primary keys, using the `@@id` attribute, as in the example below:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model CompoundId {
   id_1 String @db.VarChar(3000)
   id_2 String @db.VarChar(3000)
@@ -108,7 +108,7 @@ CREATE TABLE `Unique` (
 
 is now introspected as
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Unique {
   unique Int @unique(sort: Desc)
 }
@@ -116,7 +116,7 @@ model Unique {
 
 The `sort` argument can also be used on compound indexes:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model CompoundUnique {
   unique_1 Int
   unique_2 Int
@@ -129,7 +129,7 @@ model CompoundUnique {
 
 The following example demonstrates the use of the `sort` and `length` arguments to configure indexes and constraints for a `Post` model:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   title      String   @db.VarChar(300)
   abstract   String   @db.VarChar(3000)
@@ -152,7 +152,7 @@ The `Hash` type will store the index data in a format that is much faster to sea
 
 As an example, the following model adds an index with a `type` of `Hash` to the `value` field:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Example {
   id    Int @id
   value Int
@@ -186,7 +186,7 @@ Indexes using a function (such as `to_tsvector`) to determine the indexed value
 
 As an example, the following model adds a `Gin` index to the `value` field, with `JsonbPathOps` as the class of operators allowed to use the index:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Example {
   id    Int  @id
   value Json
@@ -235,7 +235,7 @@ The GiST index type is used for implementing indexing schemes for user-defined t
 
 As an example, the following model adds a `Gist` index to the `value` field with `InetOps` as the operators that will be using the index:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Example {
   id    Int    @id
   value String @db.Inet
@@ -280,7 +280,7 @@ As with GiST, SP-GiST is important as a building block for user-defined types, a
 As an example, the following model adds a `SpGist` index to the `value` field with `TextOps` as the operators using the index:
 
 <!-- prettier-ignore-start -->
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Example {
   id    Int    @id
   value String
@@ -326,7 +326,7 @@ The BRIN index type is useful if you have lots of data that does not change afte
 
 As an example, the following model adds a `Brin` index to the `value` field with `Int4BloomOps` as the operators that will be using the index:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Example {
   id    Int @id
   value Int
@@ -420,7 +420,7 @@ The `clustered` argument is available to configure (non)clustered indexes in SQL
 
 As an example, the following model configures the `@id` to be non-clustered (instead of the clustered default):
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Example {
   id    Int @id(clustered: false)
   value Int
@@ -480,7 +480,7 @@ For now we do not enable the full text search commands in Prisma Client for Mong
 
 To enable the `fullTextIndex` preview feature, add the `fullTextIndex` feature flag to the `generator` block of the `schema.prisma` file:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 generator client {
   provider        = "prisma-client-js"
   previewFeatures = ["fullTextIndex"]
@@ -491,7 +491,7 @@ generator client {
 
 The following example demonstrates adding a `@@fulltext` index to the `title` and `content` fields of a `Post` model:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id      Int    @id
   title   String @db.VarChar(255)
@@ -503,7 +503,7 @@ model Post {
 
 On MongoDB, you can use the `@@fulltext` index attribute (via the `fullTextIndex` preview feature) with the `sort` argument to add fields to your full-text index in ascending or descending order. The following example adds a `@@fulltext` index to the `title` and `content` fields of the `Post` model, and sorts the `title` field in descending order:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 generator js {
   provider        = "prisma-client-js"
   previewFeatures = ["fullTextIndex"]
diff --git a/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx b/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx
index 33d58b143f..a7eeb70dbc 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/40-views.mdx
@@ -30,9 +30,10 @@ The `views` preview feature allows you to represent views in your Prisma schema
 
 Support for views is currently in an early preview. To enable the `views` preview feature, add the `views` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema file:
 
-```prisma file=schema.prisma highlight=3;add
+```prisma file=schema.prisma highlight=3;add showLineNumbers
 generator client {
   provider        = "prisma-client-js"
+  //add-next-line
   previewFeatures = ["views"]
 }
 ```
@@ -199,10 +200,12 @@ The fields of the `UserInfo` example view can be defined as follows:
 <!-- prettier-ignore -->
 ```prisma highlight=2-5;normal
 view UserInfo {
+  //highlight-start
   id    Int    @unique
   email String
   name  String
   bio   String
+  //highlight-end
 }
 ```
 
@@ -212,10 +215,12 @@ view UserInfo {
 <!-- prettier-ignore -->
 ```prisma highlight=2-5;normal
 view UserInfo {
+  //highlight-start
   id    String @id @default(auto()) @map("_id") @db.ObjectId
   email String
   name  String
   bio   String
+  //highlight-end
 }
 ```
 
@@ -276,15 +281,20 @@ In order to make this `view` block valid you will need to:
 
 <!-- prettier-ignore -->
 ```prisma highlight=4;add|1,3,8,9;delete
+//delete-next-line
 /// The underlying view does not contain a valid unique identifier and can therefore currently not be handled by Prisma Client.
 view UserInfo {
+  //delete-next-line
   id    Int?
+  //add-next-line
   id    Int    @unique
   email String?
   name  String?
   bio   String?
+  //delete-start
   
   @@ignore
+  //delete-end
 }
 ```
 
diff --git a/content/200-orm/100-prisma-schema/20-data-model/50-database-mapping.mdx b/content/200-orm/100-prisma-schema/20-data-model/50-database-mapping.mdx
index 9d50f95674..65f8d67638 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/50-database-mapping.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/50-database-mapping.mdx
@@ -38,6 +38,7 @@ However, you can still choose `Comment` as the name of the model (e.g. to follow
 model Comment {
   // Fields
 
+  //highlight-next-line
   @@map("comments")
 }
 ```
@@ -50,9 +51,11 @@ You can also [`@map`](/orm/reference/prisma-schema-reference#map) a column/field
 
 ```prisma highlight=2-4;normal
 model Comment {
+  //highlight-start
   content String @map("comment_text")
   email   String @map("commenter_email")
   type    Enum   @map("comment_type")
+  //highlight-end
 
   @@map("comments")
 }
@@ -67,8 +70,10 @@ You can also `@map` an enum value, or `@@map` an enum:
 ```prisma highlight=3,5;normal
 enum Type {
   Blog,
+  //highlight-next-line
   Twitter @map("comment_twitter")
 
+  //highlight-next-line
   @@map("comment_source_enum")
 }
 ```
@@ -119,17 +124,21 @@ The following schema defines three constraints (`@id`, `@unique`, and `@relation
 
 ```prisma highlight=2,8,11,13;normal
 model User {
+  //highlight-next-line
   id    Int    @id @default(autoincrement())
   name  String @unique
   posts Post[]
 }
 
 model Post {
+  //highlight-next-line
   id         Int    @id @default(autoincrement())
   title      String
   authorName String @default("Anonymous")
+  //highlight-next-line
   author     User?  @relation(fields: [authorName], references: [name])
 
+  //highlight-next-line
   @@index([title, authorName])
 }
 ```
@@ -154,17 +163,21 @@ The following example adds custom names to one `@id` and the `@@index`:
 
 ```prisma highlight=2,13;normal
 model User {
+  //highlight-next-line
   id    Int    @id(map: "Custom_Primary_Key_Constraint_Name") @default(autoincrement())
   name  String @unique
   posts Post[]
 }
 
 model Post {
+  //highlight-next-line
   id         Int    @id @default(autoincrement())
   title      String
   authorName String @default("Anonymous")
+  //highlight-next-line
   author     User?  @relation(fields: [authorName], references: [name])
 
+  //highlight-next-line
   @@index([title, authorName], map: "My_Custom_Index_Name")
 }
 ```
@@ -211,6 +224,7 @@ Specifying `@@id([firstName, lastName], name: "fullName")` will change the Prism
 ```ts highlight=3;edit
 const user = await prisma.user.findUnique({
   where: {
+    //edit-next-line
     fullName: {
       firstName: 'Paul',
       lastName: 'Panther',
diff --git a/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx b/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx
index 907df66ba1..51258dcec4 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/60-multi-schema.mdx
@@ -30,9 +30,10 @@ This guide explains how to:
 
 Multi-schema support is currently in preview. To enable the `multiSchema` preview feature, add the `multiSchema` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema file:
 
-```prisma file=schema.prisma highlight=3;add
+```prisma file=schema.prisma highlight=3;add showLineNumbers
 generator client {
   provider        = "prisma-client-js"
+  //add-next-line
   previewFeatures = ["multiSchema"]
 }
 
@@ -46,7 +47,7 @@ datasource db {
 
 To use multiple database schemas in your Prisma schema file, add the names of your database schemas to an array in the `schemas` field, in the `datasource` block. The following example adds a `"base"` and a `"transactional"` schema:
 
-```prisma file=schema.prisma highlight=9;add
+```prisma file=schema.prisma highlight=9;add showLineNumbers
 generator client {
   provider        = "prisma-client-js"
   previewFeatures = ["multiSchema"]
@@ -55,6 +56,7 @@ generator client {
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
+  //add-next-line
   schemas  = ["base", "transactional"]
 }
 ```
@@ -63,11 +65,12 @@ You do not need to change your connection string. The `schema` value of your con
 
 To designate that a model or enum belongs to a specific database schema, add the `@@schema` attribute with the name of the database schema as a parameter. In the following example, the `User` model is part of the `"base"` schema, and the `Order` model and `Size` enum are part of the `"transactional"` schema:
 
-```prisma file=schema.prisma highlight=5,13;add
+```prisma file=schema.prisma highlight=5,13;add showLineNumbers
 model User {
   id     Int     @id
   orders Order[]
 
+  //add-next-line
   @@schema("base")
 }
 
@@ -76,6 +79,7 @@ model Order {
   user    User @relation(fields: [id], references: [id])
   user_id Int
 
+  //add-next-line
   @@schema("transactional")
 }
 
@@ -94,7 +98,7 @@ If you have tables with the same name in different database schemas, you will ne
 
 For example, consider a situation where the `config` table in the `base` database schema has the same name as the `config` table in the `users` database schema. To avoid name conflicts, give the models in your Prisma schema unique names (`BaseConfig` and `UserConfig`) and use the `@@map` attribute to map each model to the corresponding table name:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model BaseConfig {
   id Int @id
 
@@ -116,15 +120,17 @@ You can use Prisma Migrate or `db push` to apply changes to a Prisma schema with
 
 As an example, add a `Profile` model to the `base` schema of the blog post model above:
 
-```prisma file=schema.prisma highlight=4,9-16;add
+```prisma file=schema.prisma highlight=4,9-16;add showLineNumbers
 model User {
   id      Int      @id
   orders  Order[]
+  //add-next-line
   profile Profile?
 
   @@schema("base")
 }
 
+//add-start
 model Profile {
   id     Int    @id @default(autoincrement())
   bio    String
@@ -133,6 +139,7 @@ model Profile {
 
   @@schema("base")
 }
+//add-end
 
 model Order {
   id      Int  @id
diff --git a/content/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdx b/content/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdx
index 49094a1c99..dd8b1b3ee9 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/70-unsupported-database-features.mdx
@@ -53,15 +53,17 @@ To use a PostgreSQL extension, you must first install it on the file system of y
 
 In Prisma ORM versions 4.5.0 and later, you can then activate the extension by declaring it in your Prisma schema with the [`postgresqlExtensions` preview feature](/orm/prisma-schema/postgresql-extensions):
 
-```prisma file=schema.prisma highlight=3,9;add
+```prisma file=schema.prisma highlight=3,9;add showLineNumbers
 generator client {
   provider        = "prisma-client-js"
+  //add-next-line
   previewFeatures = ["postgresqlExtensions"]
 }
 
 datasource db {
   provider   = "postgresql"
   url        = env("DATABASE_URL")
+  //add-next-line
   extensions = [pgcrypto]
 }
 ```
@@ -88,6 +90,7 @@ Some database types of relational databases, such as `polygon` or `geometry`, do
 ```prisma highlight=3;normal
 model Star {
   id       Int                    @id @default(autoincrement())
+  //highlight-next-line
   position Unsupported("circle")? @default(dbgenerated("'<(10,4),11>'::circle"))
 }
 ```
diff --git a/content/200-orm/100-prisma-schema/20-data-model/80-table-inheritance.mdx b/content/200-orm/100-prisma-schema/20-data-model/80-table-inheritance.mdx
index 32170bbb82..01b16e206b 100644
--- a/content/200-orm/100-prisma-schema/20-data-model/80-table-inheritance.mdx
+++ b/content/200-orm/100-prisma-schema/20-data-model/80-table-inheritance.mdx
@@ -41,7 +41,7 @@ For example, if both the `Video` and `Article` models from above should have a s
 
 In a simple Prisma schema, this would look as follows. Note that we're adding a `User` model as well to illustrate how this can work with relations:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Video {
   id       Int    @id
   url      String @unique
diff --git a/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx b/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx
index c41ccb1c05..066c3df837 100644
--- a/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx
+++ b/content/200-orm/100-prisma-schema/80-postgresql-extensions.mdx
@@ -36,9 +36,10 @@ Prisma's `postgresqlExtensions` preview feature allows you to represent PostgreS
 
 Representing PostgreSQL extensions in your Prisma schema is currently a preview feature. To enable the `postgresqlExtensions` preview feature, you will need to add the `postgresqlExtensions` feature flag to the `previewFeatures` field of the `generator` block in your Prisma schema file:
 
-```prisma file=schema.prisma highlight=3;add
+```prisma file=schema.prisma highlight=3;add showLineNumbers
 generator client {
   provider        = "prisma-client-js"
+  //add-next-line
   previewFeatures = ["postgresqlExtensions"]
 }
 
@@ -52,7 +53,7 @@ datasource db {
 
 To represent PostgreSQL extensions in your Prisma schema, add the `extensions` field to the `datasource` block of your `schema.prisma` file with an array of the extensions that you require. For example, the following schema lists the `hstore`, `pg_trgm` and `postgis` extensions:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider   = "postgresql"
   url        = env("DATABASE_URL")
@@ -70,7 +71,7 @@ In the example above, the `hstore` extension uses the `myHstoreSchema` schema, a
 
 The `map` argument is useful when the PostgreSQL extension that you want to activate has a name that is not a valid identifier in the Prisma schema. For example, the `uuid-ossp` PostgreSQL extension name is an invalid identifier because it contains a hyphen. In the following example, the extension is mapped to the valid name `uuidOssp` in the Prisma schema:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider   = "postgresql"
   url        = env("DATABASE_URL")
diff --git a/content/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdx b/content/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdx
index 813ccca7cc..68e8e5d859 100644
--- a/content/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdx
+++ b/content/200-orm/200-prisma-client/000-setup-and-configuration/005-introduction.mdx
@@ -45,7 +45,7 @@ The setup instructions [below](#set-up) provide a high-level overview of the ste
 
 In order to set up Prisma Client, you need a [Prisma schema file](/orm/prisma-schema) with your database connection, the Prisma Client generator, and at least one model:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   url      = env("DATABASE_URL")
   provider = "postgresql"
diff --git a/content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx b/content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx
index d816ef9be8..14fdf08f93 100644
--- a/content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx
+++ b/content/200-orm/200-prisma-client/000-setup-and-configuration/050-databases-connections/index.mdx
@@ -302,20 +302,23 @@ Connection poolers like [Prisma Accelerate](/accelerate) and PgBouncer prevent y
 
 If you would like to use the Prisma CLI in order to perform other actions on your database ,e.g. migrations and introspection, you will need to add an environment variable that provides a direct connection to your database in the `datasource.directUrl` property in your Prisma schema:
 
-```env file=.env highlight=4,5;add
+```env file=.env highlight=4,5;add showLineNumbers
 # Connection URL to your database using PgBouncer.
 DATABASE_URL="postgres://root:password@127.0.0.1:54321/postgres?pgbouncer=true"
 
+//add-start
 # Direct connection URL to the database used for migrations
 DIRECT_URL="postgres://root:password@127.0.0.1:5432/postgres"
+//add-end
 ```
 
 You can then update your `schema.prisma` to use the new direct URL:
 
-```prisma file=schema.prisma highlight=4;add
+```prisma file=schema.prisma highlight=4;add showLineNumbers
 datasource db {
   provider  = "postgresql"
   url       = env("DATABASE_URL")
+  //add-next-line
   directUrl = env("DIRECT_URL")
 }
 ```
diff --git a/content/200-orm/200-prisma-client/000-setup-and-configuration/100-custom-model-and-field-names.mdx b/content/200-orm/200-prisma-client/000-setup-and-configuration/100-custom-model-and-field-names.mdx
index 7f3b73bcdc..5de4f7200d 100644
--- a/content/200-orm/200-prisma-client/000-setup-and-configuration/100-custom-model-and-field-names.mdx
+++ b/content/200-orm/200-prisma-client/000-setup-and-configuration/100-custom-model-and-field-names.mdx
@@ -298,8 +298,10 @@ model Post {
 
 model User {
   id             Int    @id @default(autoincrement())
+  //edit-start
   writtenPosts   Post[] @relation("Post_authorToUser")
   favoritedPosts Post[] @relation("Post_favoritedByToUser")
+  //edit-end
 }
 ```
 
diff --git a/content/200-orm/200-prisma-client/100-queries/030-crud.mdx b/content/200-orm/200-prisma-client/100-queries/030-crud.mdx
index baa8c581ce..c268dc64e5 100644
--- a/content/200-orm/200-prisma-client/100-queries/030-crud.mdx
+++ b/content/200-orm/200-prisma-client/100-queries/030-crud.mdx
@@ -3,6 +3,7 @@ title: 'CRUD'
 metaTitle: 'CRUD (Reference)'
 metaDescription: 'How to perform CRUD with Prisma Client.'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
@@ -789,10 +790,14 @@ To resolve this error, you can:
   ```prisma highlight=3,4;add|5,6;delete
   model Post {
     id       Int   @id @default(autoincrement())
+    //add-start
     author   User? @relation(fields: [authorId], references: [id])
     authorId Int?
+    //add-end
+    //delete-start
     author   User  @relation(fields: [authorId], references: [id])
     authorId Int
+    //delete-end
   }
   ```
 
diff --git a/content/200-orm/200-prisma-client/100-queries/037-relation-queries.mdx b/content/200-orm/200-prisma-client/100-queries/037-relation-queries.mdx
index 70ae70525c..535ff06a8f 100644
--- a/content/200-orm/200-prisma-client/100-queries/037-relation-queries.mdx
+++ b/content/200-orm/200-prisma-client/100-queries/037-relation-queries.mdx
@@ -3,6 +3,7 @@ title: 'Relation queries'
 metaTitle: 'Relation queries (Concepts)'
 metaDescription: 'Prisma Client provides convenient queries for working with relations, such as a fluent API, nested writes (transactions), nested reads and relation filters.'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
@@ -30,7 +31,7 @@ Since version [5.9.0](https://github.com/prisma/prisma/releases/tag/5.9.0), you
 
 Because the `relationLoadStrategy` option is currently in Preview, you need to enable it via the `relationJoins` preview feature flag in your Prisma schema file:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 generator client {
   provider        = "prisma-client-js"
   previewFeatures = ["relationJoins"]
@@ -319,9 +320,11 @@ Note that you **cannot** use `select` and `include` _on the same level_. This me
 ```ts highlight=3,6;delete
 // The following query returns an exception
 const user = await prisma.user.findFirst({
+  //delete-next-line
   select: { // This won't work!
     email:  true
   }
+  //delete-next-line
   include: { // This won't work!
     posts: {
       select: {
@@ -711,16 +714,20 @@ const createMany = await prisma.user.createMany({
     {
       name: 'Yewande',
       email: 'yewande@prisma.io',
+      //delete-start
       posts: {
         // Not possible to create posts!
       },
+      //delete-end
     },
     {
       name: 'Noor',
       email: 'noor@prisma.io',
+      //delete-start
       posts: {
         // Not possible to create posts!
       },
+      //delete-end
     },
   ],
 })
diff --git a/content/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdx b/content/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdx
index d2424eef2b..df2a8a2a0a 100644
--- a/content/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdx
+++ b/content/200-orm/200-prisma-client/100-queries/050-filtering-and-sorting.mdx
@@ -162,6 +162,7 @@ model User {
   id    Int     @id @default(autoincrement())
   name  String?
   email String  @unique
+  //highlight-next-line
   posts Post[] // User can have many posts
 }
 
@@ -169,8 +170,10 @@ model Post {
   id        Int     @id @default(autoincrement())
   title     String
   published Boolean @default(true)
+  //highlight-start
   author    User    @relation(fields: [authorId], references: [id])
   authorId  Int
+  //highlight-end
 }
 ```
 
diff --git a/content/200-orm/200-prisma-client/100-queries/056-aggregation-grouping-summarizing.mdx b/content/200-orm/200-prisma-client/100-queries/056-aggregation-grouping-summarizing.mdx
index 6b2508e179..065281ecf8 100644
--- a/content/200-orm/200-prisma-client/100-queries/056-aggregation-grouping-summarizing.mdx
+++ b/content/200-orm/200-prisma-client/100-queries/056-aggregation-grouping-summarizing.mdx
@@ -3,6 +3,7 @@ title: 'Aggregation, grouping, and summarizing'
 metaTitle: 'Aggregation, grouping, and summarizing (Concepts)'
 metaDescription: 'Use Prisma Client to aggregate, group by, count, and select distinct.'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
diff --git a/content/200-orm/200-prisma-client/100-queries/058-transactions.mdx b/content/200-orm/200-prisma-client/100-queries/058-transactions.mdx
index ea2e497a99..385bab6c01 100644
--- a/content/200-orm/200-prisma-client/100-queries/058-transactions.mdx
+++ b/content/200-orm/200-prisma-client/100-queries/058-transactions.mdx
@@ -627,6 +627,7 @@ const createTeamOperation = prisma.team.create({
     name: 'Aurora Adventures',
     members: {
       connect: {
+        //delete-next-line
         id: createUserOperation.id, // Not possible, ID not yet available
       },
     },
@@ -807,6 +808,7 @@ await prisma.team.deleteMany({
     },
   },
   data: {
+    //delete-next-line
     members: {}, // Cannot access members here
   },
 })
@@ -911,14 +913,18 @@ Instead of auto-generating IDs, change the `id` fields of `Team` and `User` to a
 
 ```prisma highlight=2,9;delete|3,10;add
 model Team {
+  //delete-next-line
   id      Int    @id @default(autoincrement())
+  //add-next-line
   id      String @id @default(uuid())
   name    String
   members User[]
 }
 
 model User {
+  //delete-next-line
   id    Int    @id @default(autoincrement())
+  //add-next-line
   id    String @id @default(uuid())
   email String @unique
   teams Team[]
@@ -1014,6 +1020,7 @@ model Team {
   id               Int     @id @default(autoincrement())
   name             String
   User             User[]
+  //highlight-next-line
   stripeCustomerId String?
 }
 ```
@@ -1213,6 +1220,7 @@ model Seat {
   claimedBy User? @relation(fields: [userId], references: [id])
   movieId   Int
   movie     Movie @relation(fields: [movieId], references: [id])
+  //highlight-next-line
   version   Int
 }
 ```
diff --git a/content/200-orm/200-prisma-client/100-queries/060-full-text-search.mdx b/content/200-orm/200-prisma-client/100-queries/060-full-text-search.mdx
index dc0252cc19..d461a7d7cc 100644
--- a/content/200-orm/200-prisma-client/100-queries/060-full-text-search.mdx
+++ b/content/200-orm/200-prisma-client/100-queries/060-full-text-search.mdx
@@ -17,7 +17,7 @@ The full-text search API is currently a Preview feature. To enable this feature,
 
 1. Update the [`previewFeatures`](/orm/reference/preview-features) block in your schema to include the `fullTextSearch` preview feature flag:
 
-   ```prisma file=schema.prisma
+   ```prisma file=schema.prisma showLineNumbers
    generator client {
      provider        = "prisma-client-js"
      previewFeatures = ["fullTextSearch"]
@@ -26,9 +26,10 @@ The full-text search API is currently a Preview feature. To enable this feature,
 
    For MySQL, you will also need to include the `fullTextIndex` preview feature flag:
 
-   ```prisma file=schema.prisma highlight=3;add
+   ```prisma file=schema.prisma highlight=3;add showLineNumbers
    generator client {
      provider        = "prisma-client-js"
+     //add-next-line
      previewFeatures = ["fullTextSearch", "fullTextIndex"]
    }
    ```
@@ -199,7 +200,7 @@ For MySQL, it is necessary to add indexes to any columns you search using the `@
 
 In the following example, one full text index is added to the `content` field of the `Blog` model, and another is added to both the `content` and `title` fields together:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 generator client {
   provider        = "prisma-client-js"
   previewFeatures = ["fullTextSearch", "fullTextIndex"]
diff --git a/content/200-orm/200-prisma-client/100-queries/064-custom-models.mdx b/content/200-orm/200-prisma-client/100-queries/064-custom-models.mdx
index 532e98e860..0262508fa5 100644
--- a/content/200-orm/200-prisma-client/100-queries/064-custom-models.mdx
+++ b/content/200-orm/200-prisma-client/100-queries/064-custom-models.mdx
@@ -64,7 +64,7 @@ async function main() {
 
 <TabItem value="Prisma schema">
 
-```prisma file="prisma/schema.prisma" copy
+```prisma file="prisma/schema.prisma" copy 
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
diff --git a/content/200-orm/200-prisma-client/100-queries/090-raw-database-access/050-raw-queries.mdx b/content/200-orm/200-prisma-client/100-queries/090-raw-database-access/050-raw-queries.mdx
index 03aabad749..9e9e09dd5a 100644
--- a/content/200-orm/200-prisma-client/100-queries/090-raw-database-access/050-raw-queries.mdx
+++ b/content/200-orm/200-prisma-client/100-queries/090-raw-database-access/050-raw-queries.mdx
@@ -133,6 +133,7 @@ When you type the results of `$queryRaw`, the raw data might not always match th
 ```prisma highlight=3;normal
 model Post {
   id        Int     @id @default(autoincrement())
+  //highlight-next-line
   published Boolean @default(false)
   title     String
   content   String?
diff --git a/content/200-orm/200-prisma-client/100-queries/090-raw-database-access/100-custom-and-type-safe-queries.mdx b/content/200-orm/200-prisma-client/100-queries/090-raw-database-access/100-custom-and-type-safe-queries.mdx
index 6460b9c26e..47c440bec4 100644
--- a/content/200-orm/200-prisma-client/100-queries/090-raw-database-access/100-custom-and-type-safe-queries.mdx
+++ b/content/200-orm/200-prisma-client/100-queries/090-raw-database-access/100-custom-and-type-safe-queries.mdx
@@ -41,12 +41,14 @@ If you haven't already, enable the `postgresqlExtensions` Preview feature and ad
 ```prisma highlight=3,9;add
 generator client {
   provider        = "prisma-client-js"
+  //add-next-line
   previewFeatures = ["postgresqlExtensions"]
 }
 
 datasource db {
   provider   = "postgresql"
   url        = env("DATABASE_URL")
+  //add-next-line
   extensions = [postgis]
 }
 ```
@@ -154,6 +156,7 @@ Now, setup the rules that will enable SafeQL to mark invalid SQL queries as ESLi
 /** @type {import('eslint').Linter.Config} */
 module.exports = {
   plugins: [..., '@ts-safeql/eslint-plugin'],
+  //add-start
   rules: {
     '@ts-safeql/check-sql': [
       'error',
@@ -172,6 +175,7 @@ module.exports = {
     ],
   },
 }
+//add-end
 ```
 
 > **Note**: If your `PrismaClient` instance is called something different than `prisma`, you need to adjust the value for `tag` accordingly. For example, if it is called `db`, the value for `tag` should be `'db.+($queryRaw|$executeRaw)'`.
@@ -191,21 +195,25 @@ npm install dotenv
 Then update your ESLint config as follows:
 
 ```js file=.eslintrc.js highlight=1,6-9,16;add
+//add-next-line
 require('dotenv').config()
 
 /** @type {import('eslint').Linter.Config} */
 module.exports = {
   plugins: ['@ts-safeql/eslint-plugin'],
+  //add-start
   // exclude `parserOptions` if you are not using TypeScript
   parserOptions: {
     project: './tsconfig.json',
   },
+  //add-end
   rules: {
     '@ts-safeql/check-sql': [
       'error',
       {
         connections: [
           {
+            //add-next-line
             connectionUrl: process.env.DATABASE_URL,
             // The migrations path:
             migrationsDir: './prisma/migrations',
diff --git a/content/200-orm/200-prisma-client/100-queries/100-query-optimization-performance.mdx b/content/200-orm/200-prisma-client/100-queries/100-query-optimization-performance.mdx
index d75acf5315..ee4b1354af 100644
--- a/content/200-orm/200-prisma-client/100-queries/100-query-optimization-performance.mdx
+++ b/content/200-orm/200-prisma-client/100-queries/100-query-optimization-performance.mdx
@@ -165,15 +165,19 @@ const User = objectType({
     t.nonNull.list.nonNull.field('posts', {
       type: 'Post',
       resolve: (parent, _, context) => {
+        //delete-start
         return context.prisma.post.findMany({
           where: { authorId: parent.id || undefined },
         })
+        //delete-end
+        //add-start
         return context.prisma.user
           .findUnique({
             where: { id: parent.id || undefined },
           })
           .posts()
       },
+      //add-end
     })
   },
 })
diff --git a/content/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdx b/content/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdx
index 51d81994cc..f328563466 100644
--- a/content/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdx
+++ b/content/200-orm/200-prisma-client/200-special-fields-and-types/057-composite-types.mdx
@@ -30,7 +30,7 @@ This page explains how to:
 
 We’ll use this schema for the examples that follow:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 generator client {
   provider = "prisma-client-js"
 }
@@ -116,6 +116,7 @@ In our example schema, suppose that you add a required field to `photo`. This fi
 ...
 type Photo {
   ...
+  //add-next-line
   bitDepth Int @default(8)
 }
 
diff --git a/content/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx b/content/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx
index a33d8c9d31..1e3fb01103 100644
--- a/content/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx
+++ b/content/200-orm/200-prisma-client/200-special-fields-and-types/100-working-with-json-fields.mdx
@@ -15,6 +15,7 @@ model User {
   email            String  @unique
   name             String?
   posts            Post[]
+  //highlight-next-line
   extendedPetsData Json?
 }
 ```
@@ -956,10 +957,11 @@ model Log {
 
 You can update it and type it by using [abstract syntax tree comments](/orm/prisma-schema/overview#comments)
 
-```prisma highlight=4;normal file=schema.prisma
+```prisma highlight=4;normal file=schema.prisma showLineNumbers
 model Log {
   id Int @id
 
+  //highlight-next-line
   /// [LogMetaType]
   meta Json
 }
@@ -967,7 +969,7 @@ model Log {
 
 Then, make sure you define the above type in a type declaration file included in your `tsconfig.json`
 
-```ts file=types.ts
+```ts file=types.ts showLineNumbers
 declare global {
   namespace PrismaJson {
     type LogMetaType = { timestamp: number; host: string }
diff --git a/content/200-orm/200-prisma-client/200-special-fields-and-types/200-working-with-scalar-lists-arrays.mdx b/content/200-orm/200-prisma-client/200-special-fields-and-types/200-working-with-scalar-lists-arrays.mdx
index 8ea14ee790..a518012e25 100644
--- a/content/200-orm/200-prisma-client/200-special-fields-and-types/200-working-with-scalar-lists-arrays.mdx
+++ b/content/200-orm/200-prisma-client/200-special-fields-and-types/200-working-with-scalar-lists-arrays.mdx
@@ -16,6 +16,7 @@ tocDepth: 3
 model User {
   id   Int      @id @default(autoincrement())
   name String
+  //highlight-next-line
   pets String[]
 }
 ```
@@ -27,6 +28,7 @@ model User {
 model User {
   id   String   @id @default(auto()) @map("_id") @db.ObjectId
   name String
+  //highlight-next-line
   pets String[]
 }
 ```
diff --git a/content/200-orm/200-prisma-client/200-special-fields-and-types/300-working-with-composite-ids-and-constraints.mdx b/content/200-orm/200-prisma-client/200-special-fields-and-types/300-working-with-composite-ids-and-constraints.mdx
index 08d13c3b9a..d07eb903ab 100644
--- a/content/200-orm/200-prisma-client/200-special-fields-and-types/300-working-with-composite-ids-and-constraints.mdx
+++ b/content/200-orm/200-prisma-client/200-special-fields-and-types/300-working-with-composite-ids-and-constraints.mdx
@@ -40,6 +40,7 @@ model Like {
   User   User @relation(fields: [userId], references: [id])
   Post   Post @relation(fields: [postId], references: [id])
 
+  //highlight-next-line
   @@id([postId, userId])
 }
 ```
@@ -64,6 +65,7 @@ model Like {
   User   User @relation(fields: [userId], references: [id])
   Post   Post @relation(fields: [postId], references: [id])
 
+  //highlight-next-line
   @@id(name: "likeId", [postId, userId])
 }
 ```
diff --git a/content/200-orm/200-prisma-client/300-client-extensions/100-model.mdx b/content/200-orm/200-prisma-client/300-client-extensions/100-model.mdx
index 63b820db21..19bae70373 100644
--- a/content/200-orm/200-prisma-client/300-client-extensions/100-model.mdx
+++ b/content/200-orm/200-prisma-client/300-client-extensions/100-model.mdx
@@ -3,6 +3,7 @@ title: '`model`: Add custom methods to your models'
 metaTitle: 'Prisma Client extensions: model component'
 metaDescription: 'Extend the functionality of Prisma Client, model component'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
diff --git a/content/200-orm/200-prisma-client/300-client-extensions/110-client.mdx b/content/200-orm/200-prisma-client/300-client-extensions/110-client.mdx
index fa66f86589..66ee3f770f 100644
--- a/content/200-orm/200-prisma-client/300-client-extensions/110-client.mdx
+++ b/content/200-orm/200-prisma-client/300-client-extensions/110-client.mdx
@@ -3,6 +3,7 @@ title: '`client`: Add methods to Prisma Client'
 metaTitle: 'Prisma Client extensions: client component'
 metaDescription: 'Extend the functionality of Prisma Client, client component'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
diff --git a/content/200-orm/200-prisma-client/300-client-extensions/120-query.mdx b/content/200-orm/200-prisma-client/300-client-extensions/120-query.mdx
index 24b7c5a13f..d3e035f5da 100644
--- a/content/200-orm/200-prisma-client/300-client-extensions/120-query.mdx
+++ b/content/200-orm/200-prisma-client/300-client-extensions/120-query.mdx
@@ -3,6 +3,7 @@ title: '`query`: Create custom Prisma Client queries'
 metaTitle: 'Prisma Client extensions: query component'
 metaDescription: 'Extend the functionality of Prisma Client, query component'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
diff --git a/content/200-orm/200-prisma-client/300-client-extensions/130-result.mdx b/content/200-orm/200-prisma-client/300-client-extensions/130-result.mdx
index 1381027319..79204abbff 100644
--- a/content/200-orm/200-prisma-client/300-client-extensions/130-result.mdx
+++ b/content/200-orm/200-prisma-client/300-client-extensions/130-result.mdx
@@ -3,6 +3,7 @@ title: '`result`: Add custom fields and methods to query results'
 metaTitle: 'Prisma Client extensions: result component'
 metaDescription: 'Extend the functionality of Prisma Client, result component'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
diff --git a/content/200-orm/200-prisma-client/300-client-extensions/140-shared-extensions.mdx b/content/200-orm/200-prisma-client/300-client-extensions/140-shared-extensions.mdx
index 9bc7ec8495..04033d913f 100644
--- a/content/200-orm/200-prisma-client/300-client-extensions/140-shared-extensions.mdx
+++ b/content/200-orm/200-prisma-client/300-client-extensions/140-shared-extensions.mdx
@@ -3,6 +3,7 @@ title: 'Shared Prisma Client extensions'
 metaTitle: 'Shared Prisma Client extensions'
 metaDescription: 'Share extensions or import shared extensions into your Prisma project'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
diff --git a/content/200-orm/200-prisma-client/300-client-extensions/500-middleware/100-soft-delete-middleware.mdx b/content/200-orm/200-prisma-client/300-client-extensions/500-middleware/100-soft-delete-middleware.mdx
index 0f08e59d65..e774be1c06 100644
--- a/content/200-orm/200-prisma-client/300-client-extensions/500-middleware/100-soft-delete-middleware.mdx
+++ b/content/200-orm/200-prisma-client/300-client-extensions/500-middleware/100-soft-delete-middleware.mdx
@@ -3,6 +3,7 @@ title: 'Middleware sample: soft delete'
 metaTitle: 'Middleware sample: soft delete (Reference)'
 metaDescription: 'How to use middleware to intercept deletes and set a field value instead of deleting the record.'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
@@ -48,6 +49,7 @@ model Post {
   userId  Int?
   tags    Tag[]
   views   Int     @default(0)
+  //highlight-next-line
   deleted Boolean @default(false)
 }
 
@@ -76,6 +78,7 @@ Add a field named `deleted` to the `Post` model. You can choose between two fiel
   model Post {
     id      Int     @id @default(autoincrement())
     ...
+    //highlight-next-line
     deleted Boolean @default(false)
   }
   ```
@@ -86,6 +89,7 @@ Add a field named `deleted` to the `Post` model. You can choose between two fiel
   model Post {
     id      Int       @id @default(autoincrement())
     ...
+    //highlight-next-line
     deleted DateTime?
   }
   ```
diff --git a/content/200-orm/200-prisma-client/300-client-extensions/index.mdx b/content/200-orm/200-prisma-client/300-client-extensions/index.mdx
index 72fa11c353..363a7e6f99 100644
--- a/content/200-orm/200-prisma-client/300-client-extensions/index.mdx
+++ b/content/200-orm/200-prisma-client/300-client-extensions/index.mdx
@@ -3,6 +3,7 @@ title: 'Extensions'
 metaTitle: 'Prisma Client extensions'
 metaDescription: 'Extend the functionality of Prisma Client'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
diff --git a/content/200-orm/200-prisma-client/400-type-safety/050-prisma-validator.mdx b/content/200-orm/200-prisma-client/400-type-safety/050-prisma-validator.mdx
index ee3b6f5a92..cfd27090ee 100644
--- a/content/200-orm/200-prisma-client/400-type-safety/050-prisma-validator.mdx
+++ b/content/200-orm/200-prisma-client/400-type-safety/050-prisma-validator.mdx
@@ -55,13 +55,17 @@ The following example passes the `UserSelect` generated type into the `Prisma.va
 ```ts highlight=3,4,5;delete|7-9;add
 import { Prisma } from '@prisma/client'
 
+//delete-start
 const userEmail: Prisma.UserSelect = {
   email: true,
 }
+//delete-end
 
+//add-start
 const userEmail = Prisma.validator<Prisma.UserSelect>()({
   email: true,
 })
+//add-end
 
 // Run inside async function
 const user = await prisma.user.findUnique({
diff --git a/content/200-orm/200-prisma-client/400-type-safety/830-prisma-type-system.mdx b/content/200-orm/200-prisma-client/400-type-safety/830-prisma-type-system.mdx
index 514666a03f..a1792105fc 100644
--- a/content/200-orm/200-prisma-client/400-type-safety/830-prisma-type-system.mdx
+++ b/content/200-orm/200-prisma-client/400-type-safety/830-prisma-type-system.mdx
@@ -14,7 +14,7 @@ This guide introduces Prisma ORM's type system and explains how to introspect ex
 
 Prisma ORM uses _types_ to define the kind of data that a field can hold. To make it easy to get started, Prisma ORM provides a small number of core [scalar types](/orm/reference/prisma-schema-reference#model-field-scalar-types) that should cover most default use cases. For example, take the following blog post model:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -47,7 +47,7 @@ To see the default type mappings for all databases for a specific given Prisma O
 
 Sometimes you may need to use a more specific database type that is not one of the default type mappings for your Prisma ORM type. For this purpose, Prisma ORM provides [native type attributes](/orm/prisma-schema/data-model/models#native-types-mapping) to refine the core scalar types. For example, in the `createdAt` field of your `Post` model above you may want to use a date-only column in your underlying PostgreSQL database, by using the `date` type instead of the default type mapping of `timestamp(3)`. To do this, add a `@db.Date` native type attribute to the `createdAt` field:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id        Int      @id
   title     String
@@ -85,7 +85,7 @@ npx prisma db pull
 
 You will get the following Prisma schema:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id       Int     @id @default(autoincrement())
   name     String
@@ -110,11 +110,12 @@ npx prisma db pull
 
 Your Prisma schema now includes the new `createdAt` field with a Prisma ORM type of `DateTime`. The `createdAt` field also has a `@db.Date` native type attribute, because PostgreSQL's `date` is not the default type for the `DateTime` type:
 
-```prisma file=schema.prisma highlight=5;add
+```prisma file=schema.prisma highlight=5;add showLineNumbers
 model User {
   id        Int      @id @default(autoincrement())
   name      String
   isActive  Boolean
+  //add-next-line
   createdAt DateTime @db.Date
 }
 ```
@@ -125,7 +126,7 @@ When you apply schema changes to your database using Prisma Migrate or `db push`
 
 As an example, create a Prisma schema with the following `Post` model:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id        Int      @id
   title     String
diff --git a/content/200-orm/200-prisma-client/450-testing/100-unit-testing.mdx b/content/200-orm/200-prisma-client/450-testing/100-unit-testing.mdx
index 0e65d18610..ef0d33450a 100644
--- a/content/200-orm/200-prisma-client/450-testing/100-unit-testing.mdx
+++ b/content/200-orm/200-prisma-client/450-testing/100-unit-testing.mdx
@@ -80,11 +80,12 @@ The singleton file tells Jest to mock a default export (the Prisma Client instan
 
 Next, add the `setupFilesAfterEnv` property to your `jest.config.js` file with the path to your `singleton.ts` file.
 
-```js file=jest.config.js highlight=5;add
+```js file=jest.config.js highlight=5;add showLineNumbers
 module.exports = {
   clearMocks: true,
   preset: 'ts-jest',
   testEnvironment: 'node',
+  //add-next-line
   setupFilesAfterEnv: ['<rootDir>/singleton.ts'],
 }
 ```
@@ -143,7 +144,7 @@ A real world use case for unit testing Prisma ORM might be a signup form. Your u
 
 All of the examples that follow use the following schema model:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id                       Int     @id @default(autoincrement())
   email                    String  @unique
diff --git a/content/200-orm/200-prisma-client/450-testing/150-integration-testing.mdx b/content/200-orm/200-prisma-client/450-testing/150-integration-testing.mdx
index 13a4138b43..57517dd3ae 100644
--- a/content/200-orm/200-prisma-client/450-testing/150-integration-testing.mdx
+++ b/content/200-orm/200-prisma-client/450-testing/150-integration-testing.mdx
@@ -25,7 +25,7 @@ The following ecommerce schema will be used throughout the guide. This varies fr
 
 <summary>Ecommerce schema</summary>
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 // Can have 1 customer
 // Can have many order details
 model CustomerOrder {
diff --git a/content/200-orm/200-prisma-client/500-deployment/201-serverless/150-deploy-to-azure-functions.mdx b/content/200-orm/200-prisma-client/500-deployment/201-serverless/150-deploy-to-azure-functions.mdx
index e99e30cb7f..583c41cef6 100644
--- a/content/200-orm/200-prisma-client/500-deployment/201-serverless/150-deploy-to-azure-functions.mdx
+++ b/content/200-orm/200-prisma-client/500-deployment/201-serverless/150-deploy-to-azure-functions.mdx
@@ -24,9 +24,10 @@ While Prisma ORM works well with Azure functions, there are a few things to take
 
 When deploying a function app, the operating system that Azure functions runs a remote build is different from the one used to host your functions. Therefore, we recommend specifying the following [`binaryTargets` options](/orm/reference/prisma-schema-reference#binarytargets-options) in your Prisma schema:
 
-```prisma file=schema.prisma highlight=3;normal
+```prisma file=schema.prisma highlight=3;normal showLineNumbers
 generator client {
   provider      = "prisma-client-js"
+  //highlight-next-line
   binaryTargets = ["native", "debian-openssl-1.1.x"]
 }
 ```
diff --git a/content/200-orm/200-prisma-client/500-deployment/201-serverless/300-deploy-to-vercel.mdx b/content/200-orm/200-prisma-client/500-deployment/201-serverless/300-deploy-to-vercel.mdx
index 7cdaf909bb..71bd5e5f52 100644
--- a/content/200-orm/200-prisma-client/500-deployment/201-serverless/300-deploy-to-vercel.mdx
+++ b/content/200-orm/200-prisma-client/500-deployment/201-serverless/300-deploy-to-vercel.mdx
@@ -20,10 +20,11 @@ While our examples use Next.js, you can deploy other applications to Vercel. See
 
 Vercel will automatically cache dependencies on deployment. For most applications, this will not cause any issues. However, for Prisma ORM, it may result in an outdated version of Prisma Client on a change in your Prisma schema. To avoid this issue, add `prisma generate` to the `postinstall` script of your application:
 
-```json5 file=package.json highlight=4;add
+```json5 file=package.json highlight=4;add showLineNumbers
 {
   ...
   "scripts" {
+    //add-next-line
     "postinstall": "prisma generate"
   }
   ...
@@ -40,9 +41,10 @@ If you see `prisma: command not found` errors during your deployment to Vercel,
 
 Another option to avoid an outdated Prisma Client is to use [a custom output path](/orm/prisma-client/setup-and-configuration/generating-prisma-client#using-a-custom-output-path) and check your client into version control. This way each deployment is guaranteed to include the correct Prisma Client.
 
-```prisma file=schema.prisma highlight=3;add
+```prisma file=schema.prisma highlight=3;add showLineNumbers
 generator client {
   provider = "prisma-client-js"
+  //add-next-line
   output   = "./generated/client"
 }
 ```
diff --git a/content/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdx b/content/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdx
index 253b60a347..4bd7badaf0 100644
--- a/content/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdx
+++ b/content/200-orm/200-prisma-client/500-deployment/201-serverless/400-deploy-to-aws-lambda.mdx
@@ -41,7 +41,7 @@ Lambda functions that use [arm64 architectures (AWS Graviton2 processor)](https:
 
 In the `generator` block of your `schema.prisma` file, add the following:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 binaryTargets = ["native", "linux-arm64-openssl-1.0.x"]
 ```
 
@@ -244,23 +244,25 @@ This will ensure that, after webpack bundles your code, the Prisma Client is gen
 
 Lastly, you will want to exclude [Prisma ORM query engines](/orm/more/under-the-hood/engines) that do not match the AWS Lambda runtime. Update your `serverless.yml` by adding the following script that makes sure only the required query engine, `rhel-openssl-1.0.x`, is included in the final packaged archive.
 
-```yaml file=serverless.yml highlight=6;add
+```yaml file=serverless.yml highlight=6;add showLineNumbers
 custom:
   webpack:
     packagerOptions:
       scripts:
         - prisma generate
+        //add-next-line
         -- find . -name "libquery_engine-*" -not -name "libquery_engine-rhel-openssl-*" | xargs rm
 ```
 
 If you are deploying to [Lambda functions with ARM64 architecture](#lambda-functions-with-arm64-architectures) you should update the `find` command to the following:
 
-```yaml file=serverless.yml highlight=6;add
+```yaml file=serverless.yml highlight=6;add showLineNumbers
 custom:
   webpack:
     packagerOptions:
       scripts:
         - prisma generate
+        //add-next-line
         -- find . -name "libquery_engine-*" -not -name "libquery_engine-arm64-openssl-*" | xargs rm
 ```
 
diff --git a/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare-workers.mdx b/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare-workers.mdx
index eb1eb36b67..5276eb88e8 100644
--- a/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare-workers.mdx
+++ b/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare-workers.mdx
@@ -162,10 +162,11 @@ To get started with Prisma Accelerate:
 
    Add [`directUrl`](/orm/reference/prisma-schema-reference#fields) property in `datasource` block in the `schema.prisma` file.
 
-   ```prisma highlight=4;add file=prisma/schema.prisma
+   ```prisma highlight=4;add file=prisma/schema.prisma showLineNumbers
    datasource db {
      provider  = "postgresql"
      url       = env("DATABASE_URL")
+     //add-next-line
      directUrl = env("DIRECT_URL")
    }
    ```
diff --git a/content/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdx b/content/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdx
index 7341e8f772..fda269f086 100644
--- a/content/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdx
+++ b/content/200-orm/200-prisma-client/500-deployment/301-edge/550-deploy-to-deno-deploy.mdx
@@ -49,11 +49,13 @@ To set up your application:
 
    To use Deno, you need to add the preview feature flag `deno` to the `generator` block of your `schema.prisma` file. Also, Deno requires that you generate Prisma Client in a custom location. You can enable this with the `output` parameter in the `generator` block. To satisfy both of these requirements, add the following lines to the `generator` block:
 
-   ```prisma file=schema.prisma highlight=3-4,12-23;add
+   ```prisma file=schema.prisma highlight=3-4,12-23;add showLineNumbers
    generator client {
      provider        = "prisma-client-js"
+     //add-start
      previewFeatures = ["deno"]
      output          = "../generated/client"
+     //add-end
    }
    
    datasource db {
@@ -61,6 +63,7 @@ To set up your application:
      url      = env("DATABASE_URL")
    }
    
+   //add-start
    model Log {
      id      Int    @id @default(autoincrement())
      level   Level
@@ -73,6 +76,7 @@ To set up your application:
      Warn
      Error
    }
+   //add-end
    ```
 
 4. In your `.env` file, replace the current placeholder connection string `postgresql://johndoe:randompassword@localhost:5432/mydb?schema=public` with your PostgreSQL connection string.
diff --git a/content/200-orm/200-prisma-client/500-deployment/550-deploy-database-changes-with-prisma-migrate.mdx b/content/200-orm/200-prisma-client/500-deployment/550-deploy-database-changes-with-prisma-migrate.mdx
index e9cee833a5..a49ecaff23 100644
--- a/content/200-orm/200-prisma-client/500-deployment/550-deploy-database-changes-with-prisma-migrate.mdx
+++ b/content/200-orm/200-prisma-client/500-deployment/550-deploy-database-changes-with-prisma-migrate.mdx
@@ -41,7 +41,7 @@ As part of your CI/CD, you can run `prisma migrate deploy` as part of your pipel
 
 Here is an example action that will run your migrations against your database:
 
-```yaml file=deploy.yml highlight=17-20
+```yaml file=deploy.yml highlight=17-20 showLineNumbers
 name: Deploy
 on:
   push:
diff --git a/content/200-orm/200-prisma-client/500-deployment/600-deploy-migrations-from-a-local-environment.mdx b/content/200-orm/200-prisma-client/500-deployment/600-deploy-migrations-from-a-local-environment.mdx
index 24e2a5d0ac..cded0eef25 100644
--- a/content/200-orm/200-prisma-client/500-deployment/600-deploy-migrations-from-a-local-environment.mdx
+++ b/content/200-orm/200-prisma-client/500-deployment/600-deploy-migrations-from-a-local-environment.mdx
@@ -23,9 +23,11 @@ If you do not have an automated CI/CD process, you can technically deploy new mi
 1. Make sure your migration history is up to date. You can do this through running `prisma migrate dev`, which will generate a migration history from the latest changes made.
 2. Swap your local connection URL for your production connection URL
 
-```bash file=.env highlight=1;delete|3;add
+```bash file=.env highlight=1;delete|3;add showLineNumbers
+//delete-next-line
 DATABASE_URL="postgresql://johndoe:randompassword@localhost:5432/my_local_database"
 
+//add-next-line
 DATABASE_URL="postgresql://johndoe:randompassword@localhost:5432/my_production_database"
 ```
 
diff --git a/content/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdx b/content/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdx
index fe226fb53f..ce0ff25c4b 100644
--- a/content/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdx
+++ b/content/200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdx
@@ -4,6 +4,7 @@ metaTitle: 'Metrics (Preview)'
 metaDescription: 'Diagnose application performance with insights into Prisma Client database activity.'
 sidebar_class_name: preview-badge
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
@@ -541,12 +542,14 @@ This returns information in the following format:
   "counters": [
     {
       "key": "query_total_operations",
+      //add-next-line
       "labels": { "server": "us_server1", "app_version": "one" },
       "value": 0,
       "description": "The total number of operations executed"
     },
     {
       "key": "prisma_datasource_queries_total",
+      //add-next-line
       "labels": { "server": "us_server1", "app_version": "one" },
       "value": 0,
       "description": "The total number of queries executed"
diff --git a/content/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdx b/content/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdx
index c613417562..acb70563ca 100644
--- a/content/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdx
+++ b/content/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdx
@@ -4,6 +4,7 @@ metaTitle: 'OpenTelemetry tracing (Preview)'
 metaDescription: 'Diagnose application performance with detailed traces of each query.'
 sidebar_class_name: preview-badge
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
@@ -242,7 +243,7 @@ When you perform an interactive transaction, you'll see the following spans in a
 
 As an example, take the following Prisma schema:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 generator client {
   provider        = "prisma-client-js"
   previewFeatures = ["tracing", "interactiveTransactions"]
@@ -381,10 +382,12 @@ An example implementation looks like this:
 ```ts highlight=3,7;add
 import { SemanticResourceAttributes } from '@opentelemetry/semantic-conventions'
 import { NodeTracerProvider } from '@opentelemetry/sdk-trace-node'
+//add-next-line
 import { TraceIdRatioBasedSampler } from '@opentelemetry/core'
 import { Resource } from '@opentelemetry/resources'
 
 const provider = new NodeTracerProvider({
+  //add-next-line
   sampler: new TraceIdRatioBasedSampler(0.1),
   resource: new Resource({
     // we can define some metadata about the trace resource
diff --git a/content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/230-handling-exceptions-and-errors.mdx b/content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/230-handling-exceptions-and-errors.mdx
index 4041e39ec3..0977366d88 100644
--- a/content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/230-handling-exceptions-and-errors.mdx
+++ b/content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/230-handling-exceptions-and-errors.mdx
@@ -11,7 +11,7 @@ In order to handle different types of errors you can use `instanceof` to check w
 
 The following example tries to create a user with an already existing email record. This will throw an error because the `email` field has the `@unique` attribute applied to it.
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id    Int     @id @default(autoincrement())
   email String  @unique
diff --git a/content/200-orm/300-prisma-migrate/050-getting-started.mdx b/content/200-orm/300-prisma-migrate/050-getting-started.mdx
index 73bd41672b..b6a785736c 100644
--- a/content/200-orm/300-prisma-migrate/050-getting-started.mdx
+++ b/content/200-orm/300-prisma-migrate/050-getting-started.mdx
@@ -17,7 +17,7 @@ To get started with Prisma Migrate in a development environment:
 
 1.  Create a Prisma schema:
 
-    ```prisma file=schema.prisma
+    ```prisma file=schema.prisma showLineNumbers
     datasource db {
       provider = "postgresql"
       url      = env("DATABASE_URL")
@@ -101,6 +101,7 @@ To get started with Prisma Migrate in a development environment:
     ```prisma highlight=3;add
     model User {
       id       Int    @id @default(autoincrement())
+      //add-next-line
       jobTitle String
       name     String
       posts    Post[]
@@ -213,8 +214,10 @@ To include [unsupported database features](/orm/prisma-migrate/workflows/unsuppo
    ```sql highlight=3,4;add
    /* Generated migration SQL */
 
+   //add-start
    CREATE UNIQUE INDEX tests_success_constraint ON posts (subject, target)
     WHERE success;
+    //add-end
    ```
 
    - If the changes are significant, it can be easier to replace the entire migration file with the result of a database dump ([`mysqldump`](https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html), [`pg_dump`](https://www.postgresql.org/docs/12/app-pgdump.html))
diff --git a/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/010-mental-model.mdx b/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/010-mental-model.mdx
index 8ca03218a7..33c7a8d124 100644
--- a/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/010-mental-model.mdx
+++ b/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/010-mental-model.mdx
@@ -3,6 +3,7 @@ title: 'Mental model'
 metaTitle: 'A mental model for Prisma Migrate'
 metaDescription: 'A mental model guide for working with Prisma Migrate in your project'
 tocDepth: 4
+toc_max_heading_level: 4
 ---
 
 <TopBlock title={frontMatter.title}>
diff --git a/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/200-shadow-database.mdx b/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/200-shadow-database.mdx
index 5c15aedc04..c2603ae4c9 100644
--- a/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/200-shadow-database.mdx
+++ b/content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/200-shadow-database.mdx
@@ -90,6 +90,7 @@ In some cases it might make sense (e.g. when [creating and dropping databases is
 datasource db {
   provider          = "postgresql"
   url               = env("DATABASE_URL")
+  //highlight-next-line
   shadowDatabaseUrl = env("SHADOW_DATABASE_URL")
 }
 ```
@@ -108,6 +109,7 @@ Some cloud providers do not allow you to drop and create databases with SQL. Som
 datasource db {
   provider          = "postgresql"
   url               = env("DATABASE_URL")
+  //highlight-next-line
   shadowDatabaseUrl = env("SHADOW_DATABASE_URL")
 }
 ```
diff --git a/content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx b/content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx
index f26824d9d1..3b040db926 100644
--- a/content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx
+++ b/content/200-orm/300-prisma-migrate/300-workflows/10-seeding.mdx
@@ -80,7 +80,7 @@ Here we suggest some specific seed scripts for different situations. You are fre
 1. Create a new file named `seed.ts`. This can be placed anywhere within your projects folder structure. The below example places it in the `/prisma` folder.
 2. In the `seed.ts` file, import Prisma Client, initialize it and create some records. As an example, take the following Prisma schema with a `User` and `Post` model:
 
-   ```prisma file=schema.prisma
+   ```prisma file=schema.prisma showLineNumbers
    model User {
      id    Int    @id @default(autoincrement())
      email String @unique
@@ -199,7 +199,7 @@ Here we suggest some specific seed scripts for different situations. You are fre
 1. Create a new file named `seed.js`. This can be placed anywhere within your projects folder structure. The below example places it in the `/prisma` folder.
 2. In the `seed.js` file, import Prisma Client, initialize it and create some records. As an example, take the following Prisma schema with a `User` and `Post` model:
 
-   ```prisma file=schema.prisma
+   ```prisma file=schema.prisma showLineNumbers
    generator client {
      provider = "prisma-client-js"
    }
diff --git a/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx b/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx
index 020f671487..182e6be7c3 100644
--- a/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx
+++ b/content/200-orm/300-prisma-migrate/300-workflows/100-team-development.mdx
@@ -36,7 +36,7 @@ The following tabs show the team's Prisma schema before and after a round of cha
 
 <TabItem value="Before">
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma 
 model Post {
   id        Int     @id @default(autoincrement())
   title     String
@@ -72,16 +72,20 @@ model User {
   id              Int     @id @default(autoincrement())
   email           String  @unique
   name            String?
+  //add-start
   favoriteColor   String? // Added by Ania
   bestPacmanScore Int? // Added by you
+  //add-end
   posts           Post[]
 }
 
+//add-start
 // Added by Javier
 model Tag {
   tagName     String   @id
   tagCategory Category
 }
+//add-end
 ```
 
 </TabItem>
@@ -98,6 +102,7 @@ Your team members Ania and Javier make additive changes to the schema in their l
    ```prisma highlight=3;add
    model User {
      /* ... */
+     //add-next-line
      favoriteColor String?
    }
    ```
@@ -118,10 +123,12 @@ Your team members Ania and Javier make additive changes to the schema in their l
 1. Adds a new model to the schema:
 
    ```prisma highlight=1-4;add
+   //add-start
    model Tag {
      tagName     String   @id
      tagCategory Category
    }
+   //add-end
    ```
 
 1. Generates a migration:
@@ -155,15 +162,18 @@ The migration history now has **two** new migrations:
      ```prisma highlight=3,7-11;add
      model User {
        /* ... */
+       //add-next-line
        favoriteColor   String?
        bestPacmanScore Int?
      }
      
+     //add-start
      model Tag {
        tagName     String   @id
        tagCategory Category
        posts       Post[]
      }
+     //add-end
      ```
 
 1. Run the `migrate dev` command:
diff --git a/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx b/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx
index 85e5226928..53da5871a1 100644
--- a/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx
+++ b/content/200-orm/300-prisma-migrate/300-workflows/120-native-database-functions.mdx
@@ -18,15 +18,17 @@ Do not activate extensions outside a migration file if you use Prisma Migrate. T
 
 In Prisma ORM versions 4.5.0 and later, you can activate the extension by declaring it in your Prisma schema with the [`postgresqlExtensions` preview feature](/orm/prisma-schema/postgresql-extensions):
 
-```prisma file=schema.prisma highlight=3,9;add
+```prisma file=schema.prisma highlight=3,9;add showLineNumbers
 generator client {
   provider        = "prisma-client-js"
+  //add-next-line
   previewFeatures = ["postgresqlExtensions"]
 }
 
 datasource db {
   provider   = "postgresql"
   url        = env("DATABASE_URL")
+  //add-next-line
   extensions = [pgcrypto]
 }
 ```
diff --git a/content/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdx b/content/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdx
index 870d7eafbc..c7af38ba45 100644
--- a/content/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdx
+++ b/content/200-orm/300-prisma-migrate/300-workflows/20-prototyping-your-schema.mdx
@@ -130,6 +130,7 @@ The following scenario demonstrates how to use `db push` to synchronize a new sc
     model Post {
       id          Int        @id @default(autoincrement())
       title       String
+      //add-next-line
       description String
       published   Boolean    @default(true)
       content     String     @db.VarChar(500)
diff --git a/content/200-orm/300-prisma-migrate/300-workflows/40-customizing-migrations.mdx b/content/200-orm/300-prisma-migrate/300-workflows/40-customizing-migrations.mdx
index c55f0bba93..b9530276b7 100644
--- a/content/200-orm/300-prisma-migrate/300-workflows/40-customizing-migrations.mdx
+++ b/content/200-orm/300-prisma-migrate/300-workflows/40-customizing-migrations.mdx
@@ -50,6 +50,7 @@ To actually **rename** a field and avoid data loss when you run the migration in
 ```prisma highlight=3;normal;
 model Profile {
   id       Int    @id @default(autoincrement())
+  //highlight-next-line
   biograpy String
   userId   Int    @unique
   user     User   @relation(fields: [userId], references: [id])
@@ -63,7 +64,9 @@ To rename the `biograpy` field to `biography`:
    ```prisma highlight=3;delete|4;add;
    model Profile {
      id        Int    @id @default(autoincrement())
+     //delete-next-line
      biograpy  String
+     //add-next-line
      biography String
      userId    Int    @unique
      user      User   @relation(fields: [userId], references: [id])
@@ -124,6 +127,7 @@ With the _expand and contract_ pattern, renaming the field `bio` to `biography`
    model Profile {
      id        Int    @id @default(autoincrement())
      bio       String
+     //add-next-line
      biography String
      userId    Int    @unique
      user      User   @relation(fields: [userId], references: [id])
@@ -149,6 +153,7 @@ With the _expand and contract_ pattern, renaming the field `bio` to `biography`
    ```prisma highlight=3;delete;
    model Profile {
      id        Int    @id @default(autoincrement())
+     //delete-next-line
      bio       String
      biography String
      userId    Int    @unique
diff --git a/content/200-orm/300-prisma-migrate/300-workflows/45-data-migration.mdx b/content/200-orm/300-prisma-migrate/300-workflows/45-data-migration.mdx
index 2a51979913..74ba797969 100644
--- a/content/200-orm/300-prisma-migrate/300-workflows/45-data-migration.mdx
+++ b/content/200-orm/300-prisma-migrate/300-workflows/45-data-migration.mdx
@@ -32,7 +32,7 @@ It also makes the following assumptions:
 
 For this guide, you will modify the following schema by replacing the `published` boolean field with a `status` enum:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 generator client {
   provider = "prisma-client-js"
 }
@@ -64,13 +64,15 @@ Make the following updates to your Prisma schema:
 - Add a `status` column to the `Post` model
 - Mark the `published` field as optional
 
-```prisma file=prisma/schema.prisma highlight=5,6,9-15;edit
+```prisma file=prisma/schema.prisma highlight=5,6,9-15;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String
   content   String?
+  //edit-start
   published Boolean? @default(false)
   status    Status
+  //edit-end
 }
 
 enum Status {
@@ -112,12 +114,13 @@ Then run prisma migrate dev to apply it and verify it works.
 
 Exit from the migration step and update the schema by adding a default value for the `status` field by adding the `@default()` attribute function.
 
-```prisma file=prisma/schema.prisma highlight=6;edit
+```prisma file=prisma/schema.prisma highlight=6;edit showLineNumbers
 model Post {
   id        Int      @id @default(autoincrement())
   title     String
   content   String?
   published Boolean? @default(false)
+  //edit-next-line
   status    Status   @default(Unknown)
 }
 
@@ -223,6 +226,7 @@ model Post {
   id        Int      @id @default(autoincrement())
   title     String
   content   String?
+  //delete-next-line
   published Boolean? @default(false)
   status    Status   @default(Unknown)
 }
diff --git a/content/200-orm/300-prisma-migrate/300-workflows/60-generating-down-migrations.mdx b/content/200-orm/300-prisma-migrate/300-workflows/60-generating-down-migrations.mdx
index b2b65a5817..786e45b6dc 100644
--- a/content/200-orm/300-prisma-migrate/300-workflows/60-generating-down-migrations.mdx
+++ b/content/200-orm/300-prisma-migrate/300-workflows/60-generating-down-migrations.mdx
@@ -47,7 +47,7 @@ This section describes how to generate a down migration SQL file along with the
 
 As an example, take the following Prisma schema with a `User` and `Post` model as a starting point:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id       Int     @id @default(autoincrement())
   title    String  @db.VarChar(255)
@@ -69,7 +69,7 @@ You will need to create the down migration first, before creating the correspond
 
 1. Edit your Prisma schema to make the changes you require for your up migration. In this example, you will add a new `Profile` model:
 
-   ```prisma file=schema.prisma highlight=8-14;add|20;add
+   ```prisma file=schema.prisma highlight=8-14;add|20;add showLineNumbers
    model Post {
      id       Int     @id @default(autoincrement())
      title    String  @db.VarChar(255)
@@ -77,6 +77,7 @@ You will need to create the down migration first, before creating the correspond
      author   User    @relation(fields: [authorId], references: [id])
      authorId Int
    }
+   //add-start
    
    model Profile {
      id     Int     @id @default(autoincrement())
@@ -84,11 +85,13 @@ You will need to create the down migration first, before creating the correspond
      user   User    @relation(fields: [userId], references: [id])
      userId Int     @unique
    }
+   //add-end
    
    model User {
      id      Int      @id @default(autoincrement())
      name    String?
      posts   Post[]
+     //add-next-line
      profile Profile?
    }
    ```
diff --git a/content/200-orm/300-prisma-migrate/300-workflows/70-patching-and-hotfixing.mdx b/content/200-orm/300-prisma-migrate/300-workflows/70-patching-and-hotfixing.mdx
index f0e182a642..7e536f3f32 100644
--- a/content/200-orm/300-prisma-migrate/300-workflows/70-patching-and-hotfixing.mdx
+++ b/content/200-orm/300-prisma-migrate/300-workflows/70-patching-and-hotfixing.mdx
@@ -137,7 +137,7 @@ This section gives an example scenario of a failed migration, and explains how t
 
 Imagine that you have the following `User` model in your schema, in both your local development environment and your production environment:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id   Int    @id
   name String
@@ -148,7 +148,7 @@ At this point, your schemas are in sync, but the data in the two environments is
 
 You then decide to make changes to your data model, adding another `Post` model and making the `name` field on `User` unique:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id    Int     @id
   name  String  @unique
diff --git a/content/200-orm/500-reference/100-prisma-schema-reference.mdx b/content/200-orm/500-reference/100-prisma-schema-reference.mdx
index 1394f884b5..eed0a4502c 100644
--- a/content/200-orm/500-reference/100-prisma-schema-reference.mdx
+++ b/content/200-orm/500-reference/100-prisma-schema-reference.mdx
@@ -1069,6 +1069,7 @@ Makes a field a list.
 ```prisma highlight=3;normal
 model User {
   id             Int      @id @default(autoincrement())
+  //highlight-next-line
   favoriteColors String[]
 }
 ```
@@ -1079,6 +1080,7 @@ model User {
 ```prisma highlight=3;normal
 model User {
   id             String   @id @default(auto()) @map("_id") @db.ObjectId
+  //highlight-next-line
   favoriteColors String[]
 }
 ```
@@ -1096,6 +1098,7 @@ Available in version 4.0.0 and later.
 ```prisma highlight=3;normal
 model User {
   id             Int      @id @default(autoincrement())
+  //highlight-next-line
   favoriteColors String[] @default(["red", "blue", "green"])
 }
 ```
@@ -1106,6 +1109,7 @@ model User {
 ```prisma highlight=3;normal
 model User {
   id             String   @id @default(auto()) @map("_id") @db.ObjectId
+  //highlight-next-line
   favoriteColors String[] @default(["red", "blue", "green"])
 }
 ```
@@ -1128,6 +1132,7 @@ Makes a field optional.
 ```prisma highlight=3;normal
 model User {
   id   Int     @id @default(autoincrement())
+  //highlight-next-line
   name String?
 }
 ```
@@ -1857,6 +1862,7 @@ model User {
   id      Int      @id @default(autoincrement())
   email   String   @unique
   name    String?
+  //highlight-next-line
   role    Role     @default(USER)
   posts   Post[]
   profile Profile?
@@ -1878,6 +1884,7 @@ model User {
   id      String   @id @default(auto()) @map("_id") @db.ObjectId
   email   String   @unique
   name    String?
+  //highlight-next-line
   role    Role     @default(USER)
   posts   Post[]
   profile Profile?
@@ -1896,6 +1903,7 @@ model User {
 model User {
   id             Int      @id @default(autoincrement())
   posts          Post[]
+  //highlight-next-line
   favoriteColors String[] @default(["red", "yellow", "purple"])
   roles          Role[]   @default([USER, DEVELOPER])
 }
@@ -1914,6 +1922,7 @@ enum Role {
 model User {
   id             String   @id @default(auto()) @map("_id") @db.ObjectId
   posts          Post[]
+  //highlight-next-line
   favoriteColors String[] @default(["red", "yellow", "purple"])
   roles          Role[]   @default([USER, DEVELOPER])
 }
@@ -2776,6 +2785,7 @@ The following example demonstrates manually adding `@ignore` to exclude the `ema
 model User {
   id    Int    @id
   name  String
+  //highlight-next-line
   email String @ignore // this field will be excluded
 }
 ```
@@ -2799,6 +2809,7 @@ model Post {
   author   User @relation(fields: [authorId], references: [id])
   authorId Int
 
+  //highlight-next-line
   @@ignore
 }
 ```
@@ -2812,12 +2823,14 @@ model Post {
   author   User @relation(fields: [authorId], references: [id])
   authorId Int
 
+  //highlight-next-line
   @@ignore
 }
 
 model User {
   id    Int     @id @default(autoincrement())
   name  String?
+  //highlight-next-line
   posts Post[]  @ignore
 }
 ```
@@ -2858,12 +2871,14 @@ The name of the `name` argument on the `@@schema` attribute can be omitted
 ```prisma highlight=3,9,16;normal
 generator client {
   provider        = "prisma-client-js"
+  //highlight-next-line
   previewFeatures = ["multiSchema"]
 }
 
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
+  //highlight-next-line
   schemas  = ["auth"]
 }
 
@@ -2871,6 +2886,7 @@ model User {
   id   Int    @id @default(autoincrement())
   name String
 
+  //highlight-next-line
   @@schema("auth")
 }
 ```
@@ -3153,7 +3169,9 @@ You can also use `dbgenerated()` to set the default value for supported types. F
 
 ```prisma highlight=2;add|3;delete
 model User {
+  //add-next-line
   id   String  @id @default(dbgenerated("gen_random_uuid()")) @db.Uuid
+  //delete-next-line
   id   String  @id @default(uuid()) @db.Uuid
   test String?
 }
diff --git a/content/200-orm/500-reference/380-connection-urls.mdx b/content/200-orm/500-reference/380-connection-urls.mdx
index 8eaa7c3444..ee9b218d04 100644
--- a/content/200-orm/500-reference/380-connection-urls.mdx
+++ b/content/200-orm/500-reference/380-connection-urls.mdx
@@ -44,7 +44,7 @@ Here are examples for the connection URLs of the databases Prisma ORM supports:
 
 ### PostgreSQL
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = "postgresql://janedoe:mypassword@localhost:5432/mydb?schema=sample"
@@ -53,7 +53,7 @@ datasource db {
 
 ### MySQL
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "mysql"
   url      = "mysql://janedoe:mypassword@localhost:3306/mydb"
@@ -62,7 +62,7 @@ datasource db {
 
 ### Microsoft SQL Server
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "sqlserver"
   url      = "sqlserver://localhost:1433;initial catalog=sample;user=sa;password=mypassword;"
@@ -71,7 +71,7 @@ datasource db {
 
 ### SQLite
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "sqlite"
   url      = "file:./dev.db"
@@ -80,7 +80,7 @@ datasource db {
 
 ### CockroachDB
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "cockroachdb"
   url      = "postgresql://janedoe:mypassword@localhost:26257/mydb?schema=public"
@@ -89,7 +89,7 @@ datasource db {
 
 ### MongoDB
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "mongodb"
   url      = "mongodb+srv://root:<password>@cluster0.ab1cd.mongodb.net/myDatabase?retryWrites=true&w=majority"
@@ -100,7 +100,7 @@ datasource db {
 
 You can also provide the connection URL as an environment variable:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
diff --git a/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdx b/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdx
index c567110f4f..78eb12c2ed 100644
--- a/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdx
+++ b/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/700-upgrading-to-prisma-4.mdx
@@ -90,6 +90,7 @@ For database connectors that support scalar lists (PostgreSQL, CockroachDB and M
 model User {
   id             Int      @id @default(autoincrement())
   posts          Post[]
+  //highlight-next-line
   favoriteColors String[] @default(["red", "yellow", "purple"])
 }
 ```
@@ -101,6 +102,7 @@ model User {
 model User {
   id             String   @id @default(auto()) @map("_id") @db.ObjectId
   posts          Post[]
+  //highlight-next-line
   favoriteColors String[] @default(["red", "yellow", "purple"])
 }
 ```
@@ -258,7 +260,7 @@ After you upgrade to Prisma ORM 4, any one-to-one or one-to-many relations witho
 
 When using [implicit many-to-many relations](/orm/prisma-schema/data-model/relations/many-to-many-relations#implicit-many-to-many-relations) in Prisma ORM 4, you will no longer be able to use the `references` argument, which was previously optional. For example, the following relation would now trigger a validation error:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id         Int        @id @default(autoincrement())
   categories Category[] @relation("my-relation", references: [id]) // <-- validation error
@@ -272,7 +274,7 @@ model Category {
 
 Instead, you can write:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id         Int        @id @default(autoincrement())
   categories Category[] @relation("my-relation")
diff --git a/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/100-named-constraints.mdx b/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/100-named-constraints.mdx
index e1e3a6844e..68c2d8280c 100644
--- a/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/100-named-constraints.mdx
+++ b/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/100-named-constraints.mdx
@@ -69,6 +69,7 @@ To keep existing names, run `prisma db pull` against the target environment. Thi
      id         Int    @id @default(autoincrement())
      title      String
      authorName String @default("Anonymous")
+     //highlight-next-line
      author     User?  @relation(fields: [authorName], references: [name], map: "Custom_Foreign_Key_Constraint")
    }
    ```
@@ -132,6 +133,7 @@ model Post {
   id         Int    @id @default(autoincrement())
   title      String
   authorName String @default("Anonymous")
+  //highlight-next-line
   author     User?  @relation(fields: [authorName], references: [name], map: "Custom_Foreign_Key_Constraint")
 }
 ```
@@ -143,6 +145,7 @@ model Post {
   id         Int    @id @default(autoincrement())
   title      String
   authorName String @default("Anonymous")
+  //highlight-next-line
   author     User?  @relation(fields: [authorName], references: [name], map: "Custom_Production_Name")
 }
 ```
diff --git a/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/150-referential-actions.mdx b/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/150-referential-actions.mdx
index 2723182c45..d898c2b2d3 100644
--- a/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/150-referential-actions.mdx
+++ b/content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/800-upgrading-to-prisma-3/150-referential-actions.mdx
@@ -3,6 +3,7 @@ title: 'Referential actions upgrade path'
 metaTitle: 'Referential actions upgrade path'
 metaDescription: 'Guides on how to upgrade depending on your workflow using Prisma Introspect or Prisma Migrate'
 tocDepth: 4
+toc_max_heading_level: 4
 toc: true
 ---
 
@@ -75,6 +76,7 @@ The following example would result in a cascading delete, meaning that if the `U
 model Post {
   id       Int    @id @default(autoincrement())
   title    String
+  //add-next-line
   author   User   @relation(fields: [authorId], references: [id], onDelete: Cascade)
   authorId Int
 }
@@ -114,7 +116,7 @@ The following example uses the below blog schema with a 1-m relationship between
 
 This means that if a user has a post, that user (and their posts) **cannot** be deleted.
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id       Int    @id @default(autoincrement())
   title    String
@@ -182,7 +184,9 @@ async function main() {
     })
   } catch (error) {
     if (error instanceof Prisma.PrismaClientKnownRequestError) {
+      //delete-next-line
       if (error.code === 'P2014') {
+      //add-next-line
       if (error.code === 'P2003') {
         console.log(error.message)
       }
diff --git a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/02-schema-incompatibilities-mysql.mdx b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/02-schema-incompatibilities-mysql.mdx
index 62a4ff11eb..ba57193f81 100644
--- a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/02-schema-incompatibilities-mysql.mdx
+++ b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/02-schema-incompatibilities-mysql.mdx
@@ -45,7 +45,7 @@ CREATE TABLE "Post" (
 
 #### Result of introspection in Prisma ORM versions 2._x_ and later
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id        String  @id
   published Boolean
@@ -70,6 +70,7 @@ After this adjustment, you can re-introspect your database and the `@default` at
 ```prisma line-number file=schema.prisma highlight=3;normal
 model Post {
   id        String  @id
+  //highlight-next-line
   published Boolean @default(false)
 }
 ```
@@ -78,9 +79,10 @@ model Post {
 
 You can add the `@default` attribute to the Prisma model:
 
-```prisma line-number file=schema.prisma highlight=3;add
+```prisma line-number file=schema.prisma highlight=3;add showLineNumbers
 model Post {
   id        String
+  //add-next-line
   published Boolean @default(false)
 }
 ```
@@ -113,7 +115,7 @@ CREATE TABLE "Post" (
 
 #### Result of introspection in Prisma ORM versions 2._x_ and later
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id String @id
 }
@@ -125,8 +127,9 @@ Because there's no indication of the CUID behavior in the database, Prisma ORM's
 
 As a workaround, you can manually add the `@default(cuid())` attribute to the Prisma model:
 
-```prisma line-number file=schema.prisma highlight=2;add
+```prisma line-number file=schema.prisma highlight=2;add showLineNumbers
 model Post {
+  //add-next-line
   id String @id @default(cuid())
 }
 ```
@@ -163,7 +166,7 @@ CREATE TABLE "Post" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id        String   @id
   createdAt DateTime
@@ -183,7 +186,7 @@ ALTER TABLE "Post"
 
 After this adjustment, you can re-introspect your database and the `@default` attribute will be added to the `createdAt` field:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id        String
   createdAt DateTime @default(now())
@@ -194,9 +197,10 @@ model Post {
 
 As a workaround, you can manually add the `@default(now())` attribute to the Prisma model:
 
-```prisma line-number file=schema.prisma highlight=3;normal
+```prisma line-number file=schema.prisma highlight=3;normal showLineNumbers
 model Post {
   id        String   @id
+  //highlight-next-line
   createdAt DateTime @default(now())
 }
 ```
@@ -233,7 +237,7 @@ CREATE TABLE "Post" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id        String   @id
   updatedAt DateTime
@@ -246,9 +250,10 @@ model Post {
 
 As a workaround, you can manually add the `@updatedAt` attribute to the Prisma model:
 
-```prisma line-number file=schema.prisma highlight=3;add
+```prisma line-number file=schema.prisma highlight=3;add showLineNumbers
 model Post {
   id        String   @id
+  //add-next-line
   updatedAt DateTime @updatedAt
 }
 ```
@@ -299,7 +304,7 @@ CREATE TABLE "Profile" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id      String    @id
   Profile Profile[]
@@ -330,6 +335,7 @@ After this adjustment, you can re-introspect your database and the 1-1 relation
 ```prisma line-number file=schema.prisma highlight=3;normal
 model User {
   id      String   @id
+  //highlight-next-line
   Profile Profile?
 }
 
@@ -388,7 +394,7 @@ CREATE INDEX "_PostToUser_B" ON "_PostToUser"("B" text_ops);
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id   String @id
   Post Post[] @relation(references: [id])
@@ -426,16 +432,19 @@ As a workaround, you can migrate the data into a structure that's compatible wit
 
 After that you can introspect your database and the relation will now be recognized as 1-n:
 
-```prisma line-number file=schema.prisma highlight=3,8,9;normal
+```prisma line-number file=schema.prisma highlight=3,8,9;normal showLineNumbers
 model User {
   id   String @id
+  //highlight-next-line
   Post Post[]
 }
 
 model Post {
   id       String @id
+  //highlight-start
   User     User   @relation(fields: [authorId], references: [id])
   authorId String
+  //highlight-end
 }
 ```
 
@@ -467,7 +476,7 @@ CREATE TABLE "User" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id       String  @id
   jsonData String?
@@ -484,9 +493,10 @@ ALTER TABLE User MODIFY COLUMN jsonData JSON;
 
 After this adjustment, you can re-introspect your database and the field will now be recognized as `Json`:
 
-```prisma line-number file=schema.prisma highlight=3;normal
+```prisma line-number file=schema.prisma highlight=3;normal showLineNumbers
 model User {
   id       String @id
+  //highlight-next-line
   jsonData Json?
 }
 ```
@@ -524,7 +534,7 @@ CREATE TABLE "User" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id   String  @id
   role String?
@@ -547,16 +557,19 @@ You can manually turn the `role` column into an enum with your desired values:
 
 After introspection, the type is now properly recognized as an enum:
 
-```prisma line-number file=schema.prisma highlight=3,6-9;normal
+```prisma line-number file=schema.prisma highlight=3,6-9;normal showLineNumbers
 model User {
   id   String @id
+  //highlight-next-line
   role Role?
 }
 
+//highlight-start
 enum Role {
   ADMIN
   CUSTOMER
 }
+//highlight-end
 ```
 
 ## Mismatching CUID length
@@ -585,7 +598,7 @@ CREATE TABLE "User" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id String @id
 }
@@ -642,7 +655,7 @@ CREATE UNIQUE INDEX "User_coinflips_pkey" ON "User_coinflips"("nodeId" text_ops,
 
 #### Result of Prisma ORM 2 introspection
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id             String           @id
   User_coinflips User_coinflips[]
@@ -742,7 +755,7 @@ However, in order to do so you need to manually migrate the underlying data from
 
 You can now introspect your database and the `coinflips` field will be represented as an array in your new Prisma schema:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id        String    @id
   coinflips Boolean[]
diff --git a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/02-schema-incompatibilities-postgresql.mdx b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/02-schema-incompatibilities-postgresql.mdx
index c759998b1c..1b5e76e22b 100644
--- a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/02-schema-incompatibilities-postgresql.mdx
+++ b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/02-schema-incompatibilities-postgresql.mdx
@@ -44,7 +44,7 @@ CREATE TABLE "Post" (
 
 #### Result of introspection in Prisma ORM versions 2._x_ and later
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id        String  @id
   published Boolean
@@ -66,9 +66,10 @@ ALTER TABLE "Post"
 
 After this adjustment, you can re-introspect your database and the `@default` attribute will be added to the `published` field:
 
-```prisma line-number file=schema.prisma highlight=3;normal
+```prisma line-number file=schema.prisma highlight=3;normal showLineNumbers
 model Post {
   id        String  @id
+  //highlight-next-line
   published Boolean @default(false)
 }
 ```
@@ -77,9 +78,10 @@ model Post {
 
 You can add the `@default` attribute to the Prisma model:
 
-```prisma line-number file=schema.prisma highlight=3;add
+```prisma line-number file=schema.prisma highlight=3;add showLineNumbers
 model Post {
   id        String
+  //add-next-line
   published Boolean @default(false)
 }
 ```
@@ -112,7 +114,7 @@ CREATE TABLE "Post" (
 
 #### Result of introspection in Prisma ORM versions 2._x_ and later
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id String @id
 }
@@ -124,8 +126,9 @@ Because there's no indication of the CUID behavior in the database, Prisma ORM's
 
 As a workaround, you can manually add the `@default(cuid())` attribute to the Prisma model:
 
-```prisma line-number file=schema.prisma highlight=2;add
+```prisma line-number file=schema.prisma highlight=2;add showLineNumbers
 model Post {
+  //add-next-line
   id String @id @default(cuid())
 }
 ```
@@ -162,7 +165,7 @@ CREATE TABLE "Post" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id        String   @id
   createdAt DateTime
@@ -182,7 +185,7 @@ ALTER TABLE "Post"
 
 After this adjustment, you can re-introspect your database and the `@default` attribute will be added to the `createdAt` field:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id        String
   createdAt DateTime @default(now())
@@ -196,6 +199,7 @@ As a workaround, you can manually add the `@default(now())` attribute to the Pri
 ```prisma line-number file=schema.prisma highlight=3;normal
 model Post {
   id        String   @id
+  //highlight-next-line
   createdAt DateTime @default(now())
 }
 ```
@@ -232,7 +236,7 @@ CREATE TABLE "Post" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model Post {
   id        String   @id
   updatedAt DateTime
@@ -248,6 +252,7 @@ As a workaround, you can manually add the `@updatedAt` attribute to the Prisma m
 ```prisma line-number file=schema.prisma highlight=3;add
 model Post {
   id        String   @id
+  //add-next-line
   updatedAt DateTime @updatedAt
 }
 ```
@@ -298,7 +303,7 @@ CREATE TABLE "Profile" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id      String    @id
   Profile Profile[]
@@ -329,6 +334,7 @@ After this adjustment, you can re-introspect your database and the 1-1 relation
 ```prisma line-number file=schema.prisma highlight=3;normal
 model User {
   id      String   @id
+  //highlight-next-line
   Profile Profile?
 }
 
@@ -387,7 +393,7 @@ CREATE INDEX "_PostToUser_B" ON "_PostToUser"("B" text_ops);
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id   String @id
   Post Post[] @relation(references: [id])
@@ -432,13 +438,16 @@ After that you can introspect your database and the relation will now be recogni
 ```prisma line-number file=schema.prisma highlight=3,8,9;normal
 model User {
   id   String @id
+  //highlight-next-line
   Post Post[]
 }
 
 model Post {
   id       String @id
+  //highlight-start
   User     User   @relation(fields: [authorId], references: [id])
   authorId String
+  //highlight-end
 }
 ```
 
@@ -470,7 +479,7 @@ CREATE TABLE "User" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id       String  @id
   jsonData String?
@@ -487,9 +496,10 @@ ALTER TABLE "User" ALTER COLUMN "jsonData" TYPE JSON  USING "jsonData"::json;
 
 After this adjustment, you can re-introspect your database and the field will now be recognized as `Json`:
 
-```prisma line-number file=schema.prisma highlight=3;normal
+```prisma line-number file=schema.prisma highlight=3;normal showLineNumbers
 model User {
   id       String @id
+  //highlight-next-line
   jsonData Json?
 }
 ```
@@ -527,7 +537,7 @@ CREATE TABLE "User" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id   String  @id
   role String?
@@ -550,16 +560,19 @@ You can manually turn the `role` column into an enum with your desired values:
 
 After introspection, the type is now properly recognized as an enum:
 
-```prisma line-number file=schema.prisma highlight=3,6-9;normal
+```prisma line-number file=schema.prisma highlight=3,6-9;normal showLineNumbers
 model User {
   id   String @id
+  //highlight-next-line
   role Role?
 }
 
+//highlight-start
 enum Role {
   ADMIN
   CUSTOMER
 }
+//highlight-end
 ```
 
 ## Mismatching CUID length
@@ -588,7 +601,7 @@ CREATE TABLE "User" (
 
 #### Result of introspection in Prisma ORM 2._x_ and later versions
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id String @id
 }
@@ -643,7 +656,7 @@ CREATE UNIQUE INDEX "User_coinflips_pkey" ON "User_coinflips"("nodeId" text_ops,
 
 #### Result of Prisma ORM 2 introspection
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id             String           @id
   User_coinflips User_coinflips[]
@@ -743,7 +756,7 @@ However, in order to do so you need to manually migrate the underlying data from
 
 You can now introspect your database and the `coinflips` field will be represented as an array in your new Prisma schema:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id        String    @id
   coinflips Boolean[]
diff --git a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-mysql.mdx b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-mysql.mdx
index 122e65b780..4641276b8d 100644
--- a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-mysql.mdx
+++ b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-mysql.mdx
@@ -146,7 +146,7 @@ The command created a new folder called `prisma`, and two files:
 
 Your initial Prisma schema looks as follows:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 // This is your Prisma schema file,
 // learn more about it in the docs: https://pris.ly/d/prisma-schema
 
@@ -366,7 +366,7 @@ Here's a graphical illustration for what happens when `db pull` is invoked:
 
 For the above Prisma 1 datamodel, this results in the following Prisma ORM 2 schema (note that the models have been reordered to match the initial order of the Prisma 1 datamodel):
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id       String    @id @default(cuid())
   email    String?   @unique
@@ -773,7 +773,7 @@ npx prisma db pull
 
 This time, the resulting Prisma schema looks as follows:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id       String   @id
   name     String
@@ -928,7 +928,7 @@ https://pris.ly/d/upgrade-from-prisma-1
 
 The final version of the Prisma schema should look as follows:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id       String   @id @default(cuid())
   name     String
@@ -974,7 +974,7 @@ enum Role {
 
 One thing you'll notice with this version of the Prisma ORM 2 schema is that all [relation fields](/orm/prisma-schema/data-model/relations#relation-fields) are named after their respective models, e.g:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   Post    Post[]
   Profile Profile?
@@ -1000,7 +1000,7 @@ Because all relation fields are _virtual_, meaning they don't _manifest_ in the
 
 Here's what they look like after the rename:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   posts   Post[]
   profile Profile?
diff --git a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-postgresql.mdx b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-postgresql.mdx
index d5df4f4820..2385ebab49 100644
--- a/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-postgresql.mdx
+++ b/content/200-orm/800-more/300-upgrade-guides/800-upgrade-from-prisma-1/03-upgrading-the-prisma-layer-postgresql.mdx
@@ -145,7 +145,7 @@ The command created a new folder called `prisma`, and two files:
 
 Your initial Prisma schema looks as follows:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 // This is your Prisma schema file,
 // learn more about it in the docs: https://pris.ly/d/prisma-schema
 
@@ -365,7 +365,7 @@ Here's a graphical illustration for what happens when `db pull` is invoked:
 
 For the above Prisma 1 datamodel, this results in the following Prisma ORM 2 schema (note that the models have been reordered to match the initial order of the Prisma 1 datamodel):
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id       String    @id @default(cuid())
   email    String?   @unique
@@ -783,7 +783,7 @@ npx prisma db pull
 
 This time, the resulting Prisma schema looks as follows:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id       String   @id
   name     String
@@ -938,7 +938,7 @@ https://pris.ly/d/upgrade-from-prisma-1
 
 The final version of the Prisma schema should look as follows:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   id       String   @id @default(cuid())
   name     String
@@ -984,7 +984,7 @@ enum Role {
 
 One thing you'll notice with this version of the Prisma ORM 2 schema is that all [relation fields](/orm/prisma-schema/data-model/relations#relation-fields) are named after their respective models, e.g:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   Post    Post[]
   Profile Profile?
@@ -1010,7 +1010,7 @@ Because all relation fields are _virtual_, meaning they don't _manifest_ in the
 
 Here's what they look like after the rename:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 model User {
   posts   Post[]
   profile Profile?
diff --git a/content/200-orm/800-more/450-migrating-to-prisma/01-migrate-from-typeorm.mdx b/content/200-orm/800-more/450-migrating-to-prisma/01-migrate-from-typeorm.mdx
index 11bb4cf53a..ee6daa8a59 100644
--- a/content/200-orm/800-more/450-migrating-to-prisma/01-migrate-from-typeorm.mdx
+++ b/content/200-orm/800-more/450-migrating-to-prisma/01-migrate-from-typeorm.mdx
@@ -265,7 +265,7 @@ This command created a new directory called `prisma` with the following files fo
 
 The Prisma schema file currently looks as follows:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 // This is your Prisma schema file,
 // learn more about it in the docs: https://pris.ly/d/prisma-schema
 
@@ -449,7 +449,7 @@ npx prisma db pull
 
 This creates the following Prisma models:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model typeorm_migrations {
   id        Int    @id @default(autoincrement())
   timestamp Int
@@ -554,7 +554,7 @@ You can further completely remove model that represents the TypeORM migrations t
 
 Here's an adjusted version of the Prisma schema that addresses these points:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Category {
   id                Int                @id @default(autoincrement())
   name              String
@@ -627,7 +627,7 @@ touch src/prisma.ts
 
 Now, instantiate `PrismaClient` and export it from the file so you can use it in your route handlers later:
 
-```ts copy file=src/prisma.ts
+```ts copy file=src/prisma.ts showLineNumbers
 import { PrismaClient } from '@prisma/client'
 
 export const prisma = new PrismaClient()
@@ -647,7 +647,7 @@ Let's dive into the route handlers that implement these requests.
 
 The `/feed` handler is currently implemented as follows:
 
-```ts file=src/controllers/FeedAction.ts
+```ts file=src/controllers/FeedAction.ts showLineNumbers
 import { getManager } from 'typeorm'
 import { Post } from '../entity/Post'
 
@@ -667,7 +667,7 @@ Note that each returned `Post` object includes the relation to the `author` it's
 
 Here is how the same route is implemented using Prisma Client:
 
-```ts file=src/controllers/FeedAction.ts
+```ts file=src/controllers/FeedAction.ts showLineNumbers
 import { prisma } from '../prisma'
 
 export async function feedAction(req, res) {
@@ -686,7 +686,7 @@ Note that the way how Prisma Client includes the `author` relation is absolutely
 
 The `/filterPosts` handler is currently implemented as follows:
 
-```ts file=src/controllers/FilterPostsActions.ts
+```ts file=src/controllers/FilterPostsActions.ts showLineNumbers
 import { getManager, Like } from 'typeorm'
 import { Post } from '../entity/Post'
 
@@ -707,7 +707,7 @@ export async function filterPostsAction(req, res) {
 
 With Prisma ORM, the route is implemented as follows:
 
-```ts file=src/controllers/FilterPostsActions.ts
+```ts file=src/controllers/FilterPostsActions.ts showLineNumbers
 import { prisma } from '../prisma'
 
 export async function filterPostsAction(req, res) {
@@ -736,7 +736,7 @@ Note that TypeORM by default combines several `where` conditions with an implici
 
 The `/post/:postId` handler is currently implemented as follows:
 
-```ts file=src/controllers/GetPostByIdAction.ts
+```ts file=src/controllers/GetPostByIdAction.ts showLineNumbers
 import { getManager } from 'typeorm'
 import { Post } from '../entity/Post'
 
@@ -752,7 +752,7 @@ export async function getPostByIdAction(req, res) {
 
 With Prisma ORM, the route is implemented as follows:
 
-```ts file=src/controllers/GetPostByIdAction.ts
+```ts file=src/controllers/GetPostByIdAction.ts showLineNumbers
 import { prisma } from '../prisma'
 
 export async function getPostByIdAction(req, res) {
@@ -778,7 +778,7 @@ The REST API has three routes that accept `POST` requests:
 
 The `/user` handler is currently implemented as follows:
 
-```ts file=src/controllers/CreateUserAction.ts
+```ts file=src/controllers/CreateUserAction.ts showLineNumbers
 import { getManager } from 'typeorm'
 import { User } from '../entity/User'
 
@@ -798,7 +798,7 @@ export async function createUserAction(req, res) {
 
 With Prisma ORM, the route is implemented as follows:
 
-```ts file=src/controllers/CreateUserAction.ts
+```ts file=src/controllers/CreateUserAction.ts showLineNumbers 
 import { prisma } from '../prisma'
 
 export async function createUserAction(req, res) {
@@ -844,7 +844,7 @@ export async function createDraftAction(req, res) {
 
 With Prisma ORM, the route is implemented as follows:
 
-```ts file=src/controllers/CreateDraftAction.ts
+```ts file=src/controllers/CreateDraftAction.ts showLineNumbers
 import { prisma } from '../prisma'
 
 export async function createDraftAction(req, res) {
@@ -870,7 +870,7 @@ Note that Prisma Client's nested write here save an initial query where first th
 
 The `/user/:userId/profile` handler is currently implemented as follows:
 
-```ts file=src/controllers/SetBioForUserAction.ts.ts
+```ts file=src/controllers/SetBioForUserAction.ts.ts showLineNumbers
 import { getManager } from 'typeorm'
 import { Profile } from '../entity/Profile'
 import { User } from '../entity/User'
@@ -895,7 +895,7 @@ export async function setBioForUserAction(req, res) {
 
 With Prisma ORM, the route is implemented as follows:
 
-```ts file=src/controllers/SetBioForUserAction.ts.ts
+```ts file=src/controllers/SetBioForUserAction.ts.ts showLineNumbers
 import { prisma } from '../prisma'
 
 export async function setBioForUserAction(req, res) {
@@ -929,7 +929,7 @@ Let's dive into the route handlers that implement these requests.
 
 The `/addPostToCategory?postId=POST_ID&categoryId=CATEGORY_ID` handler is currently implemented as follows:
 
-```ts file=src/controllers/AddPostToCategoryAction.ts
+```ts file=src/controllers/AddPostToCategoryAction.ts showLineNumbers
 import { getManager } from 'typeorm'
 import { Post } from '../entity/Post'
 import { Category } from '../entity/Category'
@@ -954,7 +954,7 @@ export async function addPostToCategoryAction(req, res) {
 
 With Prisma ORM, the route is implemented as follows:
 
-```ts file=src/controllers/AddPostToCategoryAction.ts
+```ts file=src/controllers/AddPostToCategoryAction.ts showLineNumbers
 import { prisma } from '../prisma'
 
 export async function addPostToCategoryAction(req, res) {
@@ -981,7 +981,7 @@ export async function addPostToCategoryAction(req, res) {
 
 Note that this Prisma Client can be made less verbose by modeling the relation as an [implicit many-to-many relation](#implicit-many-to-many-relations) instead. In that case, the query would look as follows:
 
-```ts file=src/controllers/AddPostToCategoryAction.ts
+```ts file=src/controllers/AddPostToCategoryAction.ts showLineNumbers
 const post = await prisma.post.update({
   data: {
     categories: {
diff --git a/content/200-orm/800-more/450-migrating-to-prisma/02-migrate-from-sequelize.mdx b/content/200-orm/800-more/450-migrating-to-prisma/02-migrate-from-sequelize.mdx
index b8c31fe045..32121b6e6a 100644
--- a/content/200-orm/800-more/450-migrating-to-prisma/02-migrate-from-sequelize.mdx
+++ b/content/200-orm/800-more/450-migrating-to-prisma/02-migrate-from-sequelize.mdx
@@ -195,7 +195,7 @@ This command created a new directory called `prisma` with the following files fo
 
 The Prisma schema file currently looks as follows:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 // This is your Prisma schema file,
 // learn more about it in the docs: https://pris.ly/d/prisma-schema
 
@@ -367,7 +367,7 @@ npx prisma db pull
 
 This creates the following Prisma models:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Categories {
   id             Int              @id @default(autoincrement())
   name           String
@@ -463,7 +463,7 @@ Therefore, you'll add `@default(now())` and `@updatedAt` attributes to the `crea
 To learn more how Prisma ORM does this, you can read more [`@default(now())`](/orm/reference/prisma-schema-reference#now) and [`@updatedAt`](/orm/reference/prisma-schema-reference#updatedat) here.
 Our updated schema will be as follows:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 model Categories {
   id             Int              @id @default(autoincrement())
   name           String
@@ -538,7 +538,7 @@ Sequelize generates a `SequelizeMeta` model that is used internally by the libra
 
 Here's an adjusted version of the Prisma schema that addresses these points:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 generator client {
   provider = "prisma-client-js"
 }
diff --git a/content/200-orm/800-more/450-migrating-to-prisma/03-migrate-from-mongoose.mdx b/content/200-orm/800-more/450-migrating-to-prisma/03-migrate-from-mongoose.mdx
index 3319623f57..c3a17fb6b9 100644
--- a/content/200-orm/800-more/450-migrating-to-prisma/03-migrate-from-mongoose.mdx
+++ b/content/200-orm/800-more/450-migrating-to-prisma/03-migrate-from-mongoose.mdx
@@ -172,7 +172,7 @@ This command creates:
 
 The Prisma schema file currently looks as follows:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 // This is your Prisma schema file,
 // learn more about it in the docs: https://pris.ly/d/prisma-schema
 
@@ -216,7 +216,7 @@ npx prisma db pull
 
 This creates the following Prisma models:
 
-```prisma file=prisma/schema.prisma
+```prisma file=prisma/schema.prisma showLineNumbers
 type UsersProfile {
   bio String
 }
@@ -394,7 +394,7 @@ model users {
 
 <TabItem value="schema.prisma">
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma 
 type UsersProfile {
   bio String
 }
@@ -475,27 +475,34 @@ datasource db {
   url      = env("DATABASE_URL")
 }
 
+//highlight-next-line
 type Profile {
   bio String
 }
 
+//highlight-next-line
 model Category {
   id   String @id @default(auto()) @map("_id") @db.ObjectId
   name String
+  //highlight-next-line
   v    Int    @default(0) @map("__v") @ignore
 
   posts    Post[]   @relation(fields: [post_ids], references: [id])
   post_ids String[] @db.ObjectId
 
+  //highlight-next-line
   @@map("categories")
 }
 
+//highlight-next-line
 model Post {
   id        String  @id @default(auto()) @map("_id") @db.ObjectId
   title     String
   content   String
+  //highlight-start
   published Boolean @default(false)
   v         Int     @default(0) @map("__v") @ignore
+  //highlight-end
 
   author   User   @relation(fields: [authorId], references: [id])
   authorId String @map("author") @db.ObjectId
@@ -503,17 +510,22 @@ model Post {
   categories  Category[] @relation(fields: [categoryIds], references: [id])
   categoryIds String[]   @db.ObjectId
 
+  //highlight-next-line
   @@map("posts")
 }
 
+//highlight-next-line
 model User {
   id      String   @id @default(auto()) @map("_id") @db.ObjectId
+  //highlight-next-line
   v       Int      @default(0) @map("__v") @ignore
   email   String   @unique(map: "email_1")
   name    String
+  //highlight-next-line
   profile Profile?
   posts   Post[]
 
+  //highlight-next-line
   @@map("users")
 }
 ```
diff --git a/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/600-vercel-caching-issue.mdx b/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/600-vercel-caching-issue.mdx
index 84c307f1db..3cfc3bb105 100644
--- a/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/600-vercel-caching-issue.mdx
+++ b/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/600-vercel-caching-issue.mdx
@@ -66,6 +66,7 @@ Within the `scripts` section of your project's `package.json` file, if there is
 {
   ...
   "scripts" {
+    //add-next-line
     "postinstall": "prisma generate"
   }
   ...
@@ -80,6 +81,7 @@ Within the `scripts` section of your project's `package.json` file, within the `
 {
   ...
   "scripts" {
+    //add-next-line
     "build": "prisma generate && <actual-build-command>"
   }
   ...
diff --git a/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/700-netlify-caching-issue.mdx b/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/700-netlify-caching-issue.mdx
index 64a47dba88..ddcc62a177 100644
--- a/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/700-netlify-caching-issue.mdx
+++ b/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/700-netlify-caching-issue.mdx
@@ -66,6 +66,7 @@ Within the `scripts` section of your project's `package.json` file, if there is
 {
   ...
   "scripts" {
+    //add-next-line
     "postinstall": "prisma generate"
   }
   ...
@@ -80,6 +81,7 @@ Within the `scripts` section of your project's `package.json` file, within the `
 {
   ...
   "scripts" {
+    //add-next-line
     "build": "prisma generate && <actual-build-command>"
   }
   ...
diff --git a/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/800-check-constraints.mdx b/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/800-check-constraints.mdx
index 4d4c4bb4dd..3306f7dde6 100644
--- a/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/800-check-constraints.mdx
+++ b/content/200-orm/800-more/600-help-and-troubleshooting/100-help-articles/800-check-constraints.mdx
@@ -256,7 +256,7 @@ In order to introspect your database, you need to tell Prisma ORM how to connect
 
 Create a new file named `schema.prisma` and add the following code to it:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 datasource db {
   provider = "postgresql"
   url      = env("DATABASE_URL")
@@ -285,7 +285,7 @@ npx prisma db pull
 
 This command introspects your database and for each table adds a Prisma model to the Prisma schema:
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 generator client {
   provider = "prisma-client-js"
 }
@@ -325,7 +325,7 @@ To validate whether the check constraints work, you'll now generate Prisma Clien
 
 First, add a `generator` block to your Prisma schema (typically added right below the `datasource` block):
 
-```prisma file=schema.prisma
+```prisma file=schema.prisma showLineNumbers
 generator client {
   provider = "prisma-client-js"
 }
diff --git a/content/300-accelerate/200-getting-started.mdx b/content/300-accelerate/200-getting-started.mdx
index 822efadae2..f4c5fad94f 100644
--- a/content/300-accelerate/200-getting-started.mdx
+++ b/content/300-accelerate/200-getting-started.mdx
@@ -61,7 +61,7 @@ As of Prisma version `5.2.0` you can use Prisma Studio with the Accelerate conne
 
 </Admonition>
 
-```env file=.env highlight=3;add
+```env file=.env highlight=3;add showLineNumbers
 DATABASE_URL="prisma://accelerate.prisma-data.net/?api_key=__API_KEY__"
 DIRECT_DATABASE_URL="postgresql://user:password@host:port/db_name?schema=public"
 ```
@@ -72,6 +72,7 @@ Then in your Prisma schema's `datasource` block add a field named `directUrl` wi
 datasource db {
   provider  = "postgresql"
   url       = env("DATABASE_URL")
+  //add-next-line
   directUrl = env("DIRECT_DATABASE_URL")
 }
 ```
diff --git a/content/400-pulse/400-api-reference.mdx b/content/400-pulse/400-api-reference.mdx
index bdc31b28ee..1f2ecb8e4e 100644
--- a/content/400-pulse/400-api-reference.mdx
+++ b/content/400-pulse/400-api-reference.mdx
@@ -3,6 +3,7 @@ title: 'API Reference'
 metaTitle: 'Pulse: API Reference'
 metaDescription: 'API reference documentation for Pulse.'
 tocDepth: 4
+toc_max_heading_level: 4
 toc: true
 ---
 
diff --git a/content/500-platform/20-concepts/index.mdx b/content/500-platform/20-concepts/index.mdx
index 2e7d356a90..c9e138a52b 100644
--- a/content/500-platform/20-concepts/index.mdx
+++ b/content/500-platform/20-concepts/index.mdx
@@ -2,7 +2,6 @@
 title: 'Concepts'
 metaTitle: 'Platform Console: Concepts'
 metaDescription: ''
-tocDepth: 4
 hide_table_of_contents: true
 ---
 
diff --git a/content/600-about/200-prisma-docs/20-style-guide/01-writing-style.mdx b/content/600-about/200-prisma-docs/20-style-guide/01-writing-style.mdx
index 299e0a0073..9dde9725ec 100644
--- a/content/600-about/200-prisma-docs/20-style-guide/01-writing-style.mdx
+++ b/content/600-about/200-prisma-docs/20-style-guide/01-writing-style.mdx
@@ -3,6 +3,7 @@ title: 'Writing style'
 metaTitle: 'Prisma docs style guide: writing style'
 metaDescription: 'This section of the style guide provides guidelines on tone of voice, audience, and other tonal matters.'
 tocDepth: 4
+toc_max_heading_level: 4
 search: false
 ---
 
diff --git a/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx b/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx
index d2244e84b8..2265012612 100644
--- a/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx
+++ b/content/600-about/200-prisma-docs/20-style-guide/02-word-choice.mdx
@@ -3,6 +3,7 @@ title: 'Word choice'
 metaTitle: 'Prisma docs style guide: word choice'
 metaDescription: 'This section of the style guide provides guidelines on what terms and phrase constructions to use.'
 tocDepth: 4
+toc_max_heading_level: 4
 search: false
 ---
 
diff --git a/content/600-about/200-prisma-docs/20-style-guide/03-spelling-punctuation-formatting.mdx b/content/600-about/200-prisma-docs/20-style-guide/03-spelling-punctuation-formatting.mdx
index fa8d8780be..6f601b4edd 100644
--- a/content/600-about/200-prisma-docs/20-style-guide/03-spelling-punctuation-formatting.mdx
+++ b/content/600-about/200-prisma-docs/20-style-guide/03-spelling-punctuation-formatting.mdx
@@ -3,6 +3,7 @@ title: 'Spelling, punctuation, and formatting'
 metaTitle: 'Prisma docs style guide: spelling, punctuation, and formatting'
 metaDescription: 'This section of the style guide provides guidelines on how to present the information you add.'
 tocDepth: 4
+toc_max_heading_level: 4
 search: false
 ---
 
@@ -173,6 +174,7 @@ Use the [`highlight` property](/about/prisma-docs/docs-components/mdx-examples#c
 ```prisma highlight=3;normal
 generator client {
   provider        = "prisma-client-js"
+  //highlight-next-line
   previewFeatures = ["namedConstraints"]
 }
 ```
diff --git a/content/600-about/200-prisma-docs/20-style-guide/05-prisma-product-names.mdx b/content/600-about/200-prisma-docs/20-style-guide/05-prisma-product-names.mdx
index 2b7d89b099..b71480a1fe 100644
--- a/content/600-about/200-prisma-docs/20-style-guide/05-prisma-product-names.mdx
+++ b/content/600-about/200-prisma-docs/20-style-guide/05-prisma-product-names.mdx
@@ -3,6 +3,7 @@ title: 'Prisma product and component names'
 metaTitle: 'Prisma docs style guide: Prisma product and component names'
 metaDescription: 'This section of the style guide provides guidelines on how to refer to Prisma products and components.'
 tocDepth: 4
+toc_max_heading_level: 4
 search: false
 ---
 
diff --git a/content/600-about/200-prisma-docs/20-style-guide/06-image-guidelines.mdx b/content/600-about/200-prisma-docs/20-style-guide/06-image-guidelines.mdx
index 3a9f795606..6a2202f2da 100644
--- a/content/600-about/200-prisma-docs/20-style-guide/06-image-guidelines.mdx
+++ b/content/600-about/200-prisma-docs/20-style-guide/06-image-guidelines.mdx
@@ -3,6 +3,7 @@ title: 'Prisma docs image guidelines'
 metaTitle: 'Prisma docs style guide: image guidelines'
 metaDescription: 'This page provides guidelines for images in our docs.'
 tocDepth: 4
+toc_max_heading_level: 4
 search: false
 ---
 
diff --git a/content/600-about/200-prisma-docs/20-style-guide/10-boilerplate-content.mdx b/content/600-about/200-prisma-docs/20-style-guide/10-boilerplate-content.mdx
index 9e30090ade..935d141dc3 100644
--- a/content/600-about/200-prisma-docs/20-style-guide/10-boilerplate-content.mdx
+++ b/content/600-about/200-prisma-docs/20-style-guide/10-boilerplate-content.mdx
@@ -24,6 +24,7 @@ To enable this feature, add `namedConstraints` to `previewFeatures` in your sche
 ```prisma highlight=3;normal
 generator client {
   provider        = "prisma-client-js"
+  //highlight-next-line
   previewFeatures = ["namedConstraints"]
 }
 ```
diff --git a/content/600-about/200-prisma-docs/20-style-guide/index.mdx b/content/600-about/200-prisma-docs/20-style-guide/index.mdx
index 74d2fef0fc..6c879669ee 100644
--- a/content/600-about/200-prisma-docs/20-style-guide/index.mdx
+++ b/content/600-about/200-prisma-docs/20-style-guide/index.mdx
@@ -3,6 +3,7 @@ title: 'Prisma docs style guide'
 metaTitle: 'Prisma documentation style guide'
 metaDescription: 'The Prisma style guide provides contributor guidelines for the Prisma docs.'
 tocDepth: 4
+toc_max_heading_level: 4
 hidePage: false
 ---
 
diff --git a/content/600-about/200-prisma-docs/30-docs-components/index.mdx b/content/600-about/200-prisma-docs/30-docs-components/index.mdx
index e3c72cbe8f..d9c52b7ecf 100644
--- a/content/600-about/200-prisma-docs/30-docs-components/index.mdx
+++ b/content/600-about/200-prisma-docs/30-docs-components/index.mdx
@@ -2,7 +2,6 @@
 title: 'Prisma docs components'
 metaTitle: 'Prisma documentation components'
 metaDescription: 'This section describes the Prisma docs file format.'
-tocDepth: 4
 search: false
 hide_table_of_contents: true
 ---
diff --git a/docusaurus.config.ts b/docusaurus.config.ts
index bbf3f1d447..a2bdf1a679 100644
--- a/docusaurus.config.ts
+++ b/docusaurus.config.ts
@@ -451,9 +451,9 @@ const config: Config = {
       magicComments: [
         // Remember to extend the default highlight class name as well!
         {
-          className: 'theme-code-block-highlighted-line highlighted-line code-highlight',
-          line: 'highlight-next-line',
-          block: { start: 'highlight-start', end: 'highlight-end' },
+          className: 'theme-code-block-added-line added-line code-highlight',
+          line: 'add-next-line',
+          block: {start: 'add-start', end: 'add-end'},
         },
         {
           className: 'theme-code-block-deleted-line deleted-line code-highlight',
@@ -464,6 +464,11 @@ const config: Config = {
           className: 'theme-code-block-edited-line edited-line code-highlight',
           line: 'edit-next-line',
           block: { start: 'edit-start', end: 'edit-end' },
+        },
+        {
+          className: 'theme-code-block-highlighted-line highlighted-line',
+          line: 'highlight-next-line',
+          block: { start: 'highlight-start', end: 'highlight-end' },
         }
       ]
     },
diff --git a/src/css/custom.css b/src/css/custom.css
index 266735ceda..0614b16f38 100644
--- a/src/css/custom.css
+++ b/src/css/custom.css
@@ -818,8 +818,11 @@ hr {
   max-width: 100%;
 }
 
+.tabs-container > div:has(.code-children) {
+  padding: 16px 0 0 0;
+}
+
 .tabs-container .theme-code-block pre {
-  padding: 0 !important;
 }
 
 :root[data-theme='light'] .tabs-container > div {
diff --git a/src/css/theming.css b/src/css/theming.css
index 8cdb0e97c1..a086e510aa 100644
--- a/src/css/theming.css
+++ b/src/css/theming.css
@@ -33,9 +33,10 @@
   --ifm-card-background-color: white;
   --ifm-link-hover-color: #2E5297;
   --code-bg: var(--gray-200);
-  --docusaurus-highlighted-code-line-bg: rgba(71, 187, 120, 0.1);
+  --docusaurus-added-code-line-bg: rgba(71, 187, 120, 0.1);
   --docusaurus-deleted-code-line-bg: rgba(229, 62, 62, 0.1);
   --docusaurus-edited-code-line-bg: rgba(10, 104, 255, 0.2);
+  --docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.1);
 
   --ifm-btn-border-color-active: #718096;
   --ifm-btn-border-color: #E2E8F0;
@@ -138,7 +139,7 @@
   }
 }
 :root[data-theme='light'] {
-  --docusaurus-highlighted-code-line-bg: rgba(71, 187, 120, 0.1);
+  --docusaurus-added-code-line-bg: rgba(71, 187, 120, 0.1);
   --docusaurus-deleted-code-line-bg: rgba(229, 62, 62, 0.1);
   --docusaurus-edited-code-line-bg: rgba(10, 104, 255, 0.2);
 }
diff --git a/src/theme/CodeBlock/Container/styles.module.scss b/src/theme/CodeBlock/Container/styles.module.scss
index 4305ad4646..5671ed5ae7 100644
--- a/src/theme/CodeBlock/Container/styles.module.scss
+++ b/src/theme/CodeBlock/Container/styles.module.scss
@@ -27,6 +27,7 @@
   pre {
     background: transparent !important;
     padding-top: 0 !important;
+    padding-bottom: var(--ifm-pre-padding) !important;
   }
 }
 
diff --git a/src/theme/CodeBlock/Line/index.tsx b/src/theme/CodeBlock/Line/index.tsx
index 16f63ce065..247372933b 100644
--- a/src/theme/CodeBlock/Line/index.tsx
+++ b/src/theme/CodeBlock/Line/index.tsx
@@ -20,7 +20,7 @@ export default function CodeBlockLine({
   ));
   const highlightedLine = classNames?.find((e:string) => e.includes("code-highlight"))
   return (
-    <span {...lineProps}>
+    <span {...lineProps} className={!showLineNumbers ? styles.noLineNumbers : lineProps.className ? lineProps.className : ``}>
       {showLineNumbers ? (
         <>
           <span className={styles.codeLineContent}>
diff --git a/src/theme/CodeBlock/Line/styles.module.css b/src/theme/CodeBlock/Line/styles.module.css
index 408f6988b3..c31538841d 100644
--- a/src/theme/CodeBlock/Line/styles.module.css
+++ b/src/theme/CodeBlock/Line/styles.module.css
@@ -1,20 +1,13 @@
 /* Intentionally has zero specificity, so that to be able to override
 the background in custom CSS file due bug https://github.com/facebook/docusaurus/issues/3678 */
-:where(:root) {
-  --docusaurus-highlighted-code-line-bg: rgb(72 77 91);
-}
-
-:where([data-theme='dark']) {
-  --docusaurus-highlighted-code-line-bg: rgb(100 100 100);
-}
 
-:global(.theme-code-block-highlighted-line) {
-  background-color: var(--docusaurus-highlighted-code-line-bg);
+:global(.theme-code-block-added-line) {
+  background-color: var(--docusaurus-added-code-line-bg);
   display: block;
   padding: 0 var(--ifm-pre-padding) 0 42px;
   position: relative;
 }
-:global(.theme-code-block-highlighted-line)::before {
+:global(.theme-code-block-added-line)::before {
   content: "+";
   position: absolute;
   left: 16px;
@@ -46,20 +39,27 @@ the background in custom CSS file due bug https://github.com/facebook/docusaurus
   color: #a0aec0;;
 }
 
-
+:global(.theme-code-block-highlighted-line) {
+  background-color: var(--docusaurus-highlighted-code-line-bg);
+  display: block;
+  position: relative;
+}
 
 .codeLine {
   display: table-row;
   counter-increment: line-count;
 }
 
+.noLineNumbers {
+  padding-left: var(--ifm-pre-padding);
+}
+
 .codeLineNumber {
   display: table-cell;
   text-align: right;
   width: min-content;
   left: 0;
   padding: 0 var(--ifm-pre-padding);
-  background: var(--ifm-pre-background);
   overflow-wrap: normal;
 }
 
diff --git a/src/theme/TabItem/index.tsx b/src/theme/TabItem/index.tsx
index f884fa781e..368ecace2f 100644
--- a/src/theme/TabItem/index.tsx
+++ b/src/theme/TabItem/index.tsx
@@ -5,7 +5,7 @@ export default function TabItem({children, hidden, className, code = true, table
   return (
     <div
       role="tabpanel"
-      className={clsx(styles.tabItem, className)}
+      className={clsx(styles.tabItem, className, code && 'code-children')}
       {...{hidden}}>
       <div className={
         clsx(code ? styles.codeChildren : styles.children, table && styles.tableChildren)