Clarify key module preferences and IKEv2 requirements

Removed redundant information about the Default key module preference and clarified the requirement for the TunnelType parameter in IKEv2.

Author: dallasbrooks

docset/winserver2025-ps/NetSecurity/New-NetIPsecRule.md

@@ -425,10 +425,10 @@ Specifies that matching IPsec rules of the indicated key module are created.
 This parameter specifies which keying modules to negotiate.
 The acceptable values for this parameter are: Default, AuthIP, IKEv1, or IKEv2.
 
-- Default: KeyModule is set based on the authentication method. As of Windows 11, version 24H2 and Windows Server 2025, the Default prefers IKEv2, falls back to IKEv1, and only includes AuthIP if the configured authentication method(s) require it. The protocol actually used depends on what the remote peer supports. In previous releases, Default prefers IKEv1 and falls back to AuthIP. This value is required in order for the rule to be applied to computers running Windows versions prior to Windows Server 2008.
+- Default: KeyModule is set based on the authentication method. As of Windows 11, version 24H2 and Windows Server 2025, the Default prefers IKEv2, falls back to IKEv1, and only includes AuthIP if the configured authentication method(s) require it. In previous releases, Default prefers IKEv1 and falls back to AuthIP. This value is required in order for the rule to be applied to computers running Windows versions prior to Windows Server 2008.
 - AuthIP: Supported with phase 2 authentication. 
 - IKEv1: Supported with pre-shared key (PSK), Certificates, and Kerberos. Supported with phase 1 authentication only.
-- IKEv2: Not supported with Kerberos or NTLM. Supported with phase 1 authentication only. When used with tunnel mode, the *TunnelType* parameter must be specified.
+- IKEv2: Not supported with Kerberos or NTLM. Supported with phase 1 authentication only. When used with the *Mode* parameter set to Tunnel, the *TunnelType* parameter must be specified.
 
 The default value is Default. There are authentication and cryptographic methods that are only compatible with certain keying modules. This is a very advanced setting intended only for specific interoperability scenarios. Overriding this parameter value may result in traffic being sent in plain-text if the authorization and cryptographic settings are not supported by the keying modules. Windows versions prior to Windows Server 2012 only support the Default configuration.