diff --git a/apps/docs/content/docs/postgres/database/connection-pooling.mdx b/apps/docs/content/docs/postgres/database/connection-pooling.mdx
index 75f06ca0bf..8dce981f79 100644
--- a/apps/docs/content/docs/postgres/database/connection-pooling.mdx
+++ b/apps/docs/content/docs/postgres/database/connection-pooling.mdx
@@ -16,14 +16,14 @@ Prisma Postgres supports connection pooling through [TCP connections](#connectio
 TCP connection pooling is currently in [Early Access](/console/more/feature-maturity#early-access).
 :::
 
-To use a pooled connection, append `&pooled=true` to your Prisma Postgres TCP connection string:
+To use a pooled connection, append `&pool=true` to your Prisma Postgres TCP connection string:
 
 ```bash
 # Direct connection (no pooling)
 DATABASE_URL="postgres://USER:PASSWORD@db.prisma.io:5432/?sslmode=require"
 
 # Pooled connection
-DATABASE_URL="postgres://USER:PASSWORD@db.prisma.io:5432/?sslmode=require&pooled=true"
+DATABASE_URL="postgres://USER:PASSWORD@db.prisma.io:5432/?sslmode=require&pool=true"
 ```
 
 You can also enable connection pooling when generating your connection string in the [Prisma Console](https://console.prisma.io) by toggling on the **pooling** option.