Updated the changes by Vinay

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

@@ -8,11 +8,11 @@ freshnessValidatedDate: 2024-12-19
 
 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`. Here's an example:
+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`.
+
+Here's an example:
 
-```
 1 million (sessions) x 5% (sampling_rate) x 0.0053 (gb_per_replay) x $0.35 (cost_per_gb) = $92.75 for 50,000 replays
-```
 
 To control your consumption, [adjust your sampling rates](/docs/browser/browser-monitoring/browser-pro-features/session-replay/configuration/setup-session-replay/#configure-sampling-rates).
 
@@ -37,8 +37,14 @@ Session replay minimizes impact on your app's performance with:
 * **Performance optimization techniques**: Payload size can also increase if the DOM is large. However, session replay uses a number of techniques to reduce payload size, such as:
   * GZIP compression
   * Duplication reduction
-  * Strategic payload harvesting: It only sends a large (compressed) payload when the full DOM is captured, which typically only happens when the replay feature is first imported. After that, it will only send small payloads that relate to the user's actions. The browser agent will harvest on whatever happens first of the following:
-    * The payload reaches more than 64 KB compressed
-    * 60 seconds elapses
-    * The visibility of the page changes (tab change, focus, navigation, etc)
-    * The session ends
+  * Strategic payload harvesting: A large (compressed) payload is sent only when the full DOM is captured, which typically occurs when the replay feature is first imported. Subsequently, only small payloads related to the user's actions are sent. The browser agent will harvest data based on the first occurrence of the following conditions:
+    * The payload reaches more than 64 KB compressed.
+    * 60 seconds elapses.
+    * The visibility of the page changes (e.g., tab change, focus, navigation).
+    * The session ends.
+
+### Key Changes:
+
+- **Clarity:** Improved sentence structure for better readability.
+- **Conciseness:** Removed redundant words and phrases.
+- **Consistency:** Used parallel structure in the list for uniformity.

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

@@ -9,13 +9,13 @@ freshnessValidatedDate: 2024-12-19
 If needed, you can programmatically `force` a session replay to start or stop recording using API methods. Here are some use cases:
 
 * Allow users to opt in for interaction recording. For example, if you have a pop-up asking "Allow this session to be recorded for performance analysis?" and a user consents:
-  1. Call `newrelic.recordReplay()` to initiate recording.
-  2. Once the session is complete or consent is withdrawn, use `newrelic.pauseReplay()` to stop capturing data.
+  1. Call `newrelic.recordReplay()`, to initiate recording.
+  2. After the session is complete or consent is withdrawn, use `newrelic.pauseReplay()` to stop capturing data.
 * Record sessions based on specific criteria, such as:
   * Start recording only for sessions on specific URLs such as a product checkout flow.
   * Stop recording for sensitive pages such as `/billing` or `/health-records`.
 
-See the API documentation for instructions:
+Refer the API documentation for instructions:
 
 * [`newrelic.recordReplay`](/docs/browser/new-relic-browser/browser-apis/recordReplay/)
 * [`newrelic.pauseReplay`](/docs/browser/new-relic-browser/browser-apis/pauseReplay/)
@@ -27,10 +27,10 @@ You can prevent session replays from automatically starting, even when sampled,
 Setting `autoStart: false` instructs the agent to defer its initialization until explicitly called using `.start()`. This ensures that session replays will not be created at all, even if the backend samples your application for recording.
 
 <Callout variant="important">
-  Calling `.start()` does not guarantee that a session replay will be recorded. It simply delays the module import and evaluation of sampling results until this point. If you need to force a recording, see [Manually record session replays](#manual-replays).
+  Calling `.start()` does not guarantee that a session replay will be recorded. It simply delays the module import and evaluation of sampling results until this point. If you need to force a recording, refer [Manually record session replays](#manual-replays).
 </Callout>
 
-To start using this API, see [`newrelic.start`](/docs/browser/new-relic-browser/browser-apis/start/).
+To start using this API, refer [`newrelic.start`](/docs/browser/new-relic-browser/browser-apis/start/).
 
 ## Use Nerdgraph to configure replay settings [#nerdgraph-mutation]
 

src/content/docs/browser/browser-monitoring/browser-pro-features/session-replay/configuration/customize-privacy-settings.mdx

@@ -14,7 +14,7 @@ By default, all text and inputs are replaced with asterisks. Here's an example o
       src="/images/browser_screenshot-full_text-masking-example.webp"
     />
 
-  If this setting is appropriate, move onto the next step.
+  If this setting is appropriate, move on to the next step.
 
   If you need to customize what content or user input is captured, you have options to mask, block, or ignore specific classes and attributes of content or user input. Make sure to check with your privacy team before changing the privacy settings.
 
@@ -32,12 +32,10 @@ By default, all text and inputs are replaced with asterisks. Here's an example o
         src="/images/browser_screenshot-full_mask-settings.webp"
       />
   * Add our CSS class `nr-mask` or attribute `data-nr-mask` to your webpage HTML.
+
       For example, to mask an account ID from showing in the URL, add `nr-mask` to the `<div>` containing the account ID:
 
-      ````html
-      <div>Account ID: <span class="nr-mask">99881123</span></div>
-      ```
-      ````
+      `<div>Account ID: <span class="nr-mask">99881123</span></div>`
 
   These options use an asterisk (\*) to mask all text in that element, hiding the actual text but revealing the number of characters entered. However, asterisks are not valid numbers, so masking number type-specific fields such as telephone or credit card numbers will result in a blank field in a replay.
 

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

@@ -4,7 +4,7 @@ metaDescription: "Enable session replay to play back user interactions and impro
 freshnessValidatedDate: 2024-12-19
 ---
 
-Fully utilize session replay in New Relic, start by enabling this feature in your browser application settings. This step is essential for capturing user interactions on your web app, providing insights into user journeys, and troubleshooting issues effectively. Follow the steps below to enable session replay and ensure your browser agent is configured correctly.
+Utilize session replay in New Relic, start by enabling this feature in your browser application settings. This step is essential for capturing user interactions on your web app, providing insights into user journeys, and troubleshooting issues effectively. Follow the steps below to enable session replay and ensure your browser agent is configured correctly.
 
 ## Enable session replay [#enable-session-replay]
 
@@ -16,9 +16,9 @@ Fully utilize session replay in New Relic, start by enabling this feature in you
 
     4. On the <DNT>**Application settings**</DNT> page, make sure <DNT>**Pro**</DNT> or <DNT>**Pro + SPA**</DNT> browser agent is selected. Session replay is not available for the Lite browser agent.
 
-    5. Toggle ON <DNT>**Session tracking**</DNT> and <DNT>**Session replay**</DNT> settings.
+    5. Toggle <DNT>**Session tracking**</DNT> ON and <DNT>**Session replay**</DNT> settings.
 
-## Configure sampling rates [#configure-sampling-rates]
+## Setting sampling rates [#configure-sampling-rates]
 
 Set a sampling rate (0%-100%) for the following samples:
 

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

@@ -8,8 +8,8 @@ freshnessValidatedDate: 2024-12-19
 
 Session replay captures interactions on your web app and maps other telemetry data to help you understand your user's journeys. Session replay can be used for troubleshooting and improving the end-user experience, such as:
 
-* **Troubleshooting JavaScript errors**: Troubleshoot the cause of an error by seeing what the user was doing when the error occurred. For example, if an end user receives an error while trying to complete an ecommerce transaction, you can use session replay to see which steps they took and what data they entered before the error occurred. This can help you quickly identify and fix the root cause of the problem.
-* **Improving the user experience**: Discover areas of your web app that are causing users frustration. For example, you might see that users are getting lost in your navigation or clicking on buttons that don't do anything.
+* **Troubleshooting JavaScript errors**: Troubleshoot the cause of an error by viewing what the user was doing when the error occurred. For example, if an end user receives an error while trying to complete an ecommerce transaction, you can use session replay to view which steps they took and what data they entered before the error occurred. This can help you quickly identify and fix the root cause of the problem.
+* **Improving the user experience**: Discover areas of your web app that are causing users frustration. For example, users might get lost in your navigation or click on buttons that don't function.
 * **Identifying issues in key user journeys**: Identify areas of your web app that are causing performance problems. For example, if session replay reveals the `/cart/checkout` page is experiencing excessive page load time, you'd prioritize fixing this critical user journey.
 
 <img
@@ -29,7 +29,7 @@ Replays store up to:
 
 By default, browser event data is stored 8 days, but actual data retention depends on your account.
 
-For more details on session replay, see the following sections:
+For more details on session replay, refer the following sections:
 
 * [Data consumption](/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information/#data-consumption): View or project data consumption.
 * [User privacy and security concerns](/docs/browser/browser-monitoring/browser-pro-features/session-replay/additional-information/#data-security): Learn how we protect your user data and meet privacy requirements.

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

@@ -4,7 +4,7 @@ metaDescription: "Manage session replay & modify capabilities depending on the r
 freshnessValidatedDate: 2024-12-19
 ---
 
-Manage session replay & modify capabilities provides instructions on utilizing the new user management access functionality, enabling Admins to control who can modify Session replay settings by customizing user roles and access.
+Manage session replay and modification capabilities using the user management access functionality. This feature enables customization of user roles and access permissions to define who can modify session replay settings.
 
 ## Delete all product admin role [#modify-all-admin-role]
 
@@ -75,7 +75,7 @@ Manage session replay & modify capabilities provides instructions on utilizing t
   </Step>
 
   <Step>
-    Expand the **Account acess** section and in the **Add account roles to this group** select the following:
+    Expand the **Account acess** section, and in the **Add account roles to this group** field, select the following:
 
     * **Select a role**
     * **Select an account**
@@ -104,7 +104,7 @@ Manage session replay & modify capabilities provides instructions on utilizing t
   </Step>
 
   <Step>
-    Select the <DNT>**Modify**</DNT> checkbox for <DNT>**Session replays**</DNT>.
+    In the <DNT>**Session replays**</DNT> section select the <DNT>**Modify**</DNT> checkbox.
   </Step>
 
   <Step>

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

@@ -4,15 +4,15 @@ metaDescription: "Troubleshoot common issues with session replay in New Relic Br
 freshnessValidatedDate: 2024-12-19
 ---
 
-This is the first step in diagnosing your New Relic Session replays problem yourself, use this guide to resolve issues quickly.
+This is the first step in diagnosing your New Relic Session replays problem yourself.
 
 If you don't find your problem listed here, you can always reach out to [New Relic Support](https://support.newrelic.com).
 
-## Not seeing replays in the UI [#not-seeing-replay]
+## Replays not visible in the UI [#not-seeing-replay]
 
 ### Problem
 
-  Session replay feature is enabled, but you're not seeing any replays.
+  Session replay feature is enabled, but you're not able to view any replays.
 
 ### Solution
 
@@ -22,26 +22,26 @@ If you don't find your problem listed here, you can always reach out to [New Rel
     * Ensure you have permission to view replays.
     * Make sure you're using the Pro or Pro+SPA version of the browser agent. Session replay does not work with the Lite browser agent.
     * Make sure your browser agent meets these requirements:
-      * Agent version v1.260.0 or greater. We recommend [upgrading to the latest agent version](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes) as we continue making improvements.
+      * Agent version v1.260.0 or later. We recommend [upgrading to the latest agent version](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes) as we continue making improvements.
       * Agent type: Pro or Pro+SPA. Session replay does not work with the Lite browser agent.
       * [Session tracing](/docs/browser/browser-monitoring/browser-pro-features/session-traces-explore-webpages-life-cycle/#requirements) is enabled.
     * Your end-user's browser supports the browser-level APIs needed to record a session replay (verify compatibility at [MutationObserver](https://caniuse.com/mutationobserver)).
-    * In [Errors inbox](/docs/errors-inbox/errors-inbox/), filter your views so that you always see a replay. By default, browser event data is stored 8 days, but actual data retention depends on your account.
+    * In [Errors inbox](/docs/errors-inbox/errors-inbox/), filter your views so that you always  a replay. By default, browser event data is stored 8 days, but actual data retention depends on your account.
     * If you're using the copy/paste deployment method, make sure you [updated your agent code](#update-snippet).
-    * If you’re using the APM deployment method, you may need to wait a while for session replay to be automatically enabled. If you’re still not seeing data, try restarting the agent.
-    * If you're [dropping](https://docs.newrelic.com/docs/data-apis/manage-data/drop-data-using-nerdgraph/) PageView event data, Session Replays may not display in the UI.
+    * If you use the APM deployment method, you may need to wait for session replay to enable automatically. If data is still not visible, try restarting the agent.
+    * If you're [dropping](https://docs.newrelic.com/docs/data-apis/manage-data/drop-data-using-nerdgraph/) PageView event data, Session Replays may not appear in the UI.
 
-## Replays not displaying correctly [#replays-not-displaying]
+## Replays not appearing correctly [#replays-not-appearing]
 
 ### Problem
 
-  You're seeing replays, but they're not displaying correctly.
+  You can view replays, but they are not appearing correctly.
 
   This may be because your CSS files are hosted on a separate domain and Cross-Origin Resource Sharing (CORS) security measures are preventing our agent from accessing the CSS files. This can result in incomplete or inaccurate replays, as essential styling information may be missing.
 
   Here's what's happening behind the scenes:
 
-    * Session replay works by rebuilding the user's DOM, which includes your website's structure and visual elements. To achieve this, our agent needs to access your CSS files to accurately capture styling information. We then inline these styles directly into the replay recording, eliminating the need to reference the original CSS files during playback.
+    * Session replay rebuilds the user's DOM, capturing your website's structure and visual elements. To achieve this, our agent accesses your CSS files to accurately capture styling information. These styles are then embedded directly into the replay recording, removing the need to reference the original CSS files during playback.
 
     * If your CSS files are hosted on a separate domain, CORS may prevent our agent from accessing them.
 
@@ -55,11 +55,11 @@ If you don't find your problem listed here, you can always reach out to [New Rel
   <link rel="stylesheet" href="assets.yoursite.com/styles.css" crossorigin="anonymous">
 ```
 
-## Not seeing replays in your iframes [#no-replays-in-iframes]
+## Replays not visible in your iframes [#no-replays-in-iframes]
 
 ### Problem
 
-  Session replay feature is enabled, but you're not seeing replay data for iframe content.
+  Session replay feature is enabled, but you're not able to view replay data for iframe content.
 
 ### Solution
 

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

@@ -47,7 +47,7 @@ Start analyzing the captured data in New Relic. This section provides instructio
       </Step>
 
       <Step>
-        Click on the <DNT>**Triage**</DNT> and <DNT>**Group errors**</DNT> pages to see replays attached to errors.
+        Click <DNT>**Triage**</DNT> and <DNT>**Group errors**</DNT> pages to see replays attached to errors.
 
          <img
            title="Replays in errors inbox"