chore: fix formatting

Author: unatasha8

docs/migrate-to-ory/migrate/migrate-strategies.mdx

@@ -30,6 +30,7 @@ segments or applications, learning valuable lessons to refine your approach befo
     {label: 'Single-phase rollout', value: 'single'},
     {label: 'Multi-phase rollout', value: 'multi'},
   ]}>
+
 <TabItem value="single">
 
 ### Single-phase rollout
@@ -64,9 +65,11 @@ A single-phase rollout approach is the best choice when:
   design flaws, training gaps, or technical issues only become apparent when it's too late to adjust your approach.
 - Difficult rollback: Reverting to the old system after a full cutover can be complex and potentially impossible if you've already
   decommissioned infrastructure or migrated data irreversibly.
-  </TabItem>
+
+</TabItem>
 
 <TabItem value="multi">
+
 ### Multi-phase rollout
 
 A multi-phase approach involves migrating user identities and rolling out applications/services in phases, focusing on specific
@@ -91,8 +94,11 @@ A multi-phase rollout is the best choice in most cases, especially when:
 
 - Complex management: Multiple "go-lives" require more coordination and detailed planning, increasing operational complexity.
 - Extended timeline: The time to roll out the whole system takes longer as it is broken down into phases.
-- Resource demands: Running both systems in parallel during the transition can strain resources. </TabItem>
-  </Tabs>
+- Resource demands: Running both systems in parallel during the transition can strain resources. 
+
+</TabItem>
+
+</Tabs>
 
 ## Choose your user identity migration strategy
 
@@ -110,6 +116,7 @@ Network.
     {label: 'Bulk identity migration', value: 'bulk'},
     {label: 'Graceful identity migration', value: 'graceful'},
   ]}>
+
 <TabItem value="bulk">
 
 ### Bulk identity migration
@@ -140,7 +147,10 @@ A bulk identity migration can involve some risk and downtime, but it is recommen
   perform a rollback.
 - Downtime: This approach may require planned system downtime to ensure data consistency, which can disrupt users.
 - Increased preparation: Requires extensive planning and testing to mitigate risks, making it more resource-intensive during that
-  phase. </TabItem>
+  phase. 
+  
+  </TabItem>
+
   <TabItem value="graceful">
 
 ### Graceful identity migration
@@ -174,5 +184,8 @@ A graceful identity migration is a good choice when:
   additional coding effort to implement Ory's
   [password migration using a web hook](https://www.ory.com/docs/kratos/manage-identities/import-user-accounts-identities#password-migration-using-a-web-hook).
 - Potential for data inconsistencies: If not carefully managed, there may be discrepancies between the old and new systems during
-  the transition period. </TabItem>
+  the transition period. 
+  
+  </TabItem>
+  
   </Tabs>