Skip to content

Commit 5505a22

Browse files
committed
fixed term
1 parent fc39ad4 commit 5505a22

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/cdn/cdn-change-provider.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Once you've completed your proof of concept testing, you can begin the migration
7676
> Items to verify prior to migrating production workloads
7777
> 1. Verify configuration settings such as cache objects, TTLs and other potential custom settings at the CDN profile level are being accommodated.
7878
> 2. Origin application customizations are adjusted:
79-
> * Update Access Control List (ACL) if one is being used to whitelist CDN egress ranges.
79+
> * Update Access Control List (ACL) if one is being used to allow CDN egress ranges.
8080
> * Traffic management tools such as a load balancer has the correct policies and rules for the CDN.
8181
> 3. Validate origin workloads and CDN caching performance.
8282
> * Changing between CDNs can increase traffic to origin for a period of time until the new provider caches the content.
@@ -92,4 +92,4 @@ For more information, see [Failover CDN endpoints with Traffic Manager](cdn-traf
9292
## Next Steps
9393

9494
* Create an [Azure Front Door](../frontdoor/create-front-door-portal.md) profile.
95-
* Create [Azure CDN from Verizon](cdn-create-endpoint-how-to.md) profile.
95+
* Create an [Azure CDN from Verizon](cdn-create-endpoint-how-to.md) profile.

0 commit comments

Comments
 (0)