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 25cf4052ca4..85179661300 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
@@ -24,7 +24,7 @@ The BR has the following features. It supports:
 - 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.
 - Supports restoration of data on clusters of the same topologies only, which means both clusters must have exactly the same number of hosts.
 - We recommend that you restore the data OFFLINE because it requires removing the data and restart the service.
-- If you backup data of a specified graph space in cluster A, the backup files CAN NOT be restored to cluster B. Restore specified graph space will delete all other graph space in the cluster. (experimental).
+- If you back up data of a specified graph space in cluster A and restore the graph space data to cluster B, the data of other graph spaces in cluster B will be deleted.
 <!---When backing up or restoring the data deployed in Docker, network configuration should be done, such as IP and port mapping. -->
 
 <!--
diff --git a/docs-2.0/backup-and-restore/nebula-br/4.br-restore-data.md b/docs-2.0/backup-and-restore/nebula-br/4.br-restore-data.md
index 16510680887..7ffc6ea9e39 100644
--- a/docs-2.0/backup-and-restore/nebula-br/4.br-restore-data.md
+++ b/docs-2.0/backup-and-restore/nebula-br/4.br-restore-data.md
@@ -27,7 +27,7 @@ To restore data with the BR, do a check of these:
 1. Users can use the following command to list the existing backup information:
 
   ```bash
-  $ ./bin/br show --storage <ip_address>
+  $ ./bin/br show --storage <storage_path>
   ```
   For example, run the following command to list the backup information in the local `/home/nebula/backup` path.
   ```bash