Update src/content/docs/browser/new-relic-browser/troubleshooting/bro…

…wser-data-doesnt-match-other-analytics-tools.mdx

Co-authored-by: ally sassman <42753584+ally-sassman@users.noreply.github.com>

src/content/docs/browser/new-relic-browser/troubleshooting/browser-data-doesnt-match-other-analytics-tools.mdx

@@ -26,7 +26,7 @@ Follow these troubleshooting steps for browser monitoring:
 2. If the JavaScript snippets are missing, or if users are unable to send data to New Relic, follow the steps for [troubleshooting browser monitoring installation](/docs/browser/new-relic-browser/installation-configuration/troubleshooting-browser-monitoring-installation).
 3. If you have a single-page style application and are expecting to see your route changes as views, consider using [browser SPA monitoring](/docs/browser/single-page-app-monitoring/get-started/welcome-single-page-app-monitoring), which provides an integrated view of both initial page loads and route changes.
 
-If browser monitoring is working properly, you may be seeing different results because New Relic collects and presents information differently from other analytics tools. For instance, `JavascriptErrors` and `AjaxRequest` are individually monitored and their data depends on when our agent observes them and what we can or decide to capture. For `BrowserInteraction`, we use our own custom instrumentation. And for vitals and metrics under `PageViewTiming` and `PageView`, the web-vitals library owned by Chrome team is the source of that data.
+If browser monitoring is working properly, you may be seeing different results because New Relic collects and presents information differently from other analytics tools. For instance, `JavascriptErrors` and `AjaxRequest` are individually monitored and their data depends on when our agent observes them and what we can or decide to capture. For `BrowserInteraction`, we use our own custom instrumentation, and for vitals and metrics under `PageViewTiming` and `PageView`, the web-vitals library owned by Chrome team is the source of that data.
 
 For more information on how we collect data, see: