correct links

Author: jharrell

content/200-orm/200-prisma-client/100-queries/100-query-optimization-performance.mdx

@@ -93,7 +93,7 @@ async function getUsers() {
 }
 ```
 
-For serverless development environments with frameworks that use HMR (Hot Module Replacement), ensure you properly handle a [single instance of Prisma in development](/orm/more/help-and-troubleshooting/help-articles/nextjs-prisma-client-dev-practices).
+For serverless development environments with frameworks that use HMR (Hot Module Replacement), ensure you properly handle a [single instance of Prisma in development](/orm/more/help-and-troubleshooting/nextjs-help#best-practices-for-using-prisma-client-in-development).
 
 ## Solving the n+1 problem
 

content/200-orm/200-prisma-client/500-deployment/400-module-bundlers.mdx

@@ -15,5 +15,5 @@ To do so, you can use plugins that let you copy over static assets:
 | Bundler                                                                                                           | Plugin                                                                                                         |
 | :---------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------- |
 | Webpack                                                                                                           | [`copy-webpack-plugin`](https://github.com/webpack-contrib/copy-webpack-plugin#copy-webpack-plugin)            |
-| Webpack (with [Next.js monorepo](/orm/more/help-and-troubleshooting/help-articles/nextjs-prisma-client-monorepo)) | [`nextjs-monorepo-workaround-plugin`](https://www.npmjs.com/package/@prisma/nextjs-monorepo-workaround-plugin) |
+| Webpack (with [Next.js monorepo](/orm/more/help-and-troubleshooting/nextjs-help#setting-up-prisma-orm-in-a-monorepo)) | [`nextjs-monorepo-workaround-plugin`](https://www.npmjs.com/package/@prisma/nextjs-monorepo-workaround-plugin) |
 | Parcel                                                                                                            | [`parcel-plugin-static-files-copy`](https://github.com/elwin013/parcel-plugin-static-files-copy#readme)        |

content/200-orm/300-prisma-migrate/200-understanding-prisma-migrate/600-legacy-migrate.mdx

@@ -197,7 +197,7 @@ The following table shows which SQL operations are currently supported by legacy
 | Create indexes                    | `CREATE INDEX`                  |                                          ✔️                                           |
 | Cascading deletes                 | `ON DELETE`                     |                  No (workaround: manually add in SQL and introspect)                  |
 | Cascading updates                 | `ON UPDATE`                     |                                          No                                           |
-| Data validation                   | `CHECK`                         | No ([workaround](/orm/more/help-and-troubleshooting/help-articles/check-constraints)) |
+| Data validation                   | `CHECK`                         | No ([workaround](/orm/more/help-and-troubleshooting/check-constraints)) |
 
 Note that this table assumes that the operation is also supported by the underlying database. For example, `ENUM` is not supported in SQLite. This means that you also can't use `enum` when using legacy Prisma Migrate.
 

content/200-orm/500-reference/050-prisma-client-reference.mdx

@@ -3502,7 +3502,7 @@ const result = await prisma.user.update({
 <Admonition type="info">
 
 - From version 4.3.0, you can also use these operators to compare _fields_ in the same model [with the `<model>.fields` property](#compare-columns-in-the-same-table).
-- In versions before 4.3.0, you can compare fields in the same model [with raw queries](/orm/more/help-and-troubleshooting/help-articles/comparing-columns-through-raw-queries).
+- In versions before 4.3.0, you can compare fields in the same model [with raw queries](/orm/more/help-and-troubleshooting/comparing-columns-through-raw-queries).
 
 </Admonition>
 
@@ -5525,7 +5525,7 @@ This feature was moved to general availability in version 5.0.0 and was availabl
 
 <Admonition type="info">
 
-In the following situations, you must [use raw queries to compare columns in the same table](/orm/more/help-and-troubleshooting/help-articles/comparing-columns-through-raw-queries):
+In the following situations, you must [use raw queries to compare columns in the same table](/orm/more/help-and-troubleshooting/comparing-columns-through-raw-queries):
 
 - If you use a version earlier than 4.3.0
 - If you want to use a unique filter, such as [`findUnique`](#findunique) or [`findUniqueOrThrow`](#finduniqueorthrow)

content/200-orm/800-more/600-help-and-troubleshooting/400-nextjs-help.mdx

@@ -1,6 +1,7 @@
 ---
-title: "Comprehensive Guide to Using Prisma with Next.js"
-description: "Learn best practices, monorepo strategies, and dynamic usage techniques for Prisma in Next.js applications."
+title: "Comprehensive Guide to Using Prisma ORM with Next.js"
+sidebar_label: "Using Prisma ORM with Next.js"
+description: "Learn best practices, monorepo strategies, and dynamic usage techniques for Prisma ORM in Next.js applications."
 tags:
   - Prisma
   - Next.js
@@ -10,7 +11,7 @@ tags:
   - Best Practices
 ---
 
-Prisma and Next.js form a powerful combination for building modern, server-side rendered, and API-driven web applications. This guide consolidates various tips and strategies to help you maximize their potential. Whether you’re looking for best practices, monorepo setup guidance, or strategies for dynamic usage, we’ve got you covered.
+Prisma ORM and Next.js form a powerful combination for building modern, server-side rendered, and API-driven web applications. This guide consolidates various tips and strategies to help you maximize their potential. Whether you’re looking for best practices, monorepo setup guidance, or strategies for dynamic usage, we’ve got you covered.
 
 ---
 
@@ -44,21 +45,21 @@ Using this approach ensures that only one instance of Prisma Client exists, even
 
 ---
 
-## Setting Up Prisma in a Monorepo
+## Setting Up Prisma ORM in a Monorepo
 
-### Challenges of Using Prisma in Monorepos
+### Challenges of Using Prisma ORM in Monorepos
 
-Monorepos allow multiple projects to share code and dependencies, making them a popular choice for modern development. However, using Prisma in a monorepo can present challenges related to dependency resolution and schema management.
+Monorepos allow multiple projects to share code and dependencies, making them a popular choice for modern development. However, using Prisma ORM in a monorepo can present challenges related to dependency resolution and schema management.
 
 #### Key Issues
 
-1. **Dependency Resolution**: Multiple packages in a monorepo might lead to conflicts if they use different Prisma versions.
-2. **Schema Centralization**: Managing a single Prisma schema across multiple projects can be complex.
+1. **Dependency Resolution**: Multiple packages in a monorepo might lead to conflicts if they use different version of Prisma ORM.
+2. **Schema Centralization**: Managing a single Prisma Schema across multiple projects can be complex.
 
 #### Best Practices for Monorepo Integration
 
 - **Centralize the Prisma Schema**: Place the `schema.prisma` file in a shared package, such as `@myorg/db`, to ensure consistency.
-- **Install Dependencies in the Root**: Avoid version conflicts by installing Prisma dependencies at the root of the monorepo.
+- **Install Dependencies in the Root**: Avoid version conflicts by installing Prisma ORM as a dependency at the root of the monorepo.
 - **Use NPM Scripts for Generation**:
 
 ```json
@@ -69,15 +70,15 @@ Monorepos allow multiple projects to share code and dependencies, making them a
 }
 ```
 
-This approach keeps your Prisma schema and generated client in sync across all projects in the monorepo.
+This approach keeps your Prisma Schema and generated client in sync across all projects in the monorepo.
 
 ---
 
 ## Dynamic Usage of Prisma Client in Next.js
 
 ### Handling Dynamic Scenarios
 
-Dynamic use cases, such as working with tenant-specific databases, require additional consideration when using Prisma with Next.js.
+Dynamic use cases, such as working with tenant-specific databases, require additional consideration when using Prisma ORM with Next.js.
 
 #### Problem
 

content/200-orm/800-more/600-help-and-troubleshooting/900-prisma-nuxt-module.mdx

@@ -34,7 +34,7 @@ This module provides several features to streamline the setup and usage of Prism
     <br />
     :::warning
 
-    If you're using `pnpm`, make sure to hoist Prisma dependencies. Follow the steps [here](/orm/more/help-and-troubleshooting/help-articles/prisma-nuxt-module#prisma-studio-not-opening-with-pnpm) for detailed instructions.
+    If you're using `pnpm`, make sure to hoist Prisma dependencies. Follow the [Prisma studio steps](#prisma-studio-not-opening-with-pnpm) for detailed instructions.
 
     :::