diff --git a/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md b/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md
index 46dde4b28a8..97e3fc77c00 100644
--- a/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md
+++ b/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md
@@ -127,6 +127,7 @@ Kubernetes v1.22, available as an experimental feature of v2.6.3, does not suppo
 
 1. Apply the manifest, and monitor the Restore status:
    1. Apply the `Restore` object resource:
+
       ```bash
       kubectl apply -f restore-migration.yaml
       ```