From 717e3e88dda51eaa7966063971021209042aa7ed Mon Sep 17 00:00:00 2001
From: "max.zhu@vesoft.com" <86282370+izhuxiaoqing@users.noreply.github.com>
Date: Tue, 24 Aug 2021 16:26:05 +0800
Subject: [PATCH] Update 2.meta-service.md (#622)

---
 .../3.nebula-graph-architecture/2.meta-service.md             | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs-2.0/1.introduction/3.nebula-graph-architecture/2.meta-service.md b/docs-2.0/1.introduction/3.nebula-graph-architecture/2.meta-service.md
index 09aaf46c015..28dd6041574 100644
--- a/docs-2.0/1.introduction/3.nebula-graph-architecture/2.meta-service.md
+++ b/docs-2.0/1.introduction/3.nebula-graph-architecture/2.meta-service.md
@@ -1,6 +1,6 @@
 # Meta Service
 
-This article will introduce the architecture and functions of the Meta Service.
+This topic introduces the architecture and functions of the Meta Service.
 
 ## The architecture of the Meta Service
 
@@ -8,7 +8,7 @@ The architecture of the Meta Service is as follows:
 
 ![The architecture of the Meta Service](https://docs-cdn.nebula-graph.com.cn/docs-2.0/1.introduction/2.nebula-graph-architecture/meta-architecture1.png)
 
-The Meta Service is run by the nebula-metad processes. Users can deploy nebula-metad processes according to the scenario:
+The Meta Service is run by nebula-metad processes. Users can deploy nebula-metad processes according to the scenario:
 
 * In a test environment, users can deploy one or three nebula-metad processes on different machines or a single machine.
 * In a production environment, we recommend that users deploy three nebula-metad processes on different machines for high availability.