Fixing more pages

Author: Oxyjun

src/content/docs/kv/examples/cache-data-with-workers-kv.mdx

@@ -107,7 +107,7 @@ if (!bodyMatch) return 'No content found';
 
 }
 
-````
+```
 </TabItem>
 <TabItem label="wrangler.jsonc">
 ```json
@@ -126,7 +126,7 @@ if (!bodyMatch) return 'No content found';
 		}
 	]
 }
-````
+```
 
 </TabItem>
 </Tabs>

src/content/docs/kv/examples/distributed-configuration-with-workers-kv.mdx

@@ -87,7 +87,7 @@ syncPreviewStatus()
 .catch(console.error)
 .finally(() => process.exit(0));
 
-````
+```
 </TabItem>
 <TabItem label=".env">
 ```md title=".env"
@@ -96,7 +96,7 @@ CLOUDFLARE_EMAIL = <CLOUDFLARE_EMAIL_HERE>
 CLOUDFLARE_API_KEY = <CLOUDFLARE_API_KEY_HERE>
 CLOUDFLARE_ACCOUNT_ID = <CLOUDFLARE_ACCOUNT_ID_HERE>
 CLOUDFLARE_WORKERS_KV_NAMESPACE_ID = <CLOUDFLARE_WORKERS_KV_NAMESPACE_ID_HERE>
-````
+```
 
 </TabItem>
 <TabItem label="db.sql">
@@ -115,7 +115,7 @@ INSERT INTO users (username, email, preview_features_enabled) VALUES
 ('bob', '[email protected]', false),
 ('charlie', '[email protected]', true);
 
-````
+```
 </TabItem>
 </Tabs>
 
@@ -216,7 +216,7 @@ export default {
 		}
 	]
 }
-````
+```
 
 </TabItem>
 </Tabs>

src/content/docs/kv/examples/routing-with-workers-kv.mdx

@@ -111,7 +111,7 @@ export default {
 }
 } satisfies ExportedHandler<Env>;
 
-````
+```
 </TabItem>
 <TabItem label="wrangler.jsonc">
 ```json
@@ -130,7 +130,7 @@ export default {
 		}
 	]
 }
-````
+```
 
 </TabItem>
 </Tabs>

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

@@ -13,7 +13,7 @@ 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]
-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.
 :::
@@ -96,7 +96,7 @@ export default {
 
 } satisfies ExportedHandler<Env>;
 
-````
+```
 </TabItem>
 <TabItem label="wrangler.jsonc">
 ```json
@@ -115,7 +115,7 @@ export default {
 		}
 	]
 }
-````
+```
 
 </TabItem>
 </Tabs>
@@ -272,7 +272,7 @@ export default {
 },
 } satisfies ExportedHandler<Env>;
 
-````
+```
 </TabItem>
 <TabItem label="wrangler.jsonc">
 ```json
@@ -291,7 +291,7 @@ export default {
 		}
 	]
 }
-````
+```
 
 </TabItem>
 </Tabs>