Update upgrading-from-prisma-1.md

prisma · Oct 21, 2019 · 6deeb91 · 6deeb91
1 parent 8dcc69a
commit 6deeb91
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/upgrading-from-prisma-1.md b/docs/upgrading-from-prisma-1.md
@@ -96,7 +96,7 @@ model Post {
 }
 ```
 
-**Note**: The `@unique` attributes on the `id` fields are [redundant](https://github.com/prisma/prisma2/issues/786) as uniqueness is already implied by the `@id` attribute. It also contains another bug where it [doesn't convert `@default` attributes](https://github.com/prisma/prisma2/issues/790), so you need to manually add the `@default(true)` to the `published` field in the Prisma schema.
+> **Note**: The `@unique` attributes on the `id` fields are [redundant](https://github.com/prisma/prisma2/issues/786) as uniqueness is already implied by the `@id` attribute. It also contains another bug where it [doesn't convert `@default` attributes](https://github.com/prisma/prisma2/issues/790), so you need to manually add the `@default(true)` to the `published` field in the Prisma schema.
 
 ### 2.2. Add the datasource
 
@@ -176,7 +176,7 @@ generate:
 
 With the Prisma Framework, this information is now also contained inside the Prisma schema via a `generator` block. Add it to your your Prisma schema like so:
 
-```prisma
+```diff
 datasource postgresql {
   provider = "postgresql"
   url =      "postgresql://janedoe:janedoe@localhost:5432/mydb?schema=public"
@@ -428,4 +428,4 @@ Going forward, you won't perform schema migrations using the `prisma deploy` com
 
 ## Summary
 
-In this upgrade guide, you learned how to upgrade an ExpressJS-based REST API from Prisma 1 to the Prisma Framework that uses Photon.js and Lift. In the future, we'll cover more fine-grained upgrade scenarios, based on more complicated database schemas as well as for projects that are using GraphQL Nexus and `nexus-prisma`.
+In this upgrade guide, you learned how to upgrade an ExpressJS-based REST API from Prisma 1 to the Prisma Framework that uses Photon.js and Lift. In the future, we'll cover more fine-grained upgrade scenarios, based on more complicated database schemas as well as for projects that are using GraphQL Nexus and `nexus-prisma`.