diff --git a/docs/platforms/javascript/common/best-practices/shared-environments.mdx b/docs/platforms/javascript/common/best-practices/shared-environments.mdx
index 0a1573273e450..5de050f9b9330 100644
--- a/docs/platforms/javascript/common/best-practices/shared-environments.mdx
+++ b/docs/platforms/javascript/common/best-practices/shared-environments.mdx
@@ -98,6 +98,9 @@ try {
 }
 ```
 
-If you notice that Sentry is not capturing error events from the browser extension,
-try disabling the Browser extension errors option in the Inbound Filters of your Sentry configuration.
+## Browser Extension Filter
+
+If you notice that Sentry is not capturing error events from the browser extension, an Inbound Filter might be active.
+You can disable that by going to your **Project Settings > Inbound Filters** and disabling filtering out errors known to be caused by browser extensions.
+
 Read more about Inbound Filters in the product documentation under [Inbound filters](/concepts/data-management/filtering/#inbound-data-filters).