Explicitly spelling "key-value" where relevant.

Author: Oxyjun

src/content/docs/browser-rendering/get-started/screenshots.mdx

@@ -45,7 +45,7 @@ npm install @cloudflare/puppeteer --save-dev
 
 Browser Rendering can be used with other developer products. You might need a [relational database](/d1/), an [R2 bucket](/r2/) to archive your crawled pages and assets, a [Durable Object](/durable-objects/) to keep your browser instance alive and share it with multiple requests, or [Queues](/queues/) to handle your jobs asynchronous.
 
-For the purpose of this guide, you are going to use a [Workers KV store](/kv/concepts/kv-namespaces/) to cache your screenshots.
+For the purpose of this guide, you are going to use [Workers KV](/kv/concepts/kv-namespaces/) to cache your screenshots.
 
 Create two namespaces, one for production, and one for development.
 

src/content/docs/data-localization/compatibility.mdx

@@ -139,6 +139,6 @@ The table below provides a summary of the Data Localization Suite product's beha
 [^31]: DLP is part of Gateway HTTP, however, [DLP datasets](/cloudflare-one/policies/data-loss-prevention/datasets/#use-dlp-datasets) are not available outside US region when using Customer Metadata Boundary.
 [^32]: Dashboard Analytics are empty when using CMB outside the US region. Use Logpush instead.
 [^33]: [Outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/) will carry Earth region proxy IPs, thus making regional service dysfunctional when non-Cloudflare nameservers respond to the DNS queries.
-[^34]: Jurisdictional Restrictions (storage) for Workers KV pairs is not supported today.
+[^34]: Jurisdictional Restrictions (storage) for Workers KV is not supported today.
 [^35]: Logs / Analytics not available outside US region when using Customer Metadata Boundary. Jurisdictional Restrictions (storage) options are not supported today.
 [^36]: Only when using a [Custom Domain](/images/manage-images/serve-images/serve-from-custom-domains/) set to a region.

src/content/docs/dns/manage-dns-records/how-to/batch-record-changes.mdx

@@ -10,7 +10,7 @@ import { GlossaryTooltip, Example, Render } from "~/components";
 Cloudflare allows you to apply several changes to your zone records in just one action. You can [use the dashboard](#use-the-dashboard) to delete DNS records or update their <GlossaryTooltip term="proxy status">proxy status</GlossaryTooltip> in bulk, or [use the API](#use-the-api) to perform further batched operations.
 
 :::caution[Propagation through the Cloudflare network]
-Although Cloudflare will execute the batched operations in a single [database transaction](https://en.wikipedia.org/wiki/Database_transaction), Cloudflare's distributed KV store must treat each record change as a single key-value pair. This means that the propagation of changes is not atomic. Refer to our [blog post](https://blog.cloudflare.com/batched-dns-changes/) for details.
+Although Cloudflare will execute the batched operations in a single [database transaction](https://en.wikipedia.org/wiki/Database_transaction), Cloudflare's distributed key-value store must treat each record change as a single key-value pair. This means that the propagation of changes is not atomic. Refer to our [blog post](https://blog.cloudflare.com/batched-dns-changes/) for details.
 :::
 
 ## Availability and limits
@@ -91,7 +91,7 @@ Within each of these four lists, each individual action is executed following th
 ### Aspects to consider
 
 :::caution[Propagation through the Cloudflare network]
-Although Cloudflare will execute the batched operations in a single [database transaction](https://en.wikipedia.org/wiki/Database_transaction), Cloudflare's distributed KV store must treat each record change as a single key-value pair. This means that the propagation of changes is not atomic. Refer to our [blog post](https://blog.cloudflare.com/batched-dns-changes/) for details.
+Although Cloudflare will execute the batched operations in a single [database transaction](https://en.wikipedia.org/wiki/Database_transaction), Cloudflare's distributed key-value store must treat each record change as a single key-value pair. This means that the propagation of changes is not atomic. Refer to our [blog post](https://blog.cloudflare.com/batched-dns-changes/) for details.
 :::
 
 For each operation that you list in the `/batch` request body, consider the required information and how unspecified fields will behave:

src/content/docs/durable-objects/api/sql-storage.mdx

@@ -37,7 +37,7 @@ export class MyDurableObject extends DurableObject {
 SQL API methods accessed with `ctx.storage.sql` are only allowed on [Durable Object classes with SQLite storage backend](/durable-objects/reference/durable-objects-migrations/#enable-sqlite-storage-backend-on-new-durable-object-class-migration) and will return an error if called on Durable Object classes with a key-value storage backend.
 :::
 
-Specifically for Durable Object classes with SQLite storage backend, KV operations which were previously asynchronous (for example, [`get`](/durable-objects/api/storage-api/#get), [`put`](/durable-objects/api/storage-api/#put), [`delete`](/durable-objects/api/storage-api/#delete), [`deleteAll`](/durable-objects/api/storage-api/#deleteall), [`list`](/durable-objects/api/storage-api/#list)) are synchronous, even though they return promises. These methods will have completed their operations before they return the promise.
+Specifically for Durable Object classes with SQLite storage backend, key-value operations which were previously asynchronous (for example, [`get`](/durable-objects/api/storage-api/#get), [`put`](/durable-objects/api/storage-api/#put), [`delete`](/durable-objects/api/storage-api/#delete), [`deleteAll`](/durable-objects/api/storage-api/#deleteall), [`list`](/durable-objects/api/storage-api/#list)) are synchronous, even though they return promises. These methods will have completed their operations before they return the promise.
 
 ## Methods
 

src/content/docs/kv/api/delete-key-value-pairs.mdx

@@ -70,7 +70,7 @@ Calling the `delete()` method will remove the key and value from your Workers KV
 
 Delete more than one key-value pair at a time with Wrangler or [via the REST API](/api/operations/workers-kv-namespace-delete-multiple-key-value-pairs).
 
-The bulk REST API can accept up to 10,000 KV pairs at once. Bulk writes are not supported using the [Workers KV binding](/kv/concepts/kv-bindings/).
+The bulk REST API can accept up to 10,000 key-value pairs at once. Bulk writes are not supported using the [Workers KV binding](/kv/concepts/kv-bindings/).
 
 ## Other methods to access Workers KV
 You can also [delete key-value pairs from the command line with Wrangler](/kv/reference/kv-commands/#delete) or [with the REST API](/api/operations/workers-kv-namespace-delete-key-value-pair).

src/content/docs/kv/api/read-key-value-pairs.mdx

@@ -56,7 +56,7 @@ The `get()` method returns a promise you can `await` on to get the value. If the
 #### Parameters
 
 - `key`: `string`
-  - The key of the KV pair.
+  - The key of the key-value pair.
 - `type`: `"text" | "json" | "arrayBuffer" | "stream"`
   - Optional. The type of the value to be returned. `text` is the default.
 - `options`: `{
@@ -68,7 +68,7 @@ The `get()` method returns a promise you can `await` on to get the value. If the
 #### Response
 
 - `response`: `Promise<string | Object | ArrayBuffer | ReadableStream | null>`
-  - The value for the requested KV pair. The response type will depend on the `type` parameter provided for the `get()` command as follows:
+  - The value for the requested key-value pair. The response type will depend on the `type` parameter provided for the `get()` command as follows:
     - `text`: A `string` (default).
     - `json`: An object decoded from a JSON string.
     - `arrayBuffer`: An [`ArrayBuffer`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer) instance.
@@ -91,7 +91,7 @@ Metadata is a serializable value you append to each KV entry.
 #### Parameters
 
 - `key`: `string`
-  - The key of the KV pair.
+  - The key of the key-value pair.
 - `type`: `"text" | "json" | "arrayBuffer" | "stream"`
   - Optional. The type of the value to be returned. `text` is the default.
 - `options`: `{
@@ -107,7 +107,7 @@ value: string | Object | ArrayBuffer | ReadableStream | null,
 metadata: string | null
 }>`
 
-  - An object containing the value and the metadata for the requested KV pair. The type of the value attribute will depend on the `type` parameter provided for the `getWithMetadata()` command as follows:
+  - An object containing the value and the metadata for the requested key-value pair. The type of the value attribute will depend on the `type` parameter provided for the `getWithMetadata()` command as follows:
     - `text`: A `string` (default).
     - `json`: An object decoded from a JSON string.
     - `arrayBuffer`: An [`ArrayBuffer`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer) instance.

src/content/docs/kv/api/write-key-value-pairs.mdx

@@ -86,9 +86,9 @@ Refer to [How Workers KV works](/kv/concepts/how-kv-works/) for more information
 
 Write more than one key-value pair at a time with Wrangler or [via the REST API](/api/operations/workers-kv-namespace-write-multiple-key-value-pairs).
 
-The bulk API can accept up to 10,000 KV pairs at once.
+The bulk API can accept up to 10,000 key-value pairs at once.
 
-A `key` and a `value` are required for each KV pair. The entire request size must be less than 100 megabytes. Bulk writes are not supported using the [Workers KV binding](/kv/concepts/kv-bindings/).
+A `key` and a `value` are required for each key-value pair. The entire request size must be less than 100 megabytes. Bulk writes are not supported using the [Workers KV binding](/kv/concepts/kv-bindings/).
 
 ### Expiring keys
 

src/content/docs/kv/concepts/how-kv-works.mdx

@@ -44,7 +44,7 @@ Changes are usually immediately visible in the Cloudflare global network locatio
 
 Negative lookups indicating that the key does not exist are also cached, so the same delay exists noticing a value is created as when a value is changed.
 
-Workers KV does not perform like an in-memory datastore, such as [Redis](https://redis.io). Accessing KV values, even when locally cached, has significantly more latency than reading a value from memory within a Worker script.
+Workers KV does not perform like an in-memory datastore, such as [Redis](https://redis.io). Accessing key-value values, even when locally cached, has significantly more latency than reading a value from memory within a Worker script.
 
 ## Consistency
 
@@ -54,11 +54,10 @@ Visibility of changes takes longer in locations which have recently read a previ
 
 :::note
 
-Workers KV is not ideal for applications where you need support for atomic operations or where values must be read and written in a single transaction.
-If you need stronger consistency guarantees, consider using [Durable Objects](/durable-objects/).
+Workers KV is not ideal for applications where you need support for atomic operations or where values must be read and written in a single transaction. If you need stronger consistency guarantees, consider using [Durable Objects](/durable-objects/).
 :::
 
-An approach to achieve write-after-write consistency is to send all of your writes for a given KV key through a corresponding instance of a Durable Object, and then read that value from KV in other Workers. This is useful if you need more control over writes, but are satisfied with KV's read characteristics described above.
+An approach to achieve write-after-write consistency is to send all of your writes for a given key-value key through a corresponding instance of a Durable Object, and then read that value from Workers KV in other Workers. This is useful if you need more control over writes, but are satisfied with Workers KV's read characteristics described above.
 
 ## Security
 

src/content/docs/kv/examples/workers-kv-to-serve-assets.mdx

@@ -55,9 +55,9 @@ npm install --save-dev @types/accept-language-parser
 
 ## 2. Create a new Workers KV namespace
 
-Next, we will create a KV store. This can be done through the Cloudflare dashboard or the Wrangler CLI. For this example, we will use the Wrangler CLI.
+Next, we will create a key-value store. This can be done through the Cloudflare dashboard or the Wrangler CLI. For this example, we will use the Wrangler CLI.
 
-To create a KV store via Wrangler:
+To create a key-value store via Wrangler:
 
 1. Open your terminal and run the following command:
 
@@ -128,20 +128,20 @@ We now have one Workers KV binding that will use the production Workers KV names
 
 To store static assets in Workers KV, you can use the Wrangler CLI, the Workers KV binding from a Worker application, or the Workers KV REST API. We will demonstrate how to use the Wrangler CLI.
 
-For this scenario, we'll be storing a sample HTML file within our KV store. Create a new file `index.html` in the root of project with the following content:
+For this scenario, we'll be storing a sample HTML file within our key-value store. Create a new file `index.html` in the root of project with the following content:
 
 ```html title="index.html"
 Hello World!
 ```
 
-We can then use the following Wrangler commands to create a KV pair for this file within our production and preview namespaces:
+We can then use the following Wrangler commands to create a key-value pair for this file within our production and preview namespaces:
 
 ```sh
 npx wrangler kv key put index.html --path index.html --binding assets --preview false
 npx wrangler kv key put index.html --path index.html --binding assets --preview
 ```
 
-This will create a KV pair with the filename as key and the file content as value, within the our production and preview namespaces specified by your binding in your `wrangler.toml` file.
+This will create a key-value pair with the filename as key and the file content as value, within the our production and preview namespaces specified by your binding in your `wrangler.toml` file.
 
 ## 4. Serve static assets from Workers KV from your Worker application
 
@@ -180,7 +180,7 @@ export default {
 			mimeType += "; charset=utf-8";
 		}
 
-		//get the value from the KV store and return it if found
+		//get the value from the key-value store and return it if found
 		const value = await env.assets.get(key, 'arrayBuffer')
 		if(!value){
 			return new Response("Not found", {
@@ -197,7 +197,7 @@ export default {
 } satisfies ExportedHandler<Env>;
 ```
 
-This code will use the path within the URL and find the file associated to the path within the KV store. It also sets the proper MIME type in the response to indicate to the browser how to handle the response. To retrieve the value from the KV store, this code uses `arrayBuffer` to properly handle binary data such as images, documents, and video/audio files.
+This code will use the path within the URL and find the file associated to the path within the key-value store. It also sets the proper MIME type in the response to indicate to the browser how to handle the response. To retrieve the value from the key-value store, this code uses `arrayBuffer` to properly handle binary data such as images, documents, and video/audio files.
 
 To start the Worker, run the following within a terminal:
 
@@ -218,7 +218,7 @@ Your worker has access to the following bindings:
 [wrangler:inf] Ready on http://localhost:<PORT>
 ```
 
-Access the URL provided by the Wrangler command as such `http://localhost:<PORT>/index.html`. You will be able to see the returned HTML file containing the file contents of our `index.html` file that was added to our KV store. Try it out with an image or a document and you will see that this Worker is also properly serving those assets from Workers KV.
+Access the URL provided by the Wrangler command as such `http://localhost:<PORT>/index.html`. You will be able to see the returned HTML file containing the file contents of our `index.html` file that was added to our key-value store. Try it out with an image or a document and you will see that this Worker is also properly serving those assets from Workers KV.
 
 ## 5. Create an endpoint to generate dynamic responses from your key-value pairs
 
@@ -344,7 +344,7 @@ export default {
 			mimeType += "; charset=utf-8";
 		}
 
-		//get the value from the KV store and return it if found
+		//get the value from the key-value store and return it if found
 		const value = await env.assets.get(key, 'arrayBuffer')
 		if(!value){
 			return new Response("Not found", {
@@ -361,7 +361,7 @@ export default {
 } satisfies ExportedHandler<Env>;
 ```
 
-This new code provides a specific endpoint, `/hello-world`, which will provide translated responses. When this URL is accessed, our Worker code will first retrieve the language that is requested by the client in the `Accept-Language` request header and the translations from our KV store for the `hello-world.json` key. It then gets the translated message and returns the generated HTML.
+This new code provides a specific endpoint, `/hello-world`, which will provide translated responses. When this URL is accessed, our Worker code will first retrieve the language that is requested by the client in the `Accept-Language` request header and the translations from our key-value store for the `hello-world.json` key. It then gets the translated message and returns the generated HTML.
 
 ```sh
 npx wrangler dev --remote
@@ -379,7 +379,7 @@ npx wrangler deploy
 
 Wrangler will automatically set your Workers KV binding to use the production Workers KV namespace set in our `wrangler.toml` file with the Workers KV namespace id. Throughout this example, we uploaded our assets to both the preview and the production Workers KV namespaces.
 
-We can now verify that our project is properly working by accessing our Workers default hostname and accessing `<WORKER-SUBDOMAIN>.<DEFAULT-ACCOUNT-HOSTNAME>.dev/index.html` or `<WORKER-SUBDOMAIN>.<DEFAULT-ACCOUNT-HOSTNAME>.dev/hello-world` to see our deployed Worker in action, generating responses from the values in our KV store.
+We can now verify that our project is properly working by accessing our Workers default hostname and accessing `<WORKER-SUBDOMAIN>.<DEFAULT-ACCOUNT-HOSTNAME>.dev/index.html` or `<WORKER-SUBDOMAIN>.<DEFAULT-ACCOUNT-HOSTNAME>.dev/hello-world` to see our deployed Worker in action, generating responses from the values in our key-value store.
 
 ## Related resources
 

src/content/docs/kv/get-started.mdx

@@ -107,7 +107,7 @@ A [Workers KV namespace](/kv/concepts/kv-namespaces/) is a key-value database re
 
 :::note
 
-KV operations are scoped to your account.
+Key-value operations are scoped to your account.
 :::
 
 To create a Workers KV namespace via Wrangler: