diff --git a/docs/design_docs/drop_collection_release_resources_en.md b/docs/design_docs/drop_collection_release_resources_en.md
index 1dd1475d9b..95b16bfa01 100644
--- a/docs/design_docs/drop_collection_release_resources_en.md
+++ b/docs/design_docs/drop_collection_release_resources_en.md
@@ -28,18 +28,18 @@ DataNode ignites Flush&Drop
 
 Add a `dropped` flag in `SaveBinlogPathRequest` proto
 
-DN
+DataNode
 - Flush all segments in this vChannel, When Flush&Drop, set the `dropped` flag true.
     - If fails, retry at most 10 times and restart
 
-DC
+DataCoord
 - DataCoord marks segmentInfo as `dropped`, doesn't remove segmentInfos from etcd
 - When recovery, check if the segments in the vchannel are all dropped
     - if not, recover before the drop
     - if so, no need to recover the vchannel
 
 Pros:
-    1. The easiest approach in both DN and DC
+    1. The easiest approach in both DataNode and DataCoord
     2. DN can reuse the current flush manager procedure
 Cons:
     1. The No. rpc call is equal to the No. segments in a collection, expensive