docs(orm-overview): explain acronyms for general readers

[Hephaest]

Hi team,

I reviewed the ORM Overview section and noticed two acronyms that lack explanations. These acronyms may be familiar to those who have worked with databases, but they are not widely known (e.g., a frontend developer like me).

That's why I raised this pull request. Let me know your thoughts :)

Summary by CodeRabbit

• Documentation
  • Expanded GraphQL SDL terminology with complete "Schema Definition Language" definition
  • Clarified POJO term with explicit "Plain Old JavaScript Object" definition in data modeling section

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

[coderabbitai]

Walkthrough

Two documentation files received minor clarification updates. In 250-should-you-use-prisma.mdx, GraphQL SDL references now include their full form "Schema Definition Language" in link text. In 300-data-modeling.mdx, the POJO acronym is expanded inline with its definition "Plain Old JavaScript Object." Both changes improve terminology clarity in technical content.

Changes

Cohort / File(s)	Change Summary
Documentation clarity improvements content/200-orm/050-overview/100-introduction/250-should-you-use-prisma.mdx, content/200-orm/050-overview/100-introduction/300-data-modeling.mdx	Expanded technical terminology explanations: "GraphQL SDL" → "GraphQL SDL (Schema Definition Language)" (2 occurrences); "POJO" → "POJO (Plain Old JavaScript Object)" for improved reader comprehension.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Rationale: These are pure documentation text expansions adding definitional clarity to acronyms—no logic, configuration, or structural changes. The modifications are isolated, repetitive in nature (simple text additions), and require only verification that the terminology additions are accurate and contextually appropriate.

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 PR title clearly and specifically describes the main change: adding explanations for acronyms (SDL, POJO) in ORM overview documentation for general readers, directly matching the changeset content.
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 432af39 and 5f9281f.

📒 Files selected for processing (2)

• content/200-orm/050-overview/100-introduction/250-should-you-use-prisma.mdx (1 hunks)
• content/200-orm/050-overview/100-introduction/300-data-modeling.mdx (1 hunks)

🧰 Additional context used

🧠 Learnings (6)

📓 Common learnings

Learnt from: carlagn
Repo: prisma/docs PR: 7183
File: content/200-orm/800-more/600-help-and-troubleshooting/050-dataguide/050-database-glossary.mdx:561-567
Timestamp: 2025-10-14T11:41:08.844Z
Learning: Ignore the file `content/200-orm/800-more/600-help-and-troubleshooting/050-dataguide/050-database-glossary.mdx` in future reviews as per user request. Issues in this file were addressed in PR #7185.

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".

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: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7301
File: content/800-guides/410-cloudflare-workers.mdx:87-107
Timestamp: 2025-11-20T21:00:02.587Z
Learning: Do not suggest changes to `prisma.config.ts` files in the prisma/docs repository, as the code examples are intentional for documentation purposes.

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.

📚 Learning: 2025-10-08T16:23:00.388Z

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".

Applied to files:

• content/200-orm/050-overview/100-introduction/250-should-you-use-prisma.mdx

📚 Learning: 2025-11-20T21:00:02.587Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7301
File: content/800-guides/410-cloudflare-workers.mdx:87-107
Timestamp: 2025-11-20T21:00:02.587Z
Learning: Do not suggest changes to `prisma.config.ts` files in the prisma/docs repository, as the code examples are intentional for documentation purposes.

Applied to files:

• content/200-orm/050-overview/100-introduction/250-should-you-use-prisma.mdx

📚 Learning: 2025-10-08T16:23:00.388Z

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: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.

Applied to files:

• content/200-orm/050-overview/100-introduction/250-should-you-use-prisma.mdx

📚 Learning: 2025-10-08T16:22:57.129Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.

Applied to files:

• content/200-orm/050-overview/100-introduction/250-should-you-use-prisma.mdx

📚 Learning: 2025-08-11T09:40:55.237Z

Learnt from: ankur-arch
Repo: prisma/docs PR: 7066
File: content/200-orm/200-prisma-client/700-debugging-and-troubleshooting/245-troubleshooting-binary-size-issues.mdx:8-22
Timestamp: 2025-08-11T09:40:55.237Z
Learning: When the queryCompiler preview feature is enabled in Prisma ORM (v6.7.0+), it does not require Rust engines for CLI tools like `prisma migrate` or `prisma db pull`. The previous understanding that CLI tools would still need Rust binaries even with queryCompiler enabled is incorrect.

Applied to files:

• content/200-orm/050-overview/100-introduction/250-should-you-use-prisma.mdx

🔇 Additional comments (2)

content/200-orm/050-overview/100-introduction/300-data-modeling.mdx (1)

176-176: Excellent clarity improvement for general audiences.

Expanding "POJO" to "POJO (Plain Old JavaScript Object)" is exactly right for this documentation context. Frontend developers and those new to backend concepts will immediately understand what's being described without having to search for the term. The inline expansion is concise and fits naturally in the sentence.

content/200-orm/050-overview/100-introduction/250-should-you-use-prisma.mdx (1)

94-94: Thoughtful acronym expansion for broader comprehension.

Adding "(Schema Definition Language)" after "GraphQL SDL" makes this section more accessible to readers unfamiliar with GraphQL terminology. The inline expansion is natural and unobtrusive, and the link to the Prisma blog provides deeper context for interested readers. This directly supports the PR objective of making technical content approachable for general audiences.

---

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.}