From de6b39e2ee206c0e04d4af26d71deedb0180669e Mon Sep 17 00:00:00 2001
From: Kathy <153706637+kathayl@users.noreply.github.com>
Date: Thu, 17 Jul 2025 10:37:14 -0700
Subject: [PATCH] Update limits.mdx

remove pricing bit since we have pricing page + have announced pricing
---
 src/content/docs/browser-rendering/platform/limits.mdx | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/src/content/docs/browser-rendering/platform/limits.mdx b/src/content/docs/browser-rendering/platform/limits.mdx
index 2b35edd2aafebea..14fb96637ecc750 100644
--- a/src/content/docs/browser-rendering/platform/limits.mdx
+++ b/src/content/docs/browser-rendering/platform/limits.mdx
@@ -41,8 +41,3 @@ To increase this limit, you’ll need to [upgrade to a Workers Paid plan](/worke
 ## Note on concurrency
 
 While the limits above define the maximum number of concurrent browser sessions per account, in practice you may not need to hit these limits. Browser sessions close automatically—by default, after 60 seconds of inactivity or upon task completion—so if each session finishes its work before a new request comes in, the effective concurrency is lower. This means that most workflows do not require very high concurrent browser limits.
-
-## Pricing
-
-Browser Rendering service is currently available at no cost up to the limits specified above **until billing begins**. Pricing to be announced and we will provide advance notice before any billing begins.
-