diff --git a/docs/design_docs/retrieve_entity.md b/docs/design_docs/retrieve_entity.md
index 9827d234b3..3b67efc9a1 100644
--- a/docs/design_docs/retrieve_entity.md
+++ b/docs/design_docs/retrieve_entity.md
@@ -27,7 +27,7 @@ QueryNode subscribes to the insert channel and will determine whether to use the
 
 When the DataNode processes each inserted entity, it updates the bloomfilter of the Segment to which the entity belongs. If it does not exist, it creates a bloomfilter in memory and updates it.
 
-Once DataNode receives a Flush command from DataCoord, it sorts the data in the segment in ascending order of primary key, records the maximum and minimum values of primary key, and writes the segment, statistics and bloomfilter to storage system.
+Once DataNode receives a Flush command from DataCoord, it sorts the data in the segment in ascending order of primary key, records the maximum and minimum values of primary key, and writes the segment, statistics and bloomfilter to the storage system.
 
 - Key of binlog file: `${tenant}/insert_log/${collection_id}/${partition_id}/${segment_id}/${field_id}/_${log_idx}`
 - Key of statistics file: `${tenant}/insert_log/${collection_id}/${partition_id}/${segment_id}/${field_id}/stats_${log_idx}`