Apply suggestions from code review

Co-authored-by: Lambros Petrou <[email protected]>

Author: Oxyjun

src/content/changelog/d1/2025-09-11-d1-automatic-read-retries.mdx

@@ -17,6 +17,6 @@ The retry success ratio among all retryable errors is lower, indicating that the
 
 ![D1 automatically query retries success ratio](~/assets/images/changelog/d1/d1-auto-retry-success-ratio.png)
 
-D1 ensures that any retry attempt does not cause database writes, making the automatic retries safe from side-effects, even if a query slips through the read-only detection. D1 achieves this by checking for modifications after every query execution, and if any write occurred due to a retry attempt, the query is rolled back.
+D1 ensures that any retry attempt does not cause database writes, making the automatic retries safe from side-effects, even if a query causing changes slips through the read-only detection. D1 achieves this by checking for modifications after every query execution, and if any write occurred due to a retry attempt, the query is rolled back.
 
 The read-only query detection heuristics are simple for now, and there is room for improvement to capture more cases of queries that can be retried, so this is just the beginning.

src/content/docs/d1/best-practices/retry-queries.mdx

@@ -18,7 +18,18 @@ D1 automatically retries read-only queries up to 2 more times when it encounters
 
 Consider the following example, taken from the [D1 read replication starter template](https://github.com/cloudflare/templates/blob/main/d1-starter-sessions-api-template/src/index.ts#L108).
 
+You should make sure your retries apply an exponential backoff with jitter strategy for more successful retries.
+You can use libraries abstracting that already like [`@cloudflare/actors`](https://github.com/cloudflare/actors), or [copy the retry logic](https://github.com/cloudflare/actors/blob/9ba112503132ddf6b5cef37ff145e7a2dd5ffbfc/packages/core/src/retries.ts#L18) in your own code directly.
+
 ```ts
+import { tryWhile } from "@cloudflare/actors";
+
+function queryD1Example(d1: D1Database, sql: string) {
+  const result = await tryWhile(async () => {
+    return await d1.prepare(sql).run();
+  }, shouldRetry);
+}
+
 function shouldRetry(err: unknown, nextAttempt: number) {
   const errMsg = String(err);
   const isRetryableError =

src/content/docs/d1/observability/debug-d1.mdx

@@ -83,7 +83,7 @@ Before retrying any failed operation:
 
 D1 detects read-only queries and automatically attempts up to 2 retries to execute those queries in the event of failures with retryable errors.
 
-D1 ensures that any retry attempt does not cause database writes, making the automatic retries safe from side-effects, even if a query slips through the read-only detection. D1 achieves this by checking for modifications after every query execution, and if any write occurred due to a retry attempt, the query is rolled back.
+D1 ensures that any retry attempt does not cause database writes, making the automatic retries safe from side-effects, even if a query causing modifications slips through the read-only detection. D1 achieves this by checking for modifications after every query execution, and if any write occurred due to a retry attempt, the query is rolled back.
 
 :::note
 Only read-only queries (queries containing only the following SQLite keywords: `SELECT`, `EXPLAIN`, `WITH`) are retried. Queries containing any [SQLite keyword](https://sqlite.org/lang_keywords.html) that leads to database writes are not retried.