KV -> Workers KV, only when referring to the product.

Author: Oxyjun

src/content/apps/index.yaml

@@ -70,9 +70,9 @@ entries:
     updated: 2024-06-17
   - link: https://github.com/craigsdennis/shorty-dot-dev
     name: shrty.dev
-    description: A URL shortener that makes use of KV and Workers Analytics Engine. The admin interface uses Function Calling. Go Shorty!
+    description: A URL shortener that makes use of Workers KV and Workers Analytics Engine. The admin interface uses Function Calling. Go Shorty!
     tags: [AI, Hono]
-    products: [Workers AI, KV, Workers]
+    products: [Workers AI, Workers KV, Workers]
     languages: [TypeScript]
     cloudflare: true
     updated: 2024-07-02
@@ -303,7 +303,7 @@ entries:
     updated: 2024-08-12
   - link: https://github.com/atinux/atinotes
     name: Atinotes
-    description: Store Markdown notes in Cloudflare KV with this full-stack application made with Nuxt & deployed on Cloudflare Pages.
+    description: Store Markdown notes in Cloudflare Workers KV with this full-stack application made with Nuxt & deployed on Cloudflare Pages.
     tags: [Nuxt]
     products: [Pages, Workers KV]
     languages: [TypeScript]

src/content/changelogs/kv.yaml

@@ -21,7 +21,7 @@ entries:
       The unsuccessful keys are an array of keys that were not written successfully to all storage backends and therefore should be retried.
 
   - publish_date: "2024-08-08"
-    title: New KV Analytics API
+    title: New Workers KV Analytics API
     description: |-
 
       Workers KV now has a new [metrics dashboard](/kv/observability/metrics-analytics/#view-metrics-in-the-dashboard) and [analytics API](/kv/observability/metrics-analytics/#query-via-the-graphql-api) that leverages the [GraphQL Analytics API](/analytics/graphql-api/) used by many other Cloudflare products. The new analytics API provides per-account and per-namespace metrics for both operations and storage, including latency metrics for read and write operations to Workers KV.

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

@@ -41,11 +41,11 @@ In your `browser-worker` directory, install Cloudflare’s [fork of Puppeteer](/
 npm install @cloudflare/puppeteer --save-dev
 ```
 
-## 3. Create a KV namespace
+## 3. Create a Workers KV namespace
 
 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 [KV store](/kv/concepts/kv-namespaces/) to cache your screenshots.
+For the purpose of this guide, you are going to use a [Workers KV store](/kv/concepts/kv-namespaces/) to cache your screenshots.
 
 Create two namespaces, one for production, and one for development.
 
@@ -60,7 +60,7 @@ Take note of the IDs for the next step.
 
 Configure your `browser-worker` project's [`wrangler.toml`](/workers/wrangler/configuration/) file by adding a browser [binding](/workers/runtime-apis/bindings/) and a [Node.js compatibility flag](/workers/configuration/compatibility-flags/#nodejs-compatibility-flag). Bindings allow your Workers to interact with resources on the Cloudflare developer platform. Your browser `binding` name is set by you, this guide uses the name `MYBROWSER`. Browser bindings allow for communication between a Worker and a headless browser which allows you to do actions such as taking a screenshot, generating a PDF and more.
 
-Update your `wrangler.toml` configuration file with the Browser Rendering API binding and the KV namespaces you created:
+Update your `wrangler.toml` configuration file with the Browser Rendering API binding and the Workers KV namespaces you created:
 
 ```toml
 name = "browser-worker"
@@ -157,9 +157,9 @@ export default {
 
 This Worker instantiates a browser using Puppeteer, opens a new page, navigates to what you put in the `"url"` parameter, takes a screenshot of the page, stores the screenshot in KV, closes the browser, and responds with the JPEG image of the screenshot.
 
-If your Worker is running in production, it will store the screenshot to the production KV namespace. If you are running `wrangler dev`, it will store the screenshot to the dev KV namespace.
+If your Worker is running in production, it will store the screenshot to the production Workers KV namespace. If you are running `wrangler dev`, it will store the screenshot to the dev Workers KV namespace.
 
-If the same `"url"` is requested again, it will use the cached version in KV instead, unless it expired.
+If the same `"url"` is requested again, it will use the cached version in Workers KV instead, unless it expired.
 
 ## 6. Test
 

src/content/docs/cloudflare-one/policies/access/external-evaluation.mdx

@@ -45,7 +45,7 @@ You can set up External Evaluation rules using any API service, but to get start
    npx wrangler kv namespace create "KV"
    ```
 
-   The command will output the binding name and KV namespace ID, for example
+   The command will output the binding name and Workers KV namespace ID, for example
 
    ```txt
      [[kv_namespaces]]

src/content/docs/d1/platform/limits.mdx

@@ -33,7 +33,7 @@ Limits for individual queries (listed above) apply to each individual statement
 
 [^1]: The maximum storage per account can be increased by request on Workers Paid and Enterprise plans. See the guidance on limit increases on this page to request an increase.
 
-[^2]: A single Worker script can have up to 1 MB of script metadata. A binding is defined as a binding to a resource, such as a D1 database, KV namespace, environmental variable or secret. Each resource binding is approximately 150-bytes, however environmental variables and secrets are controlled by the size of the value you provide. Excluding environmental variables, you can bind up to \~5,000 D1 databases to a single Worker script.
+[^2]: A single Worker script can have up to 1 MB of script metadata. A binding is defined as a binding to a resource, such as a D1 database, Workers KV namespace, environmental variable or secret. Each resource binding is approximately 150-bytes, however environmental variables and secrets are controlled by the size of the value you provide. Excluding environmental variables, you can bind up to \~5,000 D1 databases to a single Worker script.
 
 [^3]: Requests to Cloudflare API must resolve in 30 seconds. Therefore, this duration limit also applies to the entire batch call.
 

src/content/docs/d1/reference/community-projects.mdx

@@ -88,7 +88,7 @@ Instead of running the `wrangler d1 execute` command in your terminal every time
 
 ### L1
 
-`L1` is a package that brings some Cloudflare Worker ecosystem bindings into PHP and Laravel via the Cloudflare API. It provides interaction with D1 via PDO, KV and Queues, with more services to add in the future, making PHP integration with Cloudflare a real breeze.
+`L1` is a package that brings some Cloudflare Worker ecosystem bindings into PHP and Laravel via the Cloudflare API. It provides interaction with D1 via PDO, Workers KV and Queues, with more services to add in the future, making PHP integration with Cloudflare a real breeze.
 
 * [GitHub](https://github.com/renoki-co/l1)
 * [Packagist](https://packagist.org/packages/renoki-co/l1)

src/content/docs/d1/tutorials/build-a-comments-api/index.mdx

@@ -88,7 +88,7 @@ You will now create a D1 database. In Wrangler v2, there is support for the `wra
 npx wrangler d1 create d1-example
 ```
 
-Reference your created database in your Worker code by creating a [binding](/workers/runtime-apis/bindings/) inside of your `wrangler.toml` file, Wrangler's configuration file. Bindings allow us to access Cloudflare resources, like D1 databases, KV namespaces, and R2 buckets, using a variable name in code. In `wrangler.toml`, set up the binding `DB` and connect it to the `database_name` and `database_id`:
+Reference your created database in your Worker code by creating a [binding](/workers/runtime-apis/bindings/) inside of your `wrangler.toml` file, Wrangler's configuration file. Bindings allow us to access Cloudflare resources, like D1 databases, Workers KV namespaces, and R2 buckets, using a variable name in code. In `wrangler.toml`, set up the binding `DB` and connect it to the `database_name` and `database_id`:
 
 ```toml
 [[ d1_databases ]]

src/content/docs/d1/tutorials/build-a-staff-directory-app/index.mdx

@@ -70,7 +70,7 @@ npx wrangler d1 create staff-directory
 
 After creating your database, you will need to set up a [binding](/workers/runtime-apis/bindings/) in the Wrangler configuration file to integrate your database with your application.
 
-This binding enables your application to interact with Cloudflare resources such as D1 databases, KV namespaces, and R2 buckets. To configure this, create a `wrangler.toml` file in your project's root directory and input the basic setup information:
+This binding enables your application to interact with Cloudflare resources such as D1 databases, Workers KV namespaces, and R2 buckets. To configure this, create a `wrangler.toml` file in your project's root directory and input the basic setup information:
 
 ```toml
 name = "staff-directory"

src/content/docs/durable-objects/examples/use-kv-from-durable-objects.mdx

@@ -6,8 +6,8 @@ sidebar:
   order: 20
 head:
   - tag: title
-    content: Durable Objects - Use KV within Durable Objects
-description: Read and write to/from KV within a Durable Object
+    content: Durable Objects - Use Workers KV within Durable Objects
+description: Read and write to/from Workers KV within a Durable Object
 
 ---
 
@@ -17,7 +17,7 @@ The following Worker script shows you how to configure a <GlossaryTooltip term="
 
 Prerequisites:
 
-* A [KV namespace](/kv/api/) created via the Cloudflare dashboard or the [wrangler CLI](/workers/wrangler/install-and-update/).
+* A [Workers KV namespace](/kv/api/) created via the Cloudflare dashboard or the [wrangler CLI](/workers/wrangler/install-and-update/).
 * A [configured binding](/kv/concepts/kv-bindings/) for the `kv_namespace` in the Cloudflare dashboard or `wrangler.toml` file.
 * A [Durable Object namespace binding](/workers/wrangler/configuration/#durable-objects).
 

src/content/docs/email-routing/email-workers/runtime-api.mdx

@@ -56,7 +56,7 @@ export default {
 
 * `env` object
 
-  * An object containing the bindings associated with your Worker using ES modules format, such as KV namespaces and Durable Objects.
+  * An object containing the bindings associated with your Worker using ES modules format, such as Workers KV namespaces and Durable Objects.
 
 * `ctx` object
   * An object containing the context associated with your Worker using ES modules format. Currently, this object just contains the `waitUntil` function.