Skip to content

Commit 364d7cc

Browse files
committed
chore: formatting fixes
1 parent 3275ee3 commit 364d7cc

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ organizations that use these products or services to run their own operations.
6060
- Role-based permissions and API controls
6161
- Privacy compliance (GDPR, CCPA)
6262
- High-scale performance for millions of users
63-
</TabItem>
63+
</TabItem>
6464
<TabItem value="Workforce">
6565

6666
### Workforce (Business-to-Enterprise)
@@ -80,7 +80,7 @@ offboarding, and permission management.
8080
- Zero-trust security, MFA, and SSO for enterprise applications
8181
- Privacy compliance (GDPR, CCPA)
8282
- High-scale performance for millions of users
83-
</TabItem>
83+
</TabItem>
8484
<TabItem value="Agentic AI">
8585

8686
### Agentic AI
@@ -92,7 +92,7 @@ resources and clients (AI applications) that discover and use those resources.
9292

9393
- Standardized protocol that works across many tools and data sources
9494
- Built-in authentication and access control
95-
</TabItem>
95+
</TabItem>
9696
</Tabs>
9797

9898
## Map all identity flows in your application

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ A multi-phase rollout is the best choice in most cases, especially when:
9292
- Complex management: Multiple "go-lives" require more coordination and detailed planning, increasing operational complexity.
9393
- Extended timeline: The time to roll out the whole system takes longer as it is broken down into phases.
9494
- Resource demands: Running both systems in parallel during the transition can strain resources.
95-
</TabItem>
95+
</TabItem>
9696
</Tabs>
9797

9898
## Choose your user identity migration strategy
@@ -142,7 +142,7 @@ A bulk identity migration can involve some risk and downtime, but it is recommen
142142
- Downtime: This approach may require planned system downtime to ensure data consistency, which can disrupt users.
143143
- Increased preparation: Requires extensive planning and testing to mitigate risks, making it more resource-intensive during that
144144
phase.
145-
</TabItem>
145+
</TabItem>
146146
<TabItem value="graceful">
147147

148148
### Graceful identity migration
@@ -177,5 +177,5 @@ A graceful identity migration is a good choice when:
177177
[password migration using a web hook](https://www.ory.com/docs/kratos/manage-identities/import-user-accounts-identities#password-migration-using-a-web-hook).
178178
- Potential for data inconsistencies: If not carefully managed, there may be discrepancies between the old and new systems during
179179
the transition period.
180-
</TabItem>
180+
</TabItem>
181181
</Tabs>

0 commit comments

Comments
 (0)