Hopefully fixing links, some rewording

Author: dotpaul

docs/code-quality/ca5361.md

@@ -25,20 +25,20 @@ f1_keywords:
 
 ## Cause
 
-A <xref:System.AppContext.SetSwitch?displayProperty=nameWithType> method call sets `Switch.System.Net.DontEnableSchUseStrongCrypto` to `true`.
+A <xref:System.AppContext.SetSwitch%2A?displayProperty=nameWithType> method call sets `Switch.System.Net.DontEnableSchUseStrongCrypto` to `true`.
 
 ## Rule description
 
-Setting `Switch.System.Net.DontEnableSchUseStrongCrypto` to `true` weakens the security of outgoing Transport Layer Security (TLS) connections, by using weaker cryptography. See [Transport Layer Security (TLS) best practices with the .NET Framework](/dotnet/framework/network-programming/tls#switchsystemnetdontenableschusestrongcrypto) for more information.
+Setting `Switch.System.Net.DontEnableSchUseStrongCrypto` to `true` weakens the cryptography used in outgoing Transport Layer Security (TLS) connections. Weaker cryptography can compromise the confidentiality of communication between your application and the server, making it easier for attackers to eavesdrop sensitive data. For more information, see [Transport Layer Security (TLS) best practices with the .NET Framework](/dotnet/framework/network-programming/tls#switchsystemnetdontenableschusestrongcrypto).
 
 ## How to fix violations
 
-- If your application targets .NET Framework v4.6 or later, you can remove the <xref:System.AppContext.SetSwitch?displayProperty=nameWithType> method call.
+- If your application targets .NET Framework v4.6 or later, you can remove the <xref:System.AppContext.SetSwitch%2A?displayProperty=nameWithType> method call.
 - If your application targets .NET Framework earlier than v4.6, and runs on .NET Framework v4.6 or later, set the switch's value to `false`.
 
 ## When to suppress warnings
 
-Suppress this warning if you must connect to a legacy service that cannot be upgraded to use more secure configurations of TLS.
+You can suppress this warning if you need to connect to a legacy service, which can't be upgraded to use secure TLS configurations.
 
 ## Pseudo-code examples
 
@@ -63,7 +63,7 @@ Imports System
 Public Class ExampleClass
     Public Sub ExampleMethod()
         ' CA5361 violation
-        AppContext.SetSwitch(""Switch.System.Net.DontEnableSchUseStrongCrypto"", true)
+        AppContext.SetSwitch("Switch.System.Net.DontEnableSchUseStrongCrypto", true)
     End Sub
 End Class
 ```
@@ -77,7 +77,7 @@ public class ExampleClass
 {
     public void ExampleMethod()
     {
-        AppContext.SetSwitch(""Switch.System.Net.DontEnableSchUseStrongCrypto"", false);
+        AppContext.SetSwitch("Switch.System.Net.DontEnableSchUseStrongCrypto", false);
     }
 }
 ```
@@ -87,7 +87,7 @@ Imports System
 
 Public Class ExampleClass
     Public Sub ExampleMethod()
-        AppContext.SetSwitch(""Switch.System.Net.DontEnableSchUseStrongCrypto"", false)
+        AppContext.SetSwitch("Switch.System.Net.DontEnableSchUseStrongCrypto", false)
     End Sub
 End Class
 ```