Add info about new legacy browser filters (#9096)

docs/product/data-management-settings/filtering/index.mdx

@@ -15,16 +15,25 @@ These filters are exclusively applied at ingest time and not later in processing
 Inbound filters include:
 
 - Common browser extension errors
+- Transactions coming from health checks and ping requests
+- Events coming from legacy browsers
 - Events coming from localhost
-- Known legacy browsers errors
-- Known web crawlers
-- By their error message
-- From specific release versions of your code
-- From certain IP addresses
+- Errors from known web crawlers
 - React hydration errors
-- Transactions coming from healthcheck and ping requests
+- ChunkLoadErrors
+- Events from certain IP addresses
+- Events with certain error messages
+- Events from specific release versions of your code
 
-### Transactions coming from healthcheck
+### Legacy Browser Filters
+
+The legacy browser filters allow you to filter out certain legacy versions of browsers that are known to cause problems. 
+
+Legacy browser filters were updated in Feb 2024 and will be periodically evaluated to include additional legacy versions.
+
+If you had a legacy browser filter on before the update, the old filter will appear in your settings as "Deprecated". Deprecated legacy browser filters still work. However, if you turn them off, you won’t be able to turn them on again and will need to use the new filters instead.
+
+### Transactions Coming from Health Check
 
 In essence, the health check filter serves the purpose of excluding transactions that are generated as a part of health check procedures.