adjust warning

Author: gitName

articles/api-management/api-management-howto-manage-protocols-ciphers.md

@@ -62,10 +62,10 @@ TLS 1.3 is a major revision of the TLS protocol that provides improved security
 
 TLS 1.3 doesn't support certificate renegotiation. Certificate renegotiation in TLS allows client and server to renegotiate connection parameters mid-session for authentication without terminating the connection.
 
-Services that we identified as reliant on client certificate renegotiation do not have TLS 1.3 enabled by default. In these instances, you can review recent API requests that used certificate renegotiation and choose whether to enable TLS 1.3 for client-side connections.
+Services that we identified as reliant on client certificate renegotiation do not have TLS 1.3 enabled by default. 
 
 > [!WARNING]
-> If your APIs are accessed by TLS-compliant clients that rely on certificate renegotiation, enabling TLS 1.3 for client-side connections will cause those clients to fail to connect. 
+> If your APIs are accessed by TLS-compliant clients that rely on certificate renegotiation, enabling TLS 1.3 for client-side connections will cause those clients to fail to connect. Review APIs that recently used certificate renegotiation before enabling client-side TLS 1.3 in any service that doesn't have it enabled by default.
 
 To enable TLS 1.3 for client-side connections in these instances, configure settings on the **Protocols + ciphers** page: