Clarifying getAlarm behaviour if called while alarm is running.

Author: Oxyjun

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

@@ -35,6 +35,8 @@ Alarms can be used to build distributed primitives, like queues or batching of w
 
   - If there is an alarm set, then return the currently set alarm time as the number of milliseconds elapsed since the UNIX epoch. Otherwise, return `null`.
 
+  - If `getAlarm` is called while an [`alarm`](/durable-objects/api/alarms/#alarm) is already running, it returns `null` unless `setAlarm` has been called since the alarm handler started running.
+
 ### `setAlarm`
 
 - <code>{" "}setAlarm(scheduledTimeMs <Type text="number" />)</code>
@@ -62,6 +64,7 @@ Alarms can be used to build distributed primitives, like queues or batching of w
     - `retryCount` <Type text="number"/>: The number of times this alarm event has been retried.
     - `isRetry` <Type text="boolean"/>: A boolean value to indicate if the alarm has been retried. This value is `true` if this alarm event is a retry.
 
+
   - 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.
 
   - This method can be `async`.