diff --git a/tidb-cloud/backup-and-restore-serverless.md b/tidb-cloud/backup-and-restore-serverless.md
index 091e01bf52e77..703679ab5b02b 100644
--- a/tidb-cloud/backup-and-restore-serverless.md
+++ b/tidb-cloud/backup-and-restore-serverless.md
@@ -74,38 +74,25 @@ TiDB Cloud supports snapshot restore and point-in-time restore for your cluster.
 
 ### Restore destination
 
-TiDB Cloud supports restoring in-place and restoring to a new cluster.
-
-**In-place restore**
-
-Restore to the current cluster will overwrite existing data. Note the following:
-
-- Existing connections will be terminated once the restore is started.
-- The cluster will be unavailable, and new connections will be blocked during the restore process.
-- Restore will affect tables in the `mysql` schema. Any changes to user credentials, permissions, or system variables will be reverted to their state at the backup time.
-
-**Restore to a new cluster**
-
-Create and restore to the new cluster. Note the following:
-
-- User credentials and permissions from the source cluster will not be restored to the new cluster.
+TiDB Cloud supports restoring data to a new cluster.
 
 ### Restore timeout
 
-The restore process typically completes within a few minutes. If the restore takes longer than three hours, it is automatically canceled. The outcome of a canceled restore depends on the destination:
-
-- **In-place restore**: the cluster status changes from **Restoring** to **Available**, and the cluster becomes accessible.
-- **Restore to a new cluster**: the new cluster is deleted and the source cluster remains unchanged.
+The restore process typically completes within a few minutes. If the restore takes longer than three hours, it is automatically canceled and the new cluster is deleted, while the source cluster remains unchanged.
 
 If the data is corrupted after a canceled restore and cannot be recovered, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for assistance.
 
 ### Perform the restore
 
-To restore your TiDB Cloud cluster, follow these steps:
+> **Note:**
+>
+> User credentials and permissions from the source cluster will not be restored to the new cluster.
+
+To restore your data to a new cluster, take the following steps:
 
 1. Navigate to the [**Backup**](#view-the-backup-page) page of your cluster.
 
-2. Click **Restore**. The setting window displays.
+2. Click **Restore**.
 
 3. In **Restore Mode**, you can choose to restore from a specific backup or any point in time.
 
@@ -128,29 +115,13 @@ To restore your TiDB Cloud cluster, follow these steps:
     </div>
     </SimpleTab>
 
-4. In **Destination**, you can choose to restore to a new cluster or restore in-place.
+4. Enter a name for the new cluster.
+5. Choose a plan for the new cluster and update the capacity as needed.
 
-    <SimpleTab>
-    <div label="Restore to a new cluster">
-
-    To restore to a new cluster, take the following steps:
-
-    1. Click **Restore to a New Cluster**.
-    2. Enter a name for the new cluster.
-    3. Choose the cluster plan for the new cluster.
-
-        - If you choose a {{{ .starter }}} cluster and need more resources than the [free quota](/tidb-cloud/select-cluster-tier.md#usage-quota), set a monthly spending limit.
-        - If you choose a {{{ .essential }}} cluster, set the minimum RCU and maximum RCU, and then configure advanced settings as needed.
-
-    </div>
-    <div label="Restore in-place">
-
-    To restore in-place, click **In-place Restore**.
-
-    </div>
-    </SimpleTab>
+    - If you choose a {{{ .starter }}} cluster and need more resources than the [free quota](/tidb-cloud/select-cluster-tier.md#usage-quota), set a monthly spending limit.
+    - If you choose a {{{ .essential }}} cluster, set the minimum RCU and maximum RCU, and then configure advanced settings as needed.
 
-5. Click **Restore** to begin the restore process.
+6. Click **Restore** to begin the restore process.
 
 Once the restore process begins, the cluster status changes to **Restoring**. The cluster will remain unavailable until the restore is complete and the status changes to **Available**.