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

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

Co-authored-by: ally sassman <[email protected]>

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

@@ -28,7 +28,7 @@ Follow these troubleshooting steps for browser monitoring:
 
 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 about how we collects data, see:
+For more information on how we collect data, see:
 
 * [Page load timing process](/docs/browser/new-relic-browser/page-load-timing-resources/page-load-timing-process)
 * [Instrumentation for browser monitoring](/docs/browser/new-relic-browser/page-load-timing-resources/instrumentation-browser-monitoring)