docs(): update based on feedback

Author: mhartington

content/250-postgres/350-integrations/100-netlify.mdx

@@ -51,6 +51,7 @@ Ensure that the data source in your `prisma.config.ts` file is configured to use
 
 ```typescript 
 // prisma.config.ts
+import 'dotenv/config';
 import { defineConfig, env } from '@prisma/config';
 export default defineConfig({
   datasource: {
@@ -70,13 +71,12 @@ To ensure the generated Prisma Client library is available on your deployed Netl
   "scripts": {
     // ...
     // add-next-line
-    "postinstall": "prisma generate --no-engine"
+    "postinstall": "prisma generate"
   }
   //
 }
 ```
 
-The `--no-engine` flag ensures that the query engine binary is kept out of the generated Prisma Client library. It's not needed when using Prisma Postgres.
 
 ## Example: Deploy a Next.js template with Prisma Postgres
 
@@ -162,7 +162,7 @@ Open the `app/page.jsx` file and replace the entire contents with this code:
 
 ```js file=app/page.jsx
 import 'dotenv/config';
-import { PrismaClient } from '../generated/prisma/client.js';
+import { PrismaClient } from '../path/to/generated/prisma/client';
 import {PrismaPg} from '@prisma/adapter-pg'
 
 const databaseUrl = process.env.DATABASE_URL;
@@ -218,7 +218,7 @@ As mentioned [above](#generate-prisma-client-in-a-postinstall-script-in-packagej
         "start": "next start",
         "lint": "next lint",
         // add-next-line
-        "postinstall": "prisma generate --no-engine"
+        "postinstall": "prisma generate"
     },
     "dependencies": {
         "@netlify/blobs": "^8.1.0",

content/250-postgres/350-integrations/200-vercel.mdx

@@ -69,6 +69,7 @@ npx prisma studio
 Ensure that the data source in your `prisma.config.ts` file is configured to use the `DATABASE_URL` environment variable:
 
 ```ts 
+import 'dotenv/config';
 import { defineConfig, env } from '@prisma/config';
 export default defineConfig({
   datasource: {
@@ -88,10 +89,8 @@ To ensure the generated Prisma Client library is available on your deployed Verc
   "scripts": {
     // ...
     // add-next-line
-    "postinstall": "prisma generate --no-engine"
+    "postinstall": "prisma generate"
   }
   //
 }
 ```
-
-The `--no-engine` flag ensures that the query engine binary is kept out of the generated Prisma Client library. It's not needed when using Prisma Postgres.

content/250-postgres/400-query-optimization/100-setup.mdx

@@ -52,7 +52,7 @@ OPTIMIZE_API_KEY="YOUR_OPTIMIZE_API_KEY"
 Extend your existing Prisma Client instance with the Optimize extension:
 
 ```ts
-import { PrismaClient } from '../generated/prisma/client.js';
+import { PrismaClient } from '../path/to/generated/prisma/client';
 import { withOptimize } from "@prisma/extension-optimize";
 
 const prisma = new PrismaClient().$extends(