Apply suggestions from code review

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

Author: 3 people

develop-docs/sdk/telemetry/feedbacks.mdx

@@ -131,10 +131,10 @@ The scope is applied to the feedbacks, including tags, attachments, and trace co
 
 [Rate limiting](/sdk/expected-features/rate-limiting/) is applied to feedbacks in the same way as it is applied to events.
 
-### Dropped feedback reports
+### Dropped Feedback Reports
 
-There is no sample rate for feedbacks, as they are always sampled. However, a feedback can be discarded at any of the pipeline stages. The SDK should report dropped feedbacks through [client reports](/sdk/telemetry/client-reports/).
+There is no sample rate for feedbacks, as they are always sampled. However, a feedback can be discarded at any of the pipeline stages, for reasons like rate limiting or an invalid message (too large or empty). The SDK should report dropped feedbacks through [client reports](/sdk/telemetry/client-reports/).
 
 ### Session Replay Integration
 
-SDKs are expected to flush the current Session Replay, if running. This ensures a meaningful replay recording exists and can be included in the `replay_id` attribute of the feedback context.
+When sending feedback, SDKs are expected to flush the current Session Replay, if running. This ensures a meaningful replay recording exists and can be included in the `replay_id` attribute of the feedback context.