fixed typo

Author: Harikrishnan-M-B

articles/frontdoor/migrate-cdn-to-front-door.md

@@ -20,7 +20,7 @@ We recommend that your plan this migration well in advance and test the function
 
 > [!IMPORTANT]
 > - If you plan to migrate to Azure Front Door, set the Feature Flag **DoNotForceMigrateEdgioCDNProfiles** before January 7, 2025 using [Set up preview feature](../azure-resource-manager/management/preview-features.md). This will prevent Microsoft from auto-migrating your profiles to Azure Front Door. Auto-migration is on a *best effort* basis and may cause issues with billing, features, availability, and performance. Note you will have until January 14, 2025 to complete your migration to another CDN, but again Microsoft cannot guarantee your services will be available on the Edgio platform before this date.
-> - This guide only works if you are already using custom domains on Azure CDN from Edgio. If you don't use custom domains, you won't be able to use traffic manager to gradually shift traffic to  Front Door. You will have to update the clients to directly point to the new Front Door endpoint. Another temporary option will be to migrate to Front Door while [retaining your `<endpointname>.azureedge.net` domain.](../cdn/migrate-cdn-to-front-door-retain-edge-domain)
+> - This guide only works if you are already using custom domains on Azure CDN from Edgio. If you don't use custom domains, you won't be able to use traffic manager to gradually shift traffic to  Front Door. You will have to update the clients to directly point to the new Front Door endpoint. Another temporary option will be to migrate to Front Door while [retaining your `<endpointname>.azureedge.net` domain.](../cdn/migrate-cdn-to-front-door-retain-edge-domain.md)
 
 
 ## Prerequisites