chore: wording fixes

Author: giortzisg

develop-docs/sdk/telemetry/telemetry-buffer/backend-telemetry-buffer.mdx

@@ -86,14 +86,14 @@ Configurable via weights.
 Each telemetry category maintains a store interface; a fixed-size circular array/ring buffer (not to be confused with the `Buffer` wrapper) that stores items before transmission:
 
 - **Bounded capacity**: Default to 100 items for errors, logs, and monitors; 1000 for transactions. This prevents unbounded memory growth regardless of telemetry volume and backpressure handling.
-- **Overflow policies**:
-  - `drop_oldest` (default): Evicts the oldest item when the buffer is full, making room for new data.
+- **Overflow policies** (optional):
+  - `drop_oldest` (default): Evicts the oldest item when the buffer is full, making room for new data. This should be the normal SDK behavior.
   - `drop_newest`: Rejects incoming items when full, preserving what's already queued.
 - **Batching configuration**:
   - `batchSize`: Number of items to combine into a single batch (1 for errors, transactions, and monitors; 100 for logs).
   - `timeout`: Maximum time to wait before sending a partial batch (5 seconds for logs).
 - **Bucketed Storage Support**: The storage interface should satisfy both bucketed and single-item implementations, allowing sending spans per trace id (required for Span First).
-- **Observability**: Each store tracks dropped item counts for client reports.
+- **Observability**: Each store tracks dropped item counts for client reports. Depending on implementation we can either send reports by adding them to existing events or on a timeout basis (Consult [Client Reports](https://develop.sentry.dev/sdk/telemetry/client-reports/#envelope-item-payload) for more details). In both cases our source of truth is the dropped counter.
 
 ##### Single-item ring buffer (default)