fix: update docs

Author: ankur-arch

content/200-orm/500-reference/200-prisma-cli-reference.mdx

@@ -879,9 +879,23 @@ Fetching latest updates for this subcommand...
 
 </CodeWithResult>
 
+**Run `prisma dev` with a specific name**
+
+```terminal
+npx prisma dev --name="mydbname"
+```
+
+This creates a named instance called `mydbname` that you can later start, stop, or manage using the instance management commands.
+
 ### `dev start`
 
-Starts existing [local Prisma Postgres](/postgres/database/local-development) instances in the background:
+Starts existing [local Prisma Postgres](/postgres/database/local-development) instances in the background. 
+
+:::note
+
+This command only works with instances that already exist.
+
+:::
 
 ```terminal
 npx prisma dev start <glob>
@@ -890,13 +904,13 @@ npx prisma dev start <glob>
 `<glob>` is a placeholder for a glob pattern to specify which local Prisma Postgres instances should be started, for example:
 
 ```terminal
-npx prisma dev start mydb # starts a DB called `mydb` in the background if it already exists
+npx prisma dev start mydb # starts a DB called `mydb` in the background (only if it already exists)
 ```
 
 To start all databases that begin with `mydb` (e.g. `mydb-dev` and `mydb-prod`), you can use a glob:
 
 ```terminal
-npx prisma dev start mydb* # starts all DBs starting with `mydb`
+npx prisma dev start mydb* # starts all existing DBs starting with `mydb`
 ```
 
 This enables background instance management outside of the VS Code extension.

content/250-postgres/300-database/550-local-development.mdx

@@ -83,10 +83,10 @@ To transition to production, you only need to update the database URL in the `.e
 You can target a specific, local Prisma Postgres instance via the `--name` (`-n`) option of the `prisma dev` command, for example:
 
 ```terminal
-npx prisma dev --name mydb1
+npx prisma dev --name="mydb1"
 ```
 
-Whenever you pass the `--name mydb1` to `prisma dev`, the command will return the same connection string pointing to a local instance called `mydb1`.
+Whenever you pass the `--name="mydb1"` to `prisma dev`, the command will return the same connection string pointing to a local instance called `mydb1`. This creates a named instance that you can later manage using the instance management commands.
 
 ## Starting existing Prisma Postgres instances in the background
 
@@ -96,16 +96,22 @@ You can start existing Prisma Postgres instances in the background using:
 npx prisma dev start <glob>
 ```
 
+:::note
+
+The `dev start` command only works with instances that already exist.
+
+:::
+
 `<glob>` is a placeholder for a glob pattern to specify which local Prisma Postgres instances should be started, for example:
 
 ```terminal
-npx prisma dev start mydb # starts a DB called `mydb` in the background
+npx prisma dev start mydb # starts a DB called `mydb` in the background (only if it already exists)
 ```
 
 To start all databases that begin with `mydb` (e.g. `mydb-dev` and `mydb-prod`), you can use a glob:
 
 ```terminal
-npx prisma dev start mydb* # starts all DBs starting with `mydb`
+npx prisma dev start mydb* # starts all existing DBs starting with `mydb`
 ```
 
 This command enables you to manage Prisma Postgres instances outside of the VS Code extension, allowing for background instance management in your development workflow.