Update 2025-05-30-d1-rest-api-latency.mdx

Author: vy-ton

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

@@ -7,9 +7,9 @@ products:
 date: 2025-05-29T00:00:00Z
 ---
 
-Users using Cloudflare's [REST API](/api/resources/d1/subresources/database/methods/query/) 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 recieved the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core data centers, which added network round trips to select, central locations. 
+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 recieved the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core centralized centers, which added network round trips. 
 
-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, due to authentication at the network data center recieving the request, but still require access to Cloduflare's core data centers.
+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 Cloduflare's core data centers for other control plane metadata.
 
 Performance improvements apply to only the REST API. Users can now expect similar performance querying their database via the REST API and via a [Worker](/d1/best-practices/query-d1/#query-d1-with-workers-binding-api).