Broken link fix

content/02-understand-prisma/02-features.mdx

@@ -88,7 +88,7 @@ Lock option (MySQL):
 | Authorization and user management | Yes        | Yes   | No     | Not yet                                          | Not yet                            | Not yet         |
 | JSON support                      | Yes        | No    | No     | Not yet                                          | Not yet                            | Not yet         |
 | Fuzzy/Phrase Full Text Search     | Yes        | Yes   | No     | Not yet                                          | Not yet                            | Not yet         |
-| Table inheritance | Yes | No | No | Not yet | Not yet | Yes |
+| Table inheritance                 | Yes        | No    | No     | Not yet                                          | Not yet                            | Yes             |
 
 ## Functions
 

content/03-reference/01-tools-and-interfaces/01-prisma-schema/04-data-model.mdx

@@ -1,7 +1,7 @@
 ---
-title: "Data model"
-metaTitle: ""
-metaDescription: ""
+title: 'Data model'
+metaTitle: ''
+metaDescription: ''
 ---
 
 ## Overview
@@ -334,7 +334,7 @@ Note that in the above case, you _must_ provide your own ID values when creating
 const newUser = await prisma.user.create({
   data: {
     id: 1,
-    name: "Alice",
+    name: 'Alice',
   },
 });
 ```
@@ -397,11 +397,11 @@ Note that in this case you can only create new `Post` records by using Prisma Cl
 ```ts
 const post = await prisma.post.create({
   data: {
-    title: "Hello World",
+    title: 'Hello World',
     author: {
       create: {
-        name: "Alice",
-        email: "alice@prisma.io",
+        name: 'Alice',
+        email: 'alice@prisma.io',
       },
     },
   },
@@ -413,10 +413,10 @@ Or when a `User` record with `bob@prisma.io` as its `email` already exists, you
 ```ts
 const post = await prisma.post.create({
   data: {
-    title: "Hello World",
+    title: 'Hello World',
     author: {
       connect: {
-        email: "bob@prisma.io",
+        email: 'bob@prisma.io',
       },
     },
   },
@@ -476,8 +476,8 @@ When creating new `User` records, you now must provide a unique combination of v
 ```ts
 const user = await prisma.user.create({
   data: {
-    firstName: "Alice",
-    lastName: "Smith",
+    firstName: 'Alice',
+    lastName: 'Smith',
   },
 });
 ```
@@ -500,8 +500,8 @@ When creating new `User` records, you now must provide a unique combination of v
 ```ts
 const user = await prisma.user.create({
   data: {
-    firstName: "Alice",
-    lastName: "Smith",
+    firstName: 'Alice',
+    lastName: 'Smith',
     isAdmin: true,
   },
 });
@@ -531,10 +531,10 @@ When creating new `Post` records, you now must provide a unique combination of v
 ```ts
 const post = await prisma.post.create({
   data: {
-    title: "Hello World",
+    title: 'Hello World',
     author: {
       connect: {
-        email: "alice@prisma.io",
+        email: 'alice@prisma.io',
       },
     },
   },

content/03-reference/01-tools-and-interfaces/01-prisma-schema/06-relations.mdx

@@ -205,14 +205,10 @@ Virtual relation fields are also present in the generated [Prisma Client API]()
 
 ```js
 // Traverse relation from `Post` to `User` via fluent API
-const user = await prisma.post
-  .findOne({ where: { id: 1 } })
-  .author()
+const user = await prisma.post.findOne({ where: { id: 1 } }).author();
 
 // Traverse relation from `User` to `Post` via fluent API
-const user = await prisma.user
-  .findOne({ where: { id: 1 } })
-  .posts()
+const user = await prisma.user.findOne({ where: { id: 1 } }).posts();
 ```
 
 ## The @relation attribute
@@ -436,12 +432,12 @@ To summarize, these are the rules for determining which side of a 1-1-relation h
 
 Here's the summary in the form of a table assuming the two relation fields of the models from before `Profile.user` and `User.profile`:
 
-| `Prrofile.user` | `User.profile` | Foreign key on                                               | `@relation` attribute                             |
-| :------------------------ | :------------------------ | ------------------------------------------------------------ | ------------------------------------------------- |
-| Required                  | Optional                  | `Profile` (because the relation field on `User` is virtual) | Can't be used to determine the foreign key        |
-| Optional                  | Required                  | `User` (because the relation field on `Profile` is virtual) | Can't be used to determine the foreign key        |
-| Optional                  | Optional                  | `Profile` (because it's first in the alphabet)                | Can be used to manually determine the foreign key |
-| Required                  | Required                  | `Profile` (because it's first in the alphabet)                | Can be used to manually determine the foreign key |
+| `Prrofile.user` | `User.profile` | Foreign key on                                              | `@relation` attribute                             |
+| :-------------- | :------------- | ----------------------------------------------------------- | ------------------------------------------------- |
+| Required        | Optional       | `Profile` (because the relation field on `User` is virtual) | Can't be used to determine the foreign key        |
+| Optional        | Required       | `User` (because the relation field on `Profile` is virtual) | Can't be used to determine the foreign key        |
+| Optional        | Optional       | `Profile` (because it's first in the alphabet)              | Can be used to manually determine the foreign key |
+| Required        | Required       | `Profile` (because it's first in the alphabet)              | Can be used to manually determine the foreign key |
 
 ## One-to-many
 
@@ -628,7 +624,7 @@ If you're not using Prisma Migrate but obtain your data model from [introspectio
 The name of the relation table must be prefixed with an underscore:
 
 - **Valid**: `_CategoryToPost`, `_MyRelation`
-- **Invalid**: ``CategoryToPost`, `MyRelation`
+- **Invalid**: ``CategoryToPost`,`MyRelation`
 
 #### Columns
 
@@ -716,7 +712,7 @@ model User {
   id       Int      @id @default(autoincrement())
   name     String?
   husband  User?    @relation("MarriagePartners")
-  wife     User     @relation("MarriagePartners", references: [id]) 
+  wife     User     @relation("MarriagePartners", references: [id])
 }
 ```
 
@@ -731,7 +727,7 @@ model User {
   id       Int      @id @default(autoincrement())
   name     String?
   teacher  User?    @relation("TeacherStudents")
-  students User[]   @relation("TeacherStudents") 
+  students User[]   @relation("TeacherStudents")
 }
 ```
 
@@ -771,7 +767,7 @@ model User {
   husband     User?    @relation("MarriagePartners")
   wife        User     @relation("MarriagePartners")
   teacher     User?    @relation("TeacherStudents")
-  students    User[]   @relation("TeacherStudents") 
+  students    User[]   @relation("TeacherStudents")
   followedBy  User[]   @relation("UserFollows")
   following   User[]   @relation("UserFollows")
 }
@@ -820,4 +816,4 @@ model Post {
   author   User    @relation("WrittenPosts")
   pinnedBy User?   @relation("PinnedPost")
 }
-```
+```

content/03-reference/01-tools-and-interfaces/01-prisma-schema/index.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Prisma schema"
-metaTitle: ""
-metaDescription: ""
+title: 'Prisma schema'
+metaTitle: ''
+metaDescription: ''
 ---

content/03-reference/01-tools-and-interfaces/02-prisma-client/03-crud.mdx

@@ -1,7 +1,7 @@
 ---
-title: "CRUD"
-metaTitle: ""
-metaDescription: ""
+title: 'CRUD'
+metaTitle: ''
+metaDescription: ''
 ---
 
 ## Overview
@@ -54,7 +54,7 @@ enum Role {
 CRUD queries are exposed by the _model properties_ on your `PrismaClient` instance. Taking the `User` and `Post` models from above as examples, you'd invoke the CRUD queries via the `prisma.user` and `prisma.post` model properties, e.g.:
 
 ```ts
-await prisma.user.create({ data: { name: "Alice" } });
+await prisma.user.create({ data: { name: 'Alice' } });
 // or
 await prisma.post.findMany();
 ```
@@ -161,7 +161,7 @@ const result = await prisma.user.findOne({
 ```ts
 const result = await prisma.user.findOne({
   where: {
-    email: "alice@prisma.io",
+    email: 'alice@prisma.io',
   },
 });
 ```
@@ -185,8 +185,8 @@ model User {
 const result = await prisma.user.findOne({
   where: {
     firstName_lastName: {
-      firstName: "Alice",
-      lastName: "Smith",
+      firstName: 'Alice',
+      lastName: 'Smith',
     },
   },
 });
@@ -251,8 +251,8 @@ export type UserOrderByInput = {
 };
 
 export declare const OrderByArg: {
-  asc: "asc";
-  desc: "desc";
+  asc: 'asc';
+  desc: 'desc';
 };
 ```
 
@@ -295,7 +295,7 @@ export type User = {
 
 ```ts
 const user = await prisma.user.findMany({
-  where: { name: "Alice" },
+  where: { name: 'Alice' },
 });
 ```
 
@@ -381,7 +381,7 @@ export type User = {
 
 ```ts
 const user = await prisma.user.create({
-  data: { email: "alice@prisma.io" },
+  data: { email: 'alice@prisma.io' },
 });
 ```
 
@@ -474,7 +474,7 @@ export type User = {
 ```ts
 const user = await prisma.user.update({
   where: { id: 1 },
-  data: { email: "alice@prisma.io" },
+  data: { email: 'alice@prisma.io' },
 });
 ```
 
@@ -536,8 +536,8 @@ export type User = {
 ```ts
 const user = await prisma.user.upsert({
   where: { id: 1 },
-  update: { email: "alice@prisma.io" },
-  create: { email: "alice@prisma.io" },
+  update: { email: 'alice@prisma.io' },
+  create: { email: 'alice@prisma.io' },
 });
 ```
 
@@ -706,8 +706,8 @@ The value of `count` is an integer and represents the number of records that hav
 
 ```ts
 const updatedUserCount = await prisma.user.updateMany({
-  where: { name: "Alice" },
-  data: { name: "ALICE" },
+  where: { name: 'Alice' },
+  data: { name: 'ALICE' },
 });
 ```
 
@@ -759,7 +759,7 @@ The value of `count` is an integer and represents the number of records that hav
 
 ```ts
 const deletedUserCount = await prisma.user.deleteMany({
-  where: { name: "Alice" },
+  where: { name: 'Alice' },
 });
 ```