docs: fix spellcheck failures from the MongoDB migration guide (#8112)

* docs: fix spellcheck failures from the MongoDB migration guide

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 <noreply@anthropic.com>

* docs: tell readers to align dbName with the v6 database

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Author: ankur-arch

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
@@ -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

apps/docs/cspell.json

@@ -70,6 +70,7 @@
     "Ctype",
     "cursorrules",
     "cursorstream",
+    "cutover",
     "datadog",
     "datamodel",
     "DATAPROXY",