fix: correct casing of PrismaBetterSqlite3

[bhbs]

SQLite3 must be Sqlite3

https://github.com/prisma/prisma/blob/177882704271b747b3618b0cf6790e46f2432b7a/packages/adapter-better-sqlite3/src/index.ts#L1

Summary by CodeRabbit

• Documentation
  • Updated guidance in the Getting Started and Upgrade guides to reflect the renamed SQLite adapter export and its usage, ensuring examples and instructions match the current package API.
  • Clarified upgrade notes so users following migration steps will see the updated adapter naming in documentation and sample code.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This pull request corrects the class name casing of the Prisma SQLite adapter from PrismaBetterSQLite3 to PrismaBetterSqlite3 in two documentation files, updating import statements and constructor instantiations; no logic or control-flow changes introduced.

Changes

Cohort / File(s)	Change Summary
Prisma SQLite adapter class name correction content/100-getting-started/_components/_create-prisma-client.mdx, content/200-orm/800-more/300-upgrade-guides/200-upgrading-to-prisma-7.mdx	Renamed adapter export and usage from PrismaBetterSQLite3 to PrismaBetterSqlite3 in imports and new constructor invocations within SQLite code blocks.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Changes are simple, consistent text edits in documentation; no runtime logic to validate.

Possibly related PRs

• docs(): add v7 migration guide #7249 — Same adapter export rename (PrismaBetterSQLite3 → PrismaBetterSqlite3) applied in related upgrade-guide documentation.

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: correcting the casing of PrismaBetterSqlite3 across documentation files, which is exactly what the changeset implements.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 18f2b87 and f8ab7bb.

📒 Files selected for processing (1)

• content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/400-upgrading-to-prisma-7.mdx (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".

📚 Learning: 2025-10-09T21:32:50.340Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7167
File: content/900-ai/prompts/astro.mdx:84-84
Timestamp: 2025-10-09T21:32:50.340Z
Learning: The `npx prisma init` command supports the following flags: `--db` (shorthand for `--datasource-provider prisma+postgres`), `--output` (specifies output location for generated client), `--generator-provider` (defines the generator provider), `--datasource-provider`, `--url`, `--preview-feature`, and `--with-model`. These are documented valid CLI options for Prisma init command.

Applied to files:

• content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/400-upgrading-to-prisma-7.mdx

🔇 Additional comments (1)

content/200-orm/800-more/300-upgrade-guides/200-upgrading-versions/400-upgrading-to-prisma-7.mdx (1)

177-188: Casing correction aligns with official Prisma naming convention.

The changes correctly update the SQLite adapter class name from PrismaBetterSQLite3 to PrismaBetterSqlite3 in both the import statement (line 181) and constructor instantiation (line 183). This aligns with the official naming convention from the Prisma repository.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}