Update src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx

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

Author: vy-ton

src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx

@@ -9,6 +9,6 @@ date: 2025-05-29T00:00:00Z
 
 Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that received the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core, centralized data centers, which added network round trips and latency. 
 
-Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. REST API requests and databases outstide the United States see a bigger benefit since Cloudflare's primary core data centers reside in the United States.
+Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. REST API requests and databases outside the United States see a bigger benefit since Cloudflare's primary core data centers reside in the United States.
 
 D1 query endpoints like `/query` and `/raw` have the most noticeable improvements since they no longer access Cloudflare's core data centers. D1 control plane endpoints such as those to create and delete databases see smaller improvements, since they still require access to Cloudflare's core data centers for other control plane metadata.