diff --git a/Peer-Chunk-Sharing-Between-weed-mount-Clients.md b/P2P-reading-in-weed-mount.md
similarity index 99%
rename from Peer-Chunk-Sharing-Between-weed-mount-Clients.md
rename to P2P-reading-in-weed-mount.md
index f6fbb82..5e19c5f 100644
--- a/Peer-Chunk-Sharing-Between-weed-mount-Clients.md
+++ b/P2P-reading-in-weed-mount.md
@@ -1,4 +1,4 @@
-# Peer Chunk Sharing Between weed mount Clients
+# P2P reading in weed mount
 
 When a fleet of GPU hosts loads the same model file through `weed mount`, every client pulls bytes from the volume tier. Even with [`fs.distributeChunks`](Distributing-AI-Model-Files-for-Multi-GPU-Loading) spreading the chunks evenly across every volume server, the volume tier's total NIC bandwidth caps how fast the read burst can complete. Peer chunk sharing lets mounts fetch chunks from each other instead, so after the first wave seeds a handful of mounts, subsequent reads fan out across the whole fleet.
 
diff --git a/_Sidebar.md b/_Sidebar.md
index ba41f07..a66992d 100644
--- a/_Sidebar.md
+++ b/_Sidebar.md
@@ -60,6 +60,7 @@
 * [[FIO benchmark]]
 * [[fstab and systemd mount]]
 * [[POSIX Compliance]]
+* [[P2P reading in weed mount]]
 
 ### [[WebDAV]]
 
@@ -132,7 +133,6 @@
 ### Machine Learning
 * [[TensorFlow with SeaweedFS]]
 * [[Distributing AI Model Files for Multi-GPU Loading]]
-* [[Peer Chunk Sharing Between weed mount Clients]]
 
 ### HDFS
 * [[Hadoop Compatible File System]]