diff --git a/docs/design_docs/milvus_timesync_en.md b/docs/design_docs/milvus_timesync_en.md
index 987c738747..e0ffacb7a0 100644
--- a/docs/design_docs/milvus_timesync_en.md
+++ b/docs/design_docs/milvus_timesync_en.md
@@ -40,7 +40,7 @@ It's easy to achieve this in a `single-node` database. But for a `Distributed Sy
 
 ## Timestamp Oracle(TSO)
 
-Like [TiKV](https://github.com/tikv/tikv), Milvus 2.0 provides `TSO` service. All the events must alloc timestamp from `TSO`，not use local timestamp, so the first problem can be solved.
+Like [TiKV](https://github.com/tikv/tikv), Milvus 2.0 provides `TSO` service. All the events must alloc timestamp from `TSO`，not from local clock, so the first problem can be solved.
 
 `TSO` is provided by the `RootCoord` component. Clients could alloc one or more timestamp in a single request; the `proto` is defined as following.