diff --git a/docs/design_docs/milvus_create_index_en.md b/docs/design_docs/milvus_create_index_en.md
index 544ae748ed..383e9ac086 100644
--- a/docs/design_docs/milvus_create_index_en.md
+++ b/docs/design_docs/milvus_create_index_en.md
@@ -180,13 +180,13 @@ message CreateIndexRequest {
 
 14. There is a background service, `indexBuildLoop`, in the `IndexNode`. `indexBuildLoop` would call `scheduleIndexBuildTask` to get a `IndexBuildTask` from `IndexBuildQueue`, and then start another `goroutine` to build index and update meta.
 
-_Note_: `IndexNode` will not notify the `QueryCoord` to load the index files, if an user wants to speed up search by these index files, he should call `ReleaseCollection` firstly, then call `LoadCollection` to load these index files.
+_Note_: `IndexNode` will not notify the `QueryCoord` to load the index files, if a user wants to speed up search by these index files, he should call `ReleaseCollection` firstly, then call `LoadCollection` to load these index files.
 
 15. As mentioned earlier, `RootCoord` would only search on these flushed segments on `CreateIndex` request, the following figure show how to deal with the newly added segments.
 
 ![data_coord_flushed](./graphs/milvus_create_index_data_coord_flushed.png)
 
-16. When a segment has been flushed, `DataCoord` would notify `RootCoord` via `SegmentFlushCompleted`, the `proto` is defined as follow:
+16. When a segment has been flushed, `DataCoord` would notify `RootCoord` via `SegmentFlushCompleted`, the `proto` is defined as follows:
 
 ```proto
 service RootCoord {