diff --git a/S3-Vector-Bucket.md b/S3-Vector-Bucket.md
index 2c5aa96..b9ed466 100644
--- a/S3-Vector-Bucket.md
+++ b/S3-Vector-Bucket.md
@@ -26,11 +26,8 @@ flowchart TB
         vector["<b>vector bucket</b><br/>a table bucket with format LANCE"]
     end
     engine["<b>weed-vector</b><br/>exact search over the index"]
-    subgraph store ["stored in SeaweedFS, through the gateway's S3 API"]
-        direction LR
-        filers[("<b>filers</b><br/>file metadata")]
-        volumes[("<b>volume servers</b><br/>file chunks")]
-    end
+    filers[("<b>filers</b><br/>file metadata")]
+    volumes[("<b>volume servers</b><br/>file chunks")]
     client -->|"S3, S3 Tables and S3 Vectors requests"| gateway
     gateway --> normal
     gateway --> table
@@ -44,7 +41,6 @@ flowchart TB
     class gateway s3server
     class client,normal,table,vector,engine,filers,volumes other
     style buckets fill:none,stroke:#94a3b8
-    style store fill:none,stroke:#94a3b8
 ```
 
 The gateway serves all three bucket kinds on the S3 port. A vector bucket is a table bucket with format `LANCE`; each index is one Lance dataset under `s3://<bucket>/vector/<index>/`. `weed-vector` reads and writes it through the gateway's S3 API, and the gateway, as for any S3 request, keeps the file metadata on the filers and the chunks on the volume servers.