diff --git a/src/content/docs/queues/configuration/batching-retries.mdx b/src/content/docs/queues/configuration/batching-retries.mdx
index 85f77691120b9fd..9a33a204c33572f 100644
--- a/src/content/docs/queues/configuration/batching-retries.mdx
+++ b/src/content/docs/queues/configuration/batching-retries.mdx
@@ -308,7 +308,7 @@ Messages can be delayed by default at the queue level, or per-message (or batch)
 
 You can apply a backoff algorithm to increasingly delay messages based on the current number of attempts to deliver the message.
 
-Each message delivered to a consumer includes an `attempts` property that tracks the number of delivery attempts made.
+Each message delivered to a consumer includes an `attempts` property that tracks the number of delivery attempts made (including the current attempt).
 
 For example, to generate an [exponential backoff](https://en.wikipedia.org/wiki/Exponential_backoff) for a message, you can create a helper function that calculates this for you:
 
@@ -379,4 +379,4 @@ class Default(WorkerEntrypoint):
 
 - Review the [JavaScript API](/queues/configuration/javascript-apis/) documentation for Queues.
 - Learn more about [How Queues Works](/queues/reference/how-queues-works/).
-- Understand the [metrics available](/queues/observability/metrics/) for your queues, including backlog and delayed message counts.
\ No newline at end of file
+- Understand the [metrics available](/queues/observability/metrics/) for your queues, including backlog and delayed message counts.