Merge pull request #17793 from ssimp44/patch-5

Remove references to "planning for paid consumption" from Session Replay

src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay.mdx

@@ -45,7 +45,7 @@ By default, browser event data is stored 8 days, but actual data retention depen
 
 For more details on session replay, see the following sections:
 
-* [Data consumption](#view-consumption): View data consumption and plan for transitioning to paid consumption.
+* [Data consumption](#data-consumption): View or project data consumption.
 * [User privacy and security concerns](#data-security): Learn how we protect your user data and meet privacy requirements.
 * [Session replay and your app's performance](#app-performance): Learn how session replay minimizes impact on your app's performance.
 
@@ -390,8 +390,6 @@ Here's an example mutation and variables to create a new browser application wit
 
 ## Data consumption [#data-consumption]
 
-### Plan for paid consumption [#plan-for-paid-consumption]
-
 Session replay follows the same consumption pricing as your other browser bytes. The amount of bytes produced depends on the count, length, and user-activity levels of sessions, as well as the complexity of your site's DOM.
 
 The most accurate way to project your cost per replay is to enable the feature for a short test period and measure your actual consumption. Alternatively, you can use an average of 5.3 MB per replay as a rough approximation, though keep in mind that your actual cost may vary significantly. A simple formula to project your approximate costs is: `sessions` x `sampling_rate` x `gb_per_replay` x `cost_per_gb`