KV -> Workers KV inside links.

Author: Oxyjun

src/content/apps/index.yaml

@@ -200,7 +200,7 @@ entries:
     name: Queues Web Crawler
     description: An example use-case for Queues, a web crawler built on Browser Rendering and Puppeteer. The crawler finds the number of links to Cloudflare.com on the site, and archives a screenshot to Workers KV.
     tags: []
-    products: [KV, Browser Rendering, Workers, Pages, Queues]
+    products: [Workers KV, Browser Rendering, Workers, Pages, Queues]
     languages: [TypeScript]
     cloudflare: true
     updated: 2023-06-15

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

@@ -8,7 +8,7 @@ sidebar:
 
 import { GlossaryTooltip } from "~/components"
 
-To delete a key-value pair, call the `delete()` method of the [KV binding](/kv/concepts/kv-bindings/) on any [KV namespace](/kv/concepts/kv-namespaces/) you have bound to your Worker code:
+To delete a key-value pair, call the `delete()` method of the [Workers KV binding](/kv/concepts/kv-bindings/) on any [Workers KV namespace](/kv/concepts/kv-namespaces/) you have bound to your Worker code:
 
 ```js
 env.NAMESPACE.delete(key);
@@ -43,7 +43,7 @@ The following method is provided to delete from Workers KV:
 
 ### `delete()` method
 
-To delete a key-value pair, call the `delete()` method of the [KV binding](/kv/concepts/kv-bindings/) on any Workers KV namespace you have bound to your Worker code:
+To delete a key-value pair, call the `delete()` method of the [Workers KV binding](/kv/concepts/kv-bindings/) on any Workers KV namespace you have bound to your Worker code:
 
 ```js
 env.NAMESPACE.delete(key);
@@ -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 [KV binding](/kv/concepts/kv-bindings/).
+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/).
 
 ## 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

@@ -5,7 +5,7 @@ sidebar:
   order: 4
 ---
 
-To get the value for a given key, call the `get()` method of the [KV binding](/kv/concepts/kv-bindings/) on any [KV namespace](/kv/concepts/kv-namespaces/) you have bound to your Worker code:
+To get the value for a given key, call the `get()` method of the [Workers KV binding](/kv/concepts/kv-bindings/) on any [Workers KV namespace](/kv/concepts/kv-namespaces/) you have bound to your Worker code:
 
 ```js
 env.NAMESPACE.get(key);

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

@@ -5,7 +5,7 @@ sidebar:
   order: 5
 ---
 
-To create a new key-value pair, or to update the value for a particular key, call the `put()` method of the [KV binding](/kv/concepts/kv-bindings/) on any [KV namespace](/kv/concepts/kv-namespaces/) you have bound to your Worker code:
+To create a new key-value pair, or to update the value for a particular key, call the `put()` method of the [Workers KV binding](/kv/concepts/kv-bindings/) on any [Workers KV namespace](/kv/concepts/kv-namespaces/) you have bound to your Worker code:
 
 ```js
 env.NAMESPACE.put(key, value);
@@ -88,7 +88,7 @@ Write more than one key-value pair at a time with Wrangler or [via the REST API]
 
 The bulk API can accept up to 10,000 KV 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 [KV binding](/kv/concepts/kv-bindings/).
+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/).
 
 ### Expiring keys
 

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

@@ -99,7 +99,7 @@ Create a new Worker to read and write to your Workers KV namespace.
 
 ## 2. Create a Workers KV namespace
 
-A [KV namespace](/kv/concepts/kv-namespaces/) is a key-value database replicated to Cloudflare’s global network.
+A [Workers KV namespace](/kv/concepts/kv-namespaces/) is a key-value database replicated to Cloudflare’s global network.
 
 <Tabs syncKey = 'CLIvsDash'> <TabItem label='CLI'>
 
@@ -179,7 +179,7 @@ To bind your Workers KV namespace to your Worker:
 
 :::note[Bindings]
 
-A binding is how your Worker interacts with external resources such as [KV namespaces](/kv/concepts/kv-namespaces/). A binding is a runtime variable that the Workers runtime provides to your code. You can declare a variable name in your `wrangler.toml` file that binds to these resources at runtime, and interact with them through this variable. Every binding's variable name and behavior is determined by you when deploying the Worker.
+A binding is how your Worker interacts with external resources such as [Workers KV namespaces](/kv/concepts/kv-namespaces/). A binding is a runtime variable that the Workers runtime provides to your code. You can declare a variable name in your `wrangler.toml` file that binds to these resources at runtime, and interact with them through this variable. Every binding's variable name and behavior is determined by you when deploying the Worker.
 
 Refer to [Environment](/kv/reference/environments/) for more information.
 
@@ -312,7 +312,7 @@ You can view key-value pairs directly from the dashboard.
 
 When using [`wrangler dev`](/workers/wrangler/commands/#dev) to develop locally, Wrangler defaults to using a local version of Workers KV to avoid interfering with any of your live production data in Workers KV. This means that reading keys that you have not written locally returns null.
 
-To have `wrangler dev` connect to your Workers KV namespace running on Cloudflare's global network, call `wrangler dev --remote` instead. This uses the `preview_id` of the Workers KV binding configuration in the `wrangler.toml` file. See the [KV binding docs](/kv/concepts/kv-bindings/#using-the-kv-binding-when-developing-locally) for more information.
+To have `wrangler dev` connect to your Workers KV namespace running on Cloudflare's global network, call `wrangler dev --remote` instead. This uses the `preview_id` of the Workers KV binding configuration in the `wrangler.toml` file. See the [Workers KV binding docs](/kv/concepts/kv-bindings/#using-the-kv-binding-when-developing-locally) for more information.
 
 :::
 
@@ -465,6 +465,6 @@ By finishing this tutorial, you have:
 
 If you have any feature requests or notice any bugs, share your feedback directly with the Cloudflare team by joining the [Cloudflare Developers community on Discord](https://discord.cloudflare.com).
 
-- Learn more about the [KV API](/kv/api/).
+- Learn more about the [Workers KV API](/kv/api/).
 - Understand how to use [Environments](/kv/reference/environments/) with Workers KV.
 - Read the Wrangler [`kv` command documentation](/kv/reference/kv-commands/).

src/content/docs/pages/framework-guides/deploy-a-remix-site.mdx

@@ -76,7 +76,7 @@ npm run deploy
 ## Create and add a binding to your Remix application
 
 To add a binding to your Remix application, refer to [Bindings](/pages/functions/bindings/).
-A [binding](/pages/functions/bindings/) allows your application to interact with Cloudflare developer products, such as [KV namespaces](/kv/concepts/how-kv-works/), [Durable Objects](/durable-objects/), [R2 storage buckets](/r2/), and [D1 databases](/d1/).
+A [binding](/pages/functions/bindings/) allows your application to interact with Cloudflare developer products, such as [Workers KV namespaces](/kv/concepts/how-kv-works/), [Durable Objects](/durable-objects/), [R2 storage buckets](/r2/), and [D1 databases](/d1/).
 
 ### Binding resources in local development
 

src/content/docs/pages/functions/wrangler-configuration.mdx

@@ -353,7 +353,7 @@ This will work for local development, but will fail to validate when you try to
 
 - `kv_namespaces` <Type text="object" /> <MetaInfo text="optional" />
 
-  - A list of Workers KV namespaces that your Function should be bound to. Refer to [KV namespaces](/pages/functions/bindings/#kv-namespaces).
+  - A list of Workers KV namespaces that your Function should be bound to. Refer to [Workers KV namespaces](/pages/functions/bindings/#kv-namespaces).
 
 - `queues.producers` <Type text="object" /> <MetaInfo text="optional" />
 
@@ -440,7 +440,7 @@ When using Wrangler in the default local development mode, files will be written
 :::
 
 - Configure Workers KV namespace bindings via your [`wrangler.toml` file](/workers/wrangler/configuration/#kv-namespaces) the same way they are configured with Cloudflare Workers.
-- Interact with your [KV namespace binding](/pages/functions/bindings/#kv-namespaces).
+- Interact with your [Workers KV namespace binding](/pages/functions/bindings/#kv-namespaces).
 
 ### Queues Producers
 

src/content/docs/r2/api/s3/presigned-urls.mdx

@@ -68,7 +68,7 @@ A valid alternative design to presigned URLs is to use a Worker with a [binding]
 :::note[Bindings]
 
 
-A binding is how your Worker interacts with external resources such as [KV Namespaces](/kv/concepts/kv-namespaces/), [Durable Objects](/durable-objects/), or [R2 Buckets](/r2/buckets/). A binding is a runtime variable that the Workers runtime provides to your code. You can declare a variable name in your `wrangler.toml` file that will be bound to these resources at runtime, and interact with them through this variable. Every binding's variable name and behavior is determined by you when deploying the Worker. Refer to [Environment Variables](/workers/configuration/environment-variables/) for more information.
+A binding is how your Worker interacts with external resources such as [Workers KV Namespaces](/kv/concepts/kv-namespaces/), [Durable Objects](/durable-objects/), or [R2 Buckets](/r2/buckets/). A binding is a runtime variable that the Workers runtime provides to your code. You can declare a variable name in your `wrangler.toml` file that will be bound to these resources at runtime, and interact with them through this variable. Every binding's variable name and behavior is determined by you when deploying the Worker. Refer to [Environment Variables](/workers/configuration/environment-variables/) for more information.
 
 A binding is defined in the `wrangler.toml` file of your Worker project's directory.
 

src/content/docs/r2/api/workers/workers-api-reference.mdx

@@ -18,7 +18,7 @@ R2 organizes the data you store, called objects, into containers, called buckets
 :::note[Bindings]
 
 
-A binding is how your Worker interacts with external resources such as [KV Namespaces](/kv/concepts/kv-namespaces/), [Durable Objects](/durable-objects/), or [R2 Buckets](/r2/buckets/). A binding is a runtime variable that the Workers runtime provides to your code. You can declare a variable name in your `wrangler.toml` file that will be bound to these resources at runtime, and interact with them through this variable. Every binding's variable name and behavior is determined by you when deploying the Worker. Refer to [Environment Variables](/workers/configuration/environment-variables/) for more information.
+A binding is how your Worker interacts with external resources such as [Workers KV Namespaces](/kv/concepts/kv-namespaces/), [Durable Objects](/durable-objects/), or [R2 Buckets](/r2/buckets/). A binding is a runtime variable that the Workers runtime provides to your code. You can declare a variable name in your `wrangler.toml` file that will be bound to these resources at runtime, and interact with them through this variable. Every binding's variable name and behavior is determined by you when deploying the Worker. Refer to [Environment Variables](/workers/configuration/environment-variables/) for more information.
 
 A binding is defined in the `wrangler.toml` file of your Worker project's directory.
 
@@ -87,9 +87,9 @@ export default {
 * `list` <Type text="(options?: R2ListOptions): Promise<R2Objects>" />
 
   * Returns an <code>R2Objects</code> containing a list of <code>R2Object</code> contained within the bucket.
-  * The returned list of objects is ordered lexicographically. 
+  * The returned list of objects is ordered lexicographically.
   * Returns up to 1000 entries, but may return less in order to minimize memory pressure within the Worker.
-  * To explicitly set the number of objects to list, provide an [R2ListOptions](/r2/api/workers/workers-api-reference/#r2listoptions) object with the `limit` property set. 
+  * To explicitly set the number of objects to list, provide an [R2ListOptions](/r2/api/workers/workers-api-reference/#r2listoptions) object with the `limit` property set.
 
 * `createMultipartUpload` <Type text="(key: string, options?: R2MultipartOptions): Promise<R2MultipartUpload>" />
 
@@ -125,7 +125,7 @@ export default {
 
 :::note
 
-Cloudflare recommends using the `httpEtag` field when returning an etag in a response header. This ensures the etag is quoted and conforms to [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110#section-8.8.3). 
+Cloudflare recommends using the `httpEtag` field when returning an etag in a response header. This ensures the etag is quoted and conforms to [RFC 9110](https://www.rfc-editor.org/rfc/rfc9110#section-8.8.3).
 :::
 
 * The etag associated with the object upload.

src/content/docs/r2/api/workers/workers-api-usage.mdx

@@ -56,7 +56,7 @@ You will need to bind your bucket to a Worker.
 
 :::note[Bindings]
 
-A binding is how your Worker interacts with external resources such as [KV Namespaces](/kv/concepts/kv-namespaces/), [Durable Objects](/durable-objects/), or [R2 Buckets](/r2/buckets/). A binding is a runtime variable that the Workers runtime provides to your code. You can declare a variable name in your `wrangler.toml` file that will be bound to these resources at runtime, and interact with them through this variable. Every binding's variable name and behavior is determined by you when deploying the Worker. Refer to the [Environment Variables](/workers/configuration/environment-variables/) documentation for more information.
+A binding is how your Worker interacts with external resources such as [Workers KV Namespaces](/kv/concepts/kv-namespaces/), [Durable Objects](/durable-objects/), or [R2 Buckets](/r2/buckets/). A binding is a runtime variable that the Workers runtime provides to your code. You can declare a variable name in your `wrangler.toml` file that will be bound to these resources at runtime, and interact with them through this variable. Every binding's variable name and behavior is determined by you when deploying the Worker. Refer to the [Environment Variables](/workers/configuration/environment-variables/) documentation for more information.
 
 A binding is defined in the `wrangler.toml` file of your Worker project's directory.