fix build error

Author: halkazwini

articles/frontdoor/standard-premium/tls-policy-configure.md

@@ -40,7 +40,7 @@ If you're using Azure to host your [DNS domains](/azure/dns/dns-overview), you m
 ## Verify TLS policy configurations
 
 1. Once the custom domain with TLS policy is deployed successfully, you can test it in your browser. 
-1. View the supported cipher suit of your domain via <https://www.ssllabs.com/ssltest/analyze.html?d=p2c1test.bugbash.dev.azfdtest.xyz&latest> or use the sslscan tool.
+1. View the supported cipher suite of your domain via <https://www.ssllabs.com/ssltest/analyze.html?d=p2c1test.bugbash.dev.azfdtest.xyz&latest> or use the sslscan tool.
 
 ## Related content
 

articles/frontdoor/standard-premium/tls-policy.md

@@ -10,7 +10,7 @@ ms.date: 03/16/2025
 
 # Azure Front Door TLS policy 
 
-Azure Front Door supports [end-to-end TLS encryption](end-to-end-tls.md). When you add a custom domain to Azure Front Door, HTTPS is required, and you need to define a TLS policy which includes control of the TLS protocol version as well as the cipher suites and the order in which ciphers are used during a TLS handshake. 
+Azure Front Door supports [end-to-end TLS encryption](../end-to-end-tls.md). When you add a custom domain to Azure Front Door, HTTPS is required, and you need to define a TLS policy which includes control of the TLS protocol version as well as the cipher suites and the order in which ciphers are used during a TLS handshake. 
 
 Azure Front Door supports four versions of the TLS protocol: TLS versions 1.0, 1.1, 1.2 and 1.3. Although TLS 1.2 introduced client/mutual authentication in RFC 5246, Azure Front Door currently doesn't support client/mutual authentication (mTLS).