Update faq.mdx

deleted FAQ questions that I've moved to Pricing FAQ and Limits FAQ

Author: kathayl

src/content/docs/browser-rendering/faq.mdx

@@ -87,27 +87,3 @@ It may be because you increased the height and width of the viewport. To fix thi
 This error indicates you have hit the daily browser-instance limit on the Workers Free plan. [Free-plan accounts are capped at free plan limit is 10 minutes of browser use a day](/browser-rendering/platform/limits/#workers-free) once you exceed those, further creation attempts return a 429 until the next UTC day.
 
 To resolve: [Upgrade to a Workers Paid plan](/workers/platform/pricing/) which allows for more than 10 minutes of usage a day and has higher [limits](/browser-rendering/platform/limits/#workers-paid). If you recently upgraded but still see this error, try redeploying your Worker to ensure your usage is correctly associated with your new plan. 
-
-## Billing & Limits
-
-### What are the usage limits for Browser Rendering and how do I estimate my costs? --> DELETE LIMITS PORTION AND MOVE 2nd PART TO PRICING
-
-You can view the complete breakdown of concurrency caps, request rates, timeouts, and REST API quotas on the [limits page](/browser-rendering/platform/limits/).
-
-You can monitor your Browser Rendering usage in the [Cloudflare dashboard](https://dash.cloudflare.com). Go to **Compute (Workers)** > **Browser Rendering**. Then, you can use [the pricing page](/browser-rendering/platform/pricing/) to estimate your costs.
-
-### I upgraded from the Workers Free plan, but I'm still hitting the 10-minute per day limit. What should I do? --> LIMITS PAGE
-
-If you recently upgraded to the [Workers Paid plan](/workers/platform/pricing/) but still encounter the 10-minute per day cap, redeploy your Worker to ensure your usage is correctly associated with the new plan.
-
-### How can I manage concurrency and session isolation with Browser Rendering? --> LIMITS + keep in Development of FAQ?
-
-If you are hitting concurrency [limits](/browser-rendering/platform/limits/#workers-paid), or want to optimize concurrent browser usage with the [Workers Binding method](/browser-rendering/workers-bindings/), here are a few tips:
-
-- Optimize with tabs or shared browsers: Instead of launching a new browser for each task, consider opening multiple tabs or running multiple actions within the same browser instance. 
-- [Reuse sessions](/browser-rendering/workers-bindings/reuse-sessions/): You can optimize your setup and decrease startup time by reusing sessions instead of launching a new browser every time. If you are concerned about maintaining test isolation, for example for tests that depend on a clean environment, we recommend using [incognito browser contexts](https://pptr.dev/api/puppeteer.browser.createbrowsercontext), which isolate cookies and cache with other sessions. 
-
-If you are still running into concurrency limits you can [request a higher limit](https://forms.gle/CdueDKvb26mTaepa9). 
-
-###  Do failed API calls, such as those that time out, add to billable browser hours? --> PRICING
-No. If a request to the Browser Rendering REST API fails with a `waitForTimeout` error, the browser session is not charged.