From 8f1fc6800e42c02d8d7bbda5f1960ddc3e018a16 Mon Sep 17 00:00:00 2001
From: jcol <116673918+jeff-colucci@users.noreply.github.com>
Date: Tue, 15 Oct 2024 13:25:44 -0500
Subject: [PATCH] Update
 src/content/docs/browser/new-relic-browser/troubleshooting/browser-data-doesnt-match-other-analytics-tools.mdx

Co-authored-by: ally sassman <42753584+ally-sassman@users.noreply.github.com>
---
 .../browser-data-doesnt-match-other-analytics-tools.mdx         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/docs/browser/new-relic-browser/troubleshooting/browser-data-doesnt-match-other-analytics-tools.mdx b/src/content/docs/browser/new-relic-browser/troubleshooting/browser-data-doesnt-match-other-analytics-tools.mdx
index 113af6e70a0..54b9a7b1871 100644
--- a/src/content/docs/browser/new-relic-browser/troubleshooting/browser-data-doesnt-match-other-analytics-tools.mdx
+++ b/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)