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

Author: thomasgauvin

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

@@ -13,7 +13,9 @@ import { Render, PackageManagers, TabItem, Tabs } from "~/components";
 By storing static assets in Workers KV, you can retrieve these assets globally with low-latency and high throughput. You can then serve these assets directly, or use them to dynamically generate responses. This can be useful when serving files such as custom scripts, small images that fit within [KV limits](/kv/platform/limits/), or when generating dynamic HTML responses from static assets such as translations.
 
 :::note[Note]
-[Workers KV](/kv) allows you to access, edit and store assets directly from your [Worker](/workers). If you need to host a front-end or full-stack web application, use [Cloudflare Workers static assets](/workers/static-assets/) or [Cloudflare Pages](/pages/), which provide a purpose-built deployment experience for web applications and their assets. 
+If you need to **host a front-end or full-stack web application**, **use [Cloudflare Workers static assets](/workers/static-assets/) or [Cloudflare Pages](/pages/)**, which provide a purpose-built deployment experience for web applications and their assets. 
+
+[Workers KV](/kv) provides a more flexible API which allows you to access, edit and store assets directly from your [Worker](/workers) without requiring deployments. This can be helpful for serving custom assets that are not included in your deployment bundle, such as uploaded media assets or custom scripts and files generated at runtime.
 :::
 
 ## Write static assets to Workers KV using Wrangler