Apply suggestions from code review

Co-authored-by: marciocloudflare <[email protected]>

Author: Oxyjun

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

@@ -39,7 +39,7 @@ Limits for individual queries (listed above) apply to each individual statement
 <Details header = "Footnotes" open={true}>
 1: The maximum storage per account can be increased by request on Workers Paid and Enterprise plans. See the guidance on limit increases on this page to request an increase.
 
-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.
+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: Requests to Cloudflare API must resolve in 30 seconds. Therefore, this duration limit also applies to the entire batch call.
 

src/content/docs/durable-objects/platform/limits.mdx

@@ -26,7 +26,7 @@ Durable Objects are a special kind of Worker, so [Workers Limits](/workers/platf
 
 [^1]: Identical to the Workers [script limit](/workers/platform/limits/).
 [^2]: Durable Objects both bills and measures storage based on a gigabyte <br/> (1 GB = 1,000,000,000 bytes) and not a gibibyte (GiB). <br/>
-[^3]: Accounts on the Workers Free plan are limited to 5GB total Durable Objects storage.
+[^3]: Accounts on the Workers Free plan are limited to 5 GB total Durable Objects storage.
 [^4]: Each incoming HTTP request or WebSocket *message* resets the remaining available CPU time to 30 seconds. This allows the Durable Object to consume up to 30 seconds of compute after each incoming network request, with each new network request resetting the timer. If you consume more than 30 seconds of compute between incoming network requests, there is a heightened chance that the individual Durable Object is evicted and reset. CPU time per request invocation [can be increased](/durable-objects/platform/limits/#increasing-durable-object-cpu-limits).
 
 <Details header="Footnotes" open={true}>