Adding image to changelog, minor update.

Author: Oxyjun

src/assets/images/changelog/d1/d1-auto-retry-success-ratio.png

@@ -15,7 +15,7 @@ The retry success ratio among read-only retryable errors varies from 5% all the
 
 The retry success ratio among all retryable errors is lower, indicating that there are write-queries that could be retried. Therefore, we recommend D1 users to continue applying [retries in their own code](/d1/best-practices/retry-queries/) for queries that are not read-only but are idempotent according to the business logic of the application.
 
-[D1 automatically query retries success ratio]
+![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.
 

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

@@ -8,9 +8,11 @@ sidebar:
 
 import { GitHubCode } from "~/components";
 
-D1 automatically retries read-only queries up to 2 more times when it encounters a retryable error.
+It can be useful to retry queries from your application when you encounter an [error](/d1/observability/debug-d1/#error-list). From the list of `D1_ERROR`s, refer to the Recommended action column to determine if a query should be retried.
 
-But it can be useful to retry queries from your application when you encounter an [error](/d1/observability/debug-d1/#error-list).
+:::note
+D1 automatically retries read-only queries up to 2 more times when it encounters a retryable error.
+:::
 
 ## Example of retrying queries