Cover the cancellation request in the repeated-interrupt note

A second interrupt or task cancellation also escapes while the
cancellation request is in progress, not only during the follow-up wait.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: laughingman7743

docs/aio.md

@@ -139,7 +139,7 @@ requests cancellation of the query, waits until it reaches a terminal state, and
 Cancellation is a best-effort request, so the query can still end as `SUCCEEDED` or `FAILED`.
 The `query_id` property keeps the ID of the cancelled query.
 If the cancellation request fails, `asyncio.CancelledError` is raised with the error as its cause.
-Cancelling the task again during that wait raises `asyncio.CancelledError` without waiting for the terminal state.
+Cancelling the task again during the cancellation request or that wait raises `asyncio.CancelledError` immediately, and the query can keep running.
 With `kill_on_interrupt=False`, `asyncio.CancelledError` is raised immediately and the query keeps running.
 
 A timeout from `asyncio.wait_for()` that expires while `execute()` waits for the query therefore cancels the query

docs/usage.md

@@ -508,7 +508,7 @@ requests cancellation, waits until the query reaches a terminal state, and then
 Cancellation is a best-effort request, so the query can still end as `SUCCEEDED` or `FAILED`.
 The `query_id` property keeps the ID of the interrupted query.
 If the cancellation request fails, the `KeyboardInterrupt` propagates with the error as its cause.
-A second `KeyboardInterrupt` during that wait propagates without waiting for the terminal state.
+A second `KeyboardInterrupt` during the cancellation request or that wait propagates immediately, and the query can keep running.
 With `kill_on_interrupt=False`, the `KeyboardInterrupt` propagates immediately and the query keeps running.
 
 ```python