Skip to content

Commit a8cc386

Browse files
committed
"Two seconds" -> "2 seconds", "six seconds" -> "6 seconds"
1 parent 9503ffe commit a8cc386

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/content/docs/durable-objects/api/alarms.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Notably:
2121

2222
- Each Durable Object instance is able to schedule a single alarm at a time by calling `setAlarm()`.
2323
- Alarms have guaranteed at-least-once execution and are retried automatically when the `alarm()` handler throws.
24-
- Retries are performed using exponential backoff starting at a two second delay from the first failure with up to six retries allowed.
24+
- Retries are performed using exponential backoff starting at a 2 second delay from the first failure with up to 6 retries allowed.
2525

2626
:::note[How are alarms different from Cron Triggers?]
2727

@@ -63,7 +63,7 @@ Alarms can be used to build distributed primitives, like queues or batching of w
6363

6464
- Called by the system when a scheduled alarm time is reached.
6565

66-
- The `alarm()` handler has guaranteed at-least-once execution and will be retried upon failure using exponential backoff, starting at two second delays for up to six retries. Retries will be performed if the method fails with an uncaught exception.
66+
- The `alarm()` handler has guaranteed at-least-once execution and will be retried upon failure using exponential backoff, starting at 2 second delays for up to 6 retries. Retries will be performed if the method fails with an uncaught exception.
6767

6868
- This method can be `async`.
6969

0 commit comments

Comments
 (0)