From eed0c95181b9e069fa26d2ccf60ed4940746b46f Mon Sep 17 00:00:00 2001 From: Bennu Date: Thu, 30 Dec 2021 16:31:40 +0800 Subject: [PATCH] [skip e2e] Fix grammar (#14618) Signed-off-by: Bennu --- docs/design_docs/milvus_timesync_en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design_docs/milvus_timesync_en.md b/docs/design_docs/milvus_timesync_en.md index 176f437bfb..61b5a21c87 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 from local clock, 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.