From ef6df7b4a6c290ed07f7a6ccc3cf45fc8e772361 Mon Sep 17 00:00:00 2001
From: randomJoe211 <69501902+randomJoe211@users.noreply.github.com>
Date: Thu, 31 Mar 2022 10:37:16 +0800
Subject: [PATCH] Update docs-2.0/reuse/source_manage-service.md

---
 docs-2.0/reuse/source_manage-service.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs-2.0/reuse/source_manage-service.md b/docs-2.0/reuse/source_manage-service.md
index 43566b68115..c1342f0173c 100644
--- a/docs-2.0/reuse/source_manage-service.md
+++ b/docs-2.0/reuse/source_manage-service.md
@@ -45,7 +45,7 @@ For easy maintenance, Nebula Graph supports managing services with systemd. You
 
 !!! note
 
-    After installing the Nebula Graph, the `.service` files required for systemd are located in the `etc/unit` path under the installation directory.  The Nebula Graph installed with the RPM/DEB package automatically places the `.service` files into the path `/usr/lib/systemd/system` and the parameter `ExecStart` is generated automatically based on the specified Nebula Graph installation path, so you can use `systemctl` commands directly.
+    After installing Nebula Graph, the `.service` files required by systemd are located in the `etc/unit` path in the installation directory. Nebula Graph installed with the RPM/DEB package automatically places the `.service` files into the path `/usr/lib/systemd/system` and the parameter `ExecStart` is generated based on the specified Nebula Graph installation path, so you can use `systemctl` commands directly.
 
     Otherwise, users need to move the `.service` files manually into the directory `/usr/lib/systemd/system`, and modify the file path of the parameter `ExecStart` in the `.service` files.