From cac3ed8fb2be3ab5b0cc44750aba7a75dec796db Mon Sep 17 00:00:00 2001
From: Jun Lee <junlee@cloudflare.com>
Date: Thu, 22 Aug 2024 09:51:03 +0100
Subject: [PATCH] Using existing component to handle toml file name.

---
 src/content/docs/kv/concepts/kv-bindings.mdx | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/src/content/docs/kv/concepts/kv-bindings.mdx b/src/content/docs/kv/concepts/kv-bindings.mdx
index d378763836bd6d..c8a1df0e9cba61 100644
--- a/src/content/docs/kv/concepts/kv-bindings.mdx
+++ b/src/content/docs/kv/concepts/kv-bindings.mdx
@@ -55,10 +55,7 @@ When you use Wrangler to develop locally with the `wrangler dev` command, Wrangl
 
 To have `wrangler dev` connect to your Workers KV namespace running on Cloudflare's global network, call `wrangler dev --remote` instead. This will use the `preview_id` of the KV binding configuration in the `wrangler.toml` file. This is how a `wrangler.toml` file looks with the `preview_id` specified.
 
-```toml
----
-filename: wrangler.toml
----
+```toml title="wrangler.toml"
 name = "worker"
 
 # ...