fix(develop): Clarify that before_send should not apply to check-ins (#14972)

Author: sl0thentr0py

develop-docs/sdk/expected-features/index.mdx

@@ -233,7 +233,7 @@ Whenever possible, avoid adding the attachment altogether if taking the screensh
 
 ## Before-Send Hook
 
-Hook called with the event (and on some platforms the hint) that allows the user to decide whether an event should be sent or not.  This can also be used to further modify the event. This only works for `error` events. For `transactions` it is recommended to have `beforeSendTransaction` implemented in SDKs. To understand when you should call this in your SDK, please refer to the [error filter ordering of sessions](/sdk/telemetry/sessions/#filter-order).
+Hook called with the event (and on some platforms the hint) that allows the user to decide whether an event should be sent or not.  This can also be used to further modify the event. This only works for `error` events. Other event types like `transactions` and `check-ins` **should not** go through `beforeSend`. For `transactions` it is recommended to have `beforeSendTransaction` implemented in SDKs. For `check-ins` you can optionally implement `beforeSendCheckIn`. To understand when you should call this in your SDK, please refer to the [error filter ordering of sessions](/sdk/telemetry/sessions/#filter-order).
 
 ## Before-Breadcrumb Hook
 

develop-docs/sdk/telemetry/check-ins.mdx

@@ -159,3 +159,7 @@ monitors frontend APIs.
 `unit`
 
 : **String, required**. The interval unit. Should be one of `year`, `month`, `week`, `day`, `hour`, `minute`.
+
+## Interaction with `beforeSend`
+
+Check-in events in the SDK should **not** go through `beforeSend`. SDKs can optionally implement a dedicated `beforeSendCheckIn` hook that only applies to check-in events.