From 6427a6b15394926b2a44ac3a274d2abb10154bc4 Mon Sep 17 00:00:00 2001
From: foesa <35463247+foesa-yang@users.noreply.github.com>
Date: Thu, 21 Apr 2022 11:20:49 +0800
Subject: [PATCH] Update 1.what-is-br.md

---
 docs-2.0/backup-and-restore/nebula-br/1.what-is-br.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs-2.0/backup-and-restore/nebula-br/1.what-is-br.md b/docs-2.0/backup-and-restore/nebula-br/1.what-is-br.md
index a54f9cb586c..47006b62b27 100644
--- a/docs-2.0/backup-and-restore/nebula-br/1.what-is-br.md
+++ b/docs-2.0/backup-and-restore/nebula-br/1.what-is-br.md
@@ -18,7 +18,7 @@ The BR has the following features. It supports:
 - Supports Nebula Graph v{{ nebula.release }} only.
 - Supports full backup, but not incremental backup.
 - Currently, Nebula Listener and full-text indexes do not support backup.
-- Auto deployment and restoration are supported when there is only one metad process configured in the local file
+- Backup and restore are supported when there is only one metad process configured in the local file.
 - If you back up data to the local disk, the backup files will be saved in the local path of each server. You can also mount the NFS on your host to restore the backup data to a different host.
 - The backup graph space can be restored to the original cluster only. Cross clusters restoration is not supported.
 - During the backup process, both DDL and DML statements in the specified graph spaces are blocked. We recommend that you do the operation within the low peak period of the business, for example, from 2:00 AM to 5:00 AM.