From 69a57bc9ec47bb41246030bf139783f1008673e9 Mon Sep 17 00:00:00 2001
From: pz1116 <47019764+Pz1116@users.noreply.github.com>
Date: Wed, 22 Apr 2026 17:59:16 +0800
Subject: [PATCH] [Doc][0.18.0]Fix typo in KV Cache Pool developr guide (#8575)

### What this PR does / why we need it?
Fix typo in KV Cache Pool developr guide

Signed-off-by: pz1116 <47019764+Pz1116@users.noreply.github.com>
---
 .../developer_guide/Design_Documents/KV_Cache_Pool_Guide.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/source/developer_guide/Design_Documents/KV_Cache_Pool_Guide.md b/docs/source/developer_guide/Design_Documents/KV_Cache_Pool_Guide.md
index 54c70898..aeb10eea 100644
--- a/docs/source/developer_guide/Design_Documents/KV_Cache_Pool_Guide.md
+++ b/docs/source/developer_guide/Design_Documents/KV_Cache_Pool_Guide.md
@@ -33,7 +33,7 @@ When combined with vLLM's Prefix Caching mechanism, the pool enables efficient c
 Prefix Caching with on-chip memory is already supported by the vLLM V1 Engine.
 By introducing KV Connector V1, users can seamlessly combine on-chip memory-based Prefix Caching with Mooncake-backed KV Pool.
 
- The user can enable both features simply by enabling Prefix Caching, which is enabled by default in vLLM V1 unless the `--no_enable_prefix_caching` flag is set, and setting up the KV Connector for KV Pool (e.g., the MooncakeStoreConnector).
+ The user can enable both features simply by enabling Prefix Caching, which is enabled by default in vLLM V1 unless the `--no-enable-prefix-caching` flag is set, and setting up the KV Connector for KV Pool (e.g., the MooncakeStoreConnector).
 
 **Workflow**: