From e6a0187d948f77b274867bb33aeb0306d627c5b8 Mon Sep 17 00:00:00 2001 From: Ankur Datta <64993082+ankur-arch@users.noreply.github.com> Date: Tue, 28 Jul 2026 14:55:54 +0200 Subject: [PATCH 1/2] docs: fix spellcheck failures from the MongoDB migration guide MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add cutover to the cspell project dictionary and switch façade to facade in the guide. Follow-up to #8111, which landed with these two words failing the Spellcheck workflow on main. Co-Authored-By: Claude Fable 5 --- .../content/docs/guides/next/upgrade-prisma-orm/mongodb.mdx | 2 +- apps/docs/cspell.json | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/apps/docs/content/docs/guides/next/upgrade-prisma-orm/mongodb.mdx b/apps/docs/content/docs/guides/next/upgrade-prisma-orm/mongodb.mdx index 0565e641cf..5146c1e84c 100644 --- a/apps/docs/content/docs/guides/next/upgrade-prisma-orm/mongodb.mdx +++ b/apps/docs/content/docs/guides/next/upgrade-prisma-orm/mongodb.mdx @@ -42,7 +42,7 @@ Scaffold the project: npx prisma-next init --yes --target mongodb --authoring psl ``` -`init` writes a `prisma-next.config.ts` at the repo root. MongoDB is selected by importing the `@prisma-next/mongo` façade, not by a `provider` string in the schema. Point the connection at the **same database** your v6 app uses. +`init` writes a `prisma-next.config.ts` at the repo root. MongoDB is selected by importing the `@prisma-next/mongo` facade, not by a `provider` string in the schema. Point the connection at the **same database** your v6 app uses. ```typescript tab="After" // prisma-next.config.ts diff --git a/apps/docs/cspell.json b/apps/docs/cspell.json index 7a0c5afc51..d091b7c424 100644 --- a/apps/docs/cspell.json +++ b/apps/docs/cspell.json @@ -70,6 +70,7 @@ "Ctype", "cursorrules", "cursorstream", + "cutover", "datadog", "datamodel", "DATAPROXY", From fc54d3e1a3bb324d564b05692d746307f2c76a56 Mon Sep 17 00:00:00 2001 From: Ankur Datta <64993082+ankur-arch@users.noreply.github.com> Date: Tue, 28 Jul 2026 15:10:09 +0200 Subject: [PATCH 2/2] docs: tell readers to align dbName with the v6 database Co-Authored-By: Claude Fable 5 --- .../content/docs/guides/next/upgrade-prisma-orm/mongodb.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/content/docs/guides/next/upgrade-prisma-orm/mongodb.mdx b/apps/docs/content/docs/guides/next/upgrade-prisma-orm/mongodb.mdx index 5146c1e84c..069b9d834a 100644 --- a/apps/docs/content/docs/guides/next/upgrade-prisma-orm/mongodb.mdx +++ b/apps/docs/content/docs/guides/next/upgrade-prisma-orm/mongodb.mdx @@ -73,7 +73,7 @@ Run `npx prisma-next contract emit` to generate `contract.json` from your `.pris ### Import the client -The way to instantiate the Prisma client now is from the emitted contract: +The way to instantiate the Prisma client now is from the emitted contract. Replace `my-app-db` with the database name your v6 connection string uses; if the connection URL already carries the database name in its path, omit `dbName` and the client reads it from the URL: ```typescript tab="After" // src/prisma/db.ts