Update filtering.mdx

Author: lcian

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

@@ -22,35 +22,8 @@ All Sentry SDKs support the <PlatformIdentifier name="before-send" /> callback m
 
 Note also that breadcrumbs can be filtered, as discussed in [our Breadcrumbs documentation](/product/error-monitoring/breadcrumbs/).
 
-### Using Hints
-
-Hints are available in two places:
-
-1. <PlatformIdentifier name="before-send" /> / <PlatformIdentifier name="before-breadcrumb" />
-2. `eventProcessors`
-
-Event and breadcrumb `hints` are objects containing various information used to put together an event or a breadcrumb. Typically `hints` hold the original exception so that additional data can be extracted or grouping can be affected.
-
-For events, hints contain properties such as `event_id`, `originalException`, `syntheticException` (used internally to generate cleaner stack trace), and any other arbitrary `data` that you attach.
-
-For breadcrumbs, the use of `hints` depends on the type of breadcrumb.
-
 <PlatformContent includePath="configuration/before-send-fingerprint">
 
 In this example, the fingerprint is forced to a common value if an exception of a certain type has been caught:
 
 </PlatformContent>
-
-#### Hints for Events
-
-`originalException`
-
-The original exception that caused the Sentry SDK to create the event. This is useful for changing how the Sentry SDK groups events or to extract additional information.
-
-`syntheticException`
-
-When a string or a non-error object is raised, Sentry creates a synthetic exception so you can get a basic stack trace. This exception is stored here for further data extraction.
-
-#### Hints for Breadcrumbs
-
-<PlatformContent includePath="configuration/breadcrumb-hints" />