From 460b49310d544b112b2c770f411921d1ecba03c7 Mon Sep 17 00:00:00 2001 From: Bennu Date: Fri, 31 Dec 2021 14:18:07 +0800 Subject: [PATCH] [skip e2e] Fix grammar (#14659) 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 dde15cd1ef..feb126313e 100644 --- a/docs/design_docs/milvus_timesync_en.md +++ b/docs/design_docs/milvus_timesync_en.md @@ -42,7 +42,7 @@ It's easy to achieve this in a `single-node` database. But for a `Distributed Sy 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. +`TSO` is provided by the `RootCoord` component. Clients could alloc one or more timestamp in a single request; the `proto` is defined as follows. ```proto service RootCoord {