diff --git a/includes/sdk-troubleshooting-and-debugging/browser.md b/includes/sdk-troubleshooting-and-debugging/browser.md
index d50b226c1..296310d62 100644
--- a/includes/sdk-troubleshooting-and-debugging/browser.md
+++ b/includes/sdk-troubleshooting-and-debugging/browser.md
@@ -63,7 +63,7 @@ If you have set up an API proxy and run into configuration issues related to tha
 
 ##### Events fired but no network requests
 
-If you [set the logger to "Debug" level](./#debug-mode), and see track calls in the developer console, the `track()` method has been called. If you don't see the corresponding event in Amplitude, the Amplitude Instrumentation Explorer Chrome extension, or the network request tab of the browser, the event wasn't sent to Amplitude. Events are fired and placed in the SDK's internal queue upon a successful `track()` call, but sometimes these queued events may not send successfully. This can happen when an in-progress HTTP request is cancelled. For example, if you close the browser or leave the page with a `history.push()` event in React.
+If you [set the logger to "Debug" level](./#debug-mode), and see track calls in the developer console, the `track()` method has been called. If you don't see the corresponding event in Amplitude, the Amplitude Instrumentation Explorer Chrome extension, or the network request tab of the browser, the event wasn't sent to Amplitude. Events are fired and placed in the SDK's internal queue upon a successful `track()` call, but sometimes these queued events may not send successfully. This can happen when an in-progress HTTP request is cancelled. For example, if you close the browser or leave the page.
 
 There are two ways to address this issue: