diff --git a/adr/ADR-31.md b/adr/ADR-31.md
index 7d92814..0dede14 100644
--- a/adr/ADR-31.md
+++ b/adr/ADR-31.md
@@ -133,7 +133,7 @@ If we did a normal multi read using `{"multi_last":["$KV.USERS.1234.>"]}` we wou
 
 A `batch` parameter can be added to restrict the result set to a certain size, otherwise the server will decide when to end the batch using the same `EOB` marker message seen in Batched Mode with the addition of the `Nats-UpTo-Sequence` header
 
-When the server cannot send any more data it will respond, like the above Batch, with a zero length payload message will be sent with the `Nats-Num-Pending` and `Nats-Last-Sequence` headers set that clients can use to determine if further batch calls are needed. It would also have the `Status` header set to `204` with the `Description` header being `EOB`. Additionally the `Nats-UpTo-Sequence` would be set that indicates the last matching message in the stream that matched criteria.  This number would be used in subsequent requests as the `up_to_seq` value to ensure batches of multi-gets are done around a consistent point in time.
+When the server cannot send any more data it will respond, like the above Batch, with a zero-length payload message including the `Nats-Num-Pending` and `Nats-Last-Sequence` headers enabling clients to determine if further batch calls are needed. In addition, it would also have the `Status` header set to `204` with the `Description` header being `EOB`. The `Nats-UpTo-Sequence` header will be set indicating the last message in the stream that matched criteria. This number would be used in subsequent requests as the `up_to_seq` value to ensure batches of multi-gets are done around a consistent point in time.
 
 #### Response Format