update with feedback

Author: mhartington

content/200-orm/500-reference/325-prisma-config-reference.mdx

@@ -353,7 +353,7 @@ Configure the schema engine your project should use.
 
 ```ts
 import path from "node:path";
-import { defineConfig, env } from "@prisma/config";
+import { defineConfig, env } from "prisma/config";
 export default defineConfig({
   engine: "classic",
   datasource: {
@@ -368,7 +368,7 @@ provide the adapter you wish to use
 
 ```ts
 import path from "node:path";
-import { defineConfig, env } from "@prisma/config";
+import { defineConfig, env } from "prisma/config";
 import { PrismaD1 } from "@prisma/adapter-d1";
 export default defineConfig({
   experimental: {
@@ -429,7 +429,7 @@ provide a type-safe way of accessing that variable:
 
 ```tsx
 import path from "node:path";
-import { defineConfig, env } from "@prisma/config";
+import { defineConfig, env } from "prisma/config";
 
 type Env = {
   DATABASE_URL: string
@@ -455,7 +455,7 @@ npm install dotenv
 
 ```ts
 import "dotenv/config";
-import { defineConfig, env } from "@prisma/config";
+import { defineConfig, env } from "prisma/config";
 
 type Env = {
   DATABASE_URL: string
@@ -569,7 +569,7 @@ If Prisma is installed globally (`npm i -g prisma`), it may not find your `prism
 To avoid issues:
 
 - Prefer local Prisma installations in your project.
-- Or use `@prisma/config` locally and pass `--config` to point to your config file.
+- Or use `prisma/config` locally and pass `--config` to point to your config file.
 
 ### Monorepos