docs: fix broken MongoDB data modeling link

Arthur Gamby · Arthur Gamby · commit bab988a45864 · 2025-12-04T10:56:05.000+01:00
diff --git a/content/200-orm/050-overview/100-introduction/300-data-modeling.mdx b/content/200-orm/050-overview/100-introduction/300-data-modeling.mdx
@@ -74,7 +74,7 @@ In MongoDB databases, models are represented by _collections_ and contain _docum
 }
 ```
 
-Prisma Client currently expects a consistent model and [normalized model design](https://www.mongodb.com/docs/manual/data-modeling/concepts/embedding-vs-references/#references). This means that:
+Prisma Client currently expects a consistent model and [normalized model design](https://www.mongodb.com/docs/manual/data-modeling/best-practices/#std-label-data-modeling-best-practices). This means that:
 
 - If a model or field is not present in the Prisma schema, it is ignored
 - If a field is mandatory but not present in the MongoDB dataset, you will get an error

Original file line number	Diff line number	Diff line change
`@@ -74,7 +74,7 @@ In MongoDB databases, models are represented by _collections_ and contain _docum`
`74`	`74`	`}`
`75`	`75`	```
`76`	`76`
`77`		`-Prisma Client currently expects a consistent model and [normalized model design](https://www.mongodb.com/docs/manual/data-modeling/concepts/embedding-vs-references/#references). This means that:`
	`77`	`+Prisma Client currently expects a consistent model and [normalized model design](https://www.mongodb.com/docs/manual/data-modeling/best-practices/#std-label-data-modeling-best-practices). This means that:`
`78`	`78`
`79`	`79`	`- If a model or field is not present in the Prisma schema, it is ignored`
`80`	`80`	`- If a field is mandatory but not present in the MongoDB dataset, you will get an error`