From 0eac19573a54be2c59bc17d593ce474a7752a045 Mon Sep 17 00:00:00 2001
From: Ankur Datta <64993082+ankur-arch@users.noreply.github.com>
Date: Tue, 10 Sep 2024 16:15:54 +0200
Subject: [PATCH] fix: clear token from limitations page

---
 content/700-optimize/700-known-limitations.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/700-optimize/700-known-limitations.mdx b/content/700-optimize/700-known-limitations.mdx
index e2d4a25363..100e91d006 100644
--- a/content/700-optimize/700-known-limitations.mdx
+++ b/content/700-optimize/700-known-limitations.mdx
@@ -34,7 +34,7 @@ When using the [Optimize client extension](https://www.npmjs.com/package/@prisma
 const prisma = new PrismaClient()
   .$extends(
     withOptimize({
-      token: process.env.OPTIMIZE_API_KEY,
+      apiKey: process.env.OPTIMIZE_API_KEY,
     }),
   )
   .$extends(withAccelerate());
@@ -50,4 +50,4 @@ Raw queries are visible in MongoDB, though the parameters passed to them are not
 
 ## Driver adapter compatibility
 
-Prisma Optimize is not yet compatible with [driver adapters](/orm/overview/databases/database-drivers#driver-adapters). However, as a workaround, you can run your queries locally using the regular Prisma Client along with Prisma Optimize to inspect and improve query performance.
\ No newline at end of file
+Prisma Optimize is not yet compatible with [driver adapters](/orm/overview/databases/database-drivers#driver-adapters). However, as a workaround, you can run your queries locally using the regular Prisma Client along with Prisma Optimize to inspect and improve query performance.