Using the caution aside component for 5 GiB limit for D1.

Adding the import limit in the limits table.

src/content/docs/d1/platform/limits.mdx

@@ -25,7 +25,7 @@ import { Render } from "~/components"
 | Maximum characters (bytes) in a `LIKE` or `GLOB` pattern                                                            | 50 bytes                                          |
 | Maximum bindings per Workers script                                                                                 | Approximately 5,000 [^2]                          |
 | Maximum SQL query duration                                                                                          | 30 seconds                                        |
-| Maximum file import (`d1 execute`) size                                                                             | 5 GiB [^3]                                        |
+| Maximum file import (`d1 execute`) size                                                                             | 5 GiB [^3]                              |
 
 :::note
 
@@ -41,6 +41,8 @@ Refer to the [Choose a data or storage product](/workers/platform/storage-option
 
 [^2]: A single Worker script can have up to 1 MB of script metadata. A binding is defined as a binding to a resource, such as a D1 database, KV namespace, environmental variable or secret. Each resource binding is approximately 150-bytes, however environmental variables and secrets are controlled by the size of the value you provide. Excluding environmental variables, you can bind up to \~5,000 D1 databases to a single Worker script.
 
-[^3] The imported file is uploaded to R2. See [R2 upload limit](/r2/platform/limits).
+[^3]: The imported file is uploaded to R2. See [R2 upload limit](/r2/platform/limits).
+
+<sup>3</sup> The imported file is uploaded to R2. See [R2 upload limit](/r2/platform/limits).
 
 <Render file="limits_increase" product="workers" />