diff --git a/command-line-flags-for-tidb-configuration.md b/command-line-flags-for-tidb-configuration.md
index 6db3a5dbfaf21..a6a7e05f50b5d 100644
--- a/command-line-flags-for-tidb-configuration.md
+++ b/command-line-flags-for-tidb-configuration.md
@@ -97,11 +97,11 @@ When you start the TiDB cluster, you can use command-line options or environment
 
 ## `--path`
 
-- The path to the data directory for local storage engine like "mocktikv"
-- For `--store = tikv`, you must specify the path; for `--store = mocktikv`, the default value is used if you do not specify the path.
+- The path to the data directory for local storage engine like "unistore"
+- For `--store = tikv`, you must specify the path; for `--store = unistore`, the default value is used if you do not specify the path.
 - For the distributed storage engine like TiKV, `--path` specifies the actual PD address. Assuming that you deploy the PD server on 192.168.100.113:2379, 192.168.100.114:2379 and 192.168.100.115:2379, the value of `--path` is "192.168.100.113:2379, 192.168.100.114:2379, 192.168.100.115:2379".
 - Default: "/tmp/tidb"
-- You can use `tidb-server --store=mocktikv --path=""` to enable a pure in-memory TiDB.
+- You can use `tidb-server --store=unistore --path=""` to enable a pure in-memory TiDB.
 
 ## `--tmp-storage-path`
 
@@ -162,8 +162,8 @@ When you start the TiDB cluster, you can use command-line options or environment
 ## `--store`
 
 - Specifies the storage engine used by TiDB in the bottom layer
-- Default: "mocktikv"
-- You can choose "mocktikv" or "tikv". ("mocktikv" is the local storage engine; "tikv" is a distributed storage engine)
+- Default: "unistore"
+- You can choose "unistore" or "tikv". ("unistore" is the local storage engine; "tikv" is a distributed storage engine)
 
 ## `--token-limit`
 
diff --git a/sql-statements/sql-statement-backup.md b/sql-statements/sql-statement-backup.md
index 374c957a90bf4..77e24624ad81a 100644
--- a/sql-statements/sql-statement-backup.md
+++ b/sql-statements/sql-statement-backup.md
@@ -16,7 +16,7 @@ The `BACKUP` statement is blocked until the entire backup task is finished, fail
 
 Only one `BACKUP` and [`RESTORE`](/sql-statements/sql-statement-restore.md) task can be executed at a time. If a `BACKUP` or `RESTORE` statement is already being executed on the same TiDB server, the new `BACKUP` execution will wait until all previous tasks are finished.
 
-`BACKUP` can only be used with "tikv" storage engine. Using `BACKUP` with the "mocktikv" engine will fail.
+`BACKUP` can only be used with "tikv" storage engine. Using `BACKUP` with the "unistore" engine will fail.
 
 ## Synopsis
 
diff --git a/sql-statements/sql-statement-restore.md b/sql-statements/sql-statement-restore.md
index bcb98e6b14c21..7dea34c622692 100644
--- a/sql-statements/sql-statement-restore.md
+++ b/sql-statements/sql-statement-restore.md
@@ -20,7 +20,7 @@ The `RESTORE` statement is blocking, and will finish only after the entire resto
 
 Only one `BACKUP` and `RESTORE` task can be executed at a time. If a `BACKUP` or `RESTORE` task is already running on the same TiDB server, the new `RESTORE` execution will wait until all previous tasks are done.
 
-`RESTORE` can only be used with "tikv" storage engine. Using `RESTORE` with the "mocktikv" engine will fail.
+`RESTORE` can only be used with "tikv" storage engine. Using `RESTORE` with the "unistore" engine will fail.
 
 ## Synopsis