diff --git a/Erasure-coding-for-warm-storage.md b/Erasure-coding-for-warm-storage.md
index 794cb7d..1bba64c 100644
--- a/Erasure-coding-for-warm-storage.md
+++ b/Erasure-coding-for-warm-storage.md
@@ -31,7 +31,7 @@ With servers added or removed, some data shards may not be laid out optimally. F
 The default command is `ec.balance -force`. It will try to spread the data shards evenly to minimize the data shard loss risk.
 
 ## How the read works?
-When all data shards are online, the read are randomly assigned to one volume server (A) that has at least one data shard. Server A will read its copy of index file, and locate the volume server (B), and read from server B for the file.
+When all data shards are online, the read for one file key are assigned to one volume server (A) that has at least one data shard for the volume. Server A will read its copy of index file, and locate the volume server (B), and read from server B for the file key.
 
 In case of missing data shards or read failures from server B, server A will try to collect as many pieces of data as possible from the remaining servers, and compute the required data.