Add minor SEO edits for js/filtering (#12862)

Co-authored-by: Alex Krawiec <[email protected]>

Author: coolguyzone

docs/platforms/javascript/common/configuration/filtering.mdx

@@ -1,14 +1,14 @@
 ---
 title: Filtering
 sidebar_order: 60
-description: "Learn more about how to configure your SDK to filter events reported to Sentry."
+description: "Learn more about how to configure your JavaScript SDK to set up filtering for events reported to Sentry."
 ---
 
 When you add Sentry to your app, you get a lot of valuable information about errors and performance. And lots of information is good -- as long as it's the right information, at a reasonable volume.
 
 Sentry offers [Inbound Filters](/concepts/data-management/filtering/) that you can enable per project to filter out various events in sentry.io. You can use our pre-defined inbound filters (e.g. filtering known browser extensions), as well as add your own message-based filters.
 
-However, we recommend filtering at the client-level, because it removes the overhead of sending events you don't actually want. The Sentry SDKs have several configuration options, which are described in this document, to help you filter out events. To learn more about the event fields you can use for filtering, see [Event Payloads](https://develop.sentry.dev/sdk/data-model/event-payloads/).
+However, we recommend filtering at the client-level, because it removes the overhead of sending events you don't actually want. The [Sentry SDKs](/platforms/) have several configuration options, which are described in this document, to help you filter out events. To learn more about the event fields you can use for filtering, see [Event Payloads](https://develop.sentry.dev/sdk/data-model/event-payloads/).
 
 ## Filtering Error Events