fixed session affinity link

Author: duongau

articles/frontdoor/blue-green-deployment.md

@@ -79,7 +79,7 @@ Azure Front Door is Microsoft's modern cloud Content Delivery Network (CDN) that
     > [!NOTE]
     > Initially, set the weight of the current origin higher than the new origin to ensure most traffic is routed to the current origin. Gradually increase the weight of the new origin and decrease the weight of the current origin as you test. The total weight doesn't need to be 100, but it helps visualize traffic distribution. The example sets the existing origin to receive three times as much traffic as the new origin.
 
-1. Enable session affinity if your application requires it. For more information, see [Session affinity](routing-methods.md#session-affinity).
+1. Enable session affinity if your application requires it. For more information, see [Session affinity](routing-methods.md). 
 
     > [!NOTE]
     > *Session affinity* ensures the end user is routed to the same origin after the first request. Enable this feature based on your application and the type of enhancements being rolled out. For major revisions, enable session affinity to keep users on the new codebase. For minor enhancements, you can leave session affinity disabled. When in doubt, enable session affinity.

articles/frontdoor/routing-methods.md

@@ -91,7 +91,6 @@ The weighted method supports several scenarios:
 * **Application migration to Azure**: Create an origin group with both Azure and external origins. Adjust weights to prefer new origins, gradually increasing their traffic share until they handle most traffic, then disable and remove less preferred origins.
 * **Cloud-bursting for additional capacity**: Expand on-premises deployments into the cloud by adding or enabling more origins and specifying traffic distribution.
 
-
 ## <a name="affinity"></a>Session affinity
 
 By default, Azure Front Door forwards requests from the same client to different origins. However, session affinity is useful for stateful applications or scenarios where subsequent requests from the same user need to be processed by the same origin. This feature ensures that the same origin handles a user's session, which is beneficial for scenarios like client authentication.