Fixing typo.

Author: Oxyjun

src/content/docs/d1/build-with-d1/use-indexes.mdx

@@ -98,7 +98,7 @@ Review the `USING INDEX <INDEX_NAME>` output from the query planner, confirming
 
 This is also a fairly common use-case for an index. Finding a user based on their email address is often a very common query type for login (authentication) systems.
 
-Using an index can reduce the number of rows read by a query. You use the `meta` object to estimate your usage. Refer to ["Can I use an index to reduce the number of rows read by a query?"](/d1/platform/pricing/#can-i-use-an-index-to-reduce-the-number-of-rows-read-by-a-query) and ["How can I estimate my (eventual) bill?"](/d1/platform/pricing/#how-can-i-estimate-my-eventual-bill).
+Using an index can reduce the number of rows read by a query. Use the `meta` object to estimate your usage. Refer to ["Can I use an index to reduce the number of rows read by a query?"](/d1/platform/pricing/#can-i-use-an-index-to-reduce-the-number-of-rows-read-by-a-query) and ["How can I estimate my (eventual) bill?"](/d1/platform/pricing/#how-can-i-estimate-my-eventual-bill).
 
 ## Multi-column indexes