batching: clarify idempotency behavior in server-side batching explanation

src/pages/docs/messages/batch.mdx

@@ -18,7 +18,7 @@ It makes messages more cost efficient in high-throughput scenarios by reducing t
 Server-side batching is effective in applications such as fan engagement platforms, where key moments in a game, such as points being scored, cause huge surges in the number of reactions and messages. It also enables a much higher number of users to be [present](/docs/presence-occupancy/presence) on a channel when it is enabled.
 
 <Aside data-type="important">
-Be aware that server-side batching doesn't support [idempotency](/docs/pub-sub/advanced#idempotency) due to how messages are grouped on the server. However, if you are explicitly setting a message ID, then these messages will be excluded from being batched.
+Be aware that server-side batching doesn't support [idempotency](/docs/pub-sub/advanced#idempotency) due to how messages are grouped on the server. Messages with an explicitly set ID are still batched, but they **won't** be deduplicated based on that ID.
 </Aside>
 
 ### Configure server-side batching <a id="configure"/>