diff --git a/content/200-orm/200-prisma-client/500-deployment/301-edge/100-overview.mdx b/content/200-orm/200-prisma-client/500-deployment/301-edge/100-overview.mdx
index 3cae0697ba..6d152f79f9 100644
--- a/content/200-orm/200-prisma-client/500-deployment/301-edge/100-overview.mdx
+++ b/content/200-orm/200-prisma-client/500-deployment/301-edge/100-overview.mdx
@@ -40,7 +40,7 @@ Here is an overview of the different database drivers and their compatibility wi
 - [`node-postgres`](https://node-postgres.com/) (`pg`) uses Cloudflare's `connect()` (TCP) to access the database. It is only compatible with Cloudflare Workers, not with Vercel Edge Functions.
 - [`@libsql/client`](https://github.com/tursodatabase/libsql-client-ts) is used to access Turso databases. It works with Cloudflare Workers and Vercel Edge Functions.
 
-> **Note**: There's [also work being done](https://github.com/sidorares/node-mysql2/pull/2289) on the `node-mysql2` driver which will enable access to traditional MySQL databases from Cloudflare Workers and Pages as well.
+There's [also work being done](https://github.com/sidorares/node-mysql2/pull/2289) on the `node-mysql2` driver which will enable access to traditional MySQL databases from Cloudflare Workers and Pages in the future as well.
 
 You can use all of these drivers with Prisma ORM using the respective [driver adapters](/orm/overview/databases/database-drivers).
 
@@ -54,3 +54,5 @@ Depending on which deployment provider and database/driver you use, there may be
   - [Vercel Postgres](/orm/prisma-client/deployment/edge/deploy-to-vercel#vercel-postgres)
   - [Neon](/orm/prisma-client/deployment/edge/deploy-to-vercel#neon)
   - [PlanetScale](/orm/prisma-client/deployment/edge/deploy-to-vercel#planetscale)
+
+If you want to deploy an app using Turso, you can follow the instructions [here](/orm/overview/databases/turso).
diff --git a/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx b/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx
index 067097e56e..92292611b3 100644
--- a/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx
+++ b/content/200-orm/200-prisma-client/500-deployment/301-edge/450-deploy-to-cloudflare.mdx
@@ -21,8 +21,6 @@ This section covers _general_ things you need to be aware of when deploying to C
 
 When deploying a Cloudflare Worker that uses Prisma ORM, you need to use an [edge-compatible driver](/orm/prisma-client/deployment/edge/overview#edge-compatibility-of-database-drivers) and its respective [driver adapter](/orm/overview/databases/database-drivers#driver-adapters) for Prisma ORM.
 
-> **Note**: [Prisma Accelerate](/accelerate) enables you to access _any_ database from _any_ edge function provider. No edge-compatible driver is necessary.
-
 The edge-compatible drivers for Cloudflare Workers and Pages are:
 
 - [Neon Serverless](https://neon.tech/docs/serverless/serverless-driver) uses HTTP to access the database
@@ -30,7 +28,9 @@ The edge-compatible drivers for Cloudflare Workers and Pages are:
 - [`node-postgres`](https://node-postgres.com/) (`pg`) uses Cloudflare's `connect()` (TCP) to access the database
 - [`@libsql/client`](https://github.com/tursodatabase/libsql-client-ts) is used to access Turso databases
 
-> **Note**: There's [also work being done](https://github.com/sidorares/node-mysql2/pull/2289) on the `node-mysql2` driver which will enable access to traditional MySQL databases from Cloudflare Workers and Pages as well.
+There's [also work being done](https://github.com/sidorares/node-mysql2/pull/2289) on the `node-mysql2` driver which will enable access to traditional MySQL databases from Cloudflare Workers and Pages in the future as well.
+
+> **Note**: [Prisma Accelerate](/accelerate) enables you to access _any_ database from _any_ edge function provider. No edge-compatible driver is necessary.
 
 ### Setting your database connection URL as an environment variable