feat(content): TW feedback

src/content/docs/tutorial-app-performance/guide-to-monitoring-core-web-vitals.mdx

@@ -204,7 +204,7 @@ Let's say your organization recently updated images on the site’s home page on
 
 ## Get more context with session traces [#session-traces]
 
-New Relic captures data about a user's session on a given page. Session traces are randomly sampled and recorded in New Relic, letting you view how a user experienced page load timing issues, JavaScript events, or other errors. 
+New Relic captures data about a user's session on a given page. Session traces are randomly sampled, letting you view how a user experienced page load timing issues, JavaScript events, or other errors. 
 
 <img
     title="Session traces in the New Relic UI"
@@ -214,9 +214,9 @@ New Relic captures data about a user's session on a given page. Session traces a
 
 We recommend using session traces to find patterns across different user sessions. If one of your core web vitals scores could be improved, one option is to look at session traces to see what common attributes are shared across different user sessions. Here's an example of how session traces can help you improve your site:
 
-1. From the **Web vitals** tab, click the page that's performing poorly. Using the above image, you see that your site has a good overall LCP score, but you also notice some of your individual pages need improvement. 
-2. Looking at the **Page URLs** section of the **Web vitals** page, you see that your homepage URL has an LCP score of greater than four seconds. Is this due to an error that affects all users, or is it only affecting one kind of user? For example, do you notice that users with one version of Chrome or a certain operating system are experiencing slow page load times? 
-3. A new window will populate when you click the URL you want to troubleshoot. You notice that your LCP score is much higher than your site's overall LCP score. Scrolling to the **Session traces** section at the bottom of this page, you see various samples of real user sessions. Are users on a certain Chrome version experiencing the same error? Is it related to a specific AJAX request or DOM loading?
+1. From the **Web vitals** tab, click the page that's performing poorly. Using the above image as an example, you see that your site has a good overall LCP score, but you also notice some of your individual pages need improvement. 
+2. Looking at the **Page URLs** section of the **Web vitals** page, you see that your homepage URL has an LCP score of greater than four seconds. Is this due to an error that affects all users, or is it only affecting one kind of user? For example, if you notice that users with one version of Chrome or a certain operating system are experiencing slow page load times, you can better troubleshoot the specific cause of an issue. 
+3. A new window will populate when you click the URL you want to troubleshoot. You notice that your LCP score is much higher than your site's overall LCP score. Scrolling to the **Session traces** section at the bottom of this page, you see various samples of real user sessions. These sessions can give you more granular detail about how that user experienced AJAX requests, issues related to DOM loading, JavaScript events or other errors.  
 
 Data from randomized sessions helps you find patterns across hundreds or thousands of user interactions with a web page. If a pattern appears in this randomly selected data, you can have more confidence that your plan to resolve an issue will improve your page scores. 
 

src/content/docs/tutorial-app-performance/performance-benchmarks.mdx

@@ -8,7 +8,7 @@ redirects:
 
 import sonicSliUiOverview from 'images/sonic_screenshot-full_sli-ui-overview.webp'
 
-Your system architecture is made up of hosts, apps, and services that affect and depend on each other. If one part of your architecture underperforms, it can create a cascading chain of events that could lead to critical system outages. Service levels, however, let you apply thresholds that make keeping track of your system easier. If performance on a service exceeds or falls below a given threshold, you receive an alert. Here are the layers to service levels: 
+Your system architecture is made up of hosts, apps, and services that affect and depend on each other. If one part of your architecture underperforms, it can later lead to critical system outages. Service levels, however, let you apply thresholds that make keeping track of your system easier. If performance on a service exceeds or falls below a given threshold, you receive an alert. Here are the layers to service levels: 
 
 * A service level is made up of service level objectives (SLOs). SLOs are goals that represent how you expect your services to behave. 
 * Your SLOs are defined by service level indicators (SLIs). SLIs are key measurements and metrics that determine service availability.