fix(browser): Apply suggestions from code review

Co-authored-by: Bradley Camacho <[email protected]>

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

@@ -23,7 +23,7 @@ import browserErrorsInboxSessionReplay from 'images/browser_screenshot-full_erro
 
 Session replay allows you to play back user interactions on your web app and map 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 showing you 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.
+* **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.
 * **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.
 
@@ -94,7 +94,7 @@ Session replay works by taking a snapshot of the end-user's DOM (Document Object
   <Step>
     ### Configure session sampling rates [#configure-sampling-rates]
 
-    Make selections for the following sampling rates:
+Set a sampling rate (0%-100%) for the following samples:
 
     * **Session sampling rate** records a random sample of all user sessions.
 
@@ -122,7 +122,7 @@ For example, if you set the session sampling rate to 50% and the error sampling
 
 If you need to change the default privacy settings, you can choose specific classes and attributes to mask, block, or ignore:
 
-    * **Mask** means specific text will be replaced with asterisks (*). For example, you could mask sensitive user input such as login information.
+**Mask** means specific text will be replaced with asterisks (*). For example, you could mask sensitive user input such as login information.
 
 
 
@@ -133,7 +133,7 @@ If you need to change the default privacy settings, you can choose specific clas
   >
       If you want to customize exactly what is masked with asterisks, you have a few options:
 
-        * On the Application settings page, add your own CSS selectors or check the masking boxes.
+        * On the **Application settings** page, add your own CSS selectors or check the masking boxes.
 
                 <img
                     title="Mask settings"
@@ -155,7 +155,7 @@ If you need to change the default privacy settings, you can choose specific clas
   </Collapser>
   </CollapserGroup>
 
-    * **Block** means content will be replaced with an empty placeholder. For example, if you have a video playing on your About Us webpage and don’t want it captured, you could block the class that contains that video.
+**Block** means content will be replaced with an empty placeholder. For example, if you have a video playing on your About Us webpage and don’t want it captured, you could block the class that contains that video.
 
 
 
@@ -191,7 +191,7 @@ If you need to change the default privacy settings, you can choose specific clas
             </Collapser>
             </CollapserGroup>
 
-    * **Ignore** means user input will be ignored entirely. For example, if you want to ignore sensitive information like a user's email address and password, you could ignore the element that contains those fields.
+**Ignore** means user input will be ignored entirely. For example, if you want to ignore sensitive information like a user's email address and password, you could ignore the element that contains those fields.
 
 
 
@@ -249,7 +249,7 @@ If you need to change the default privacy settings, you can choose specific clas
 In the UI, you can find session replays in two places:
 
   * On the **Session replay** page:
-        1. Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > All Capabilities > Browser**.
+        1. Go to **[one.newrelic.com > All Capabilities](https://one.newrelic.com/all-capabilities) > Browser**.
         2. Select your browser app.
         3. In the left-hand menu, scroll down and click **Session replay**.
         4. Click into each replay to view session details.
@@ -264,7 +264,7 @@ In the UI, you can find session replays in two places:
 
   * On the **Errors inbox** page:
         1. In the left-hand browser menu, click **Errors**.
-        2. Click on the Triage and Group errors pages to see replays attached to errors.
+        2. Click on the **Triage** and **Group errors** pages to see replays attached to errors.
 
         <img
             title="Replays in errors inbox"