Update Set-InboundConnector.md

Author: chrisda

exchange/exchange-ps/exchange/Set-InboundConnector.md

@@ -186,7 +186,7 @@ Accept wildcard characters: False
 The ConnectorType parameter specifies a category for the domains that are serviced by the connector. Valid input for this parameter includes the following values:
 
 - Partner: The connector services domains that are external to your organization.
-- OnPremises: The connector services domains that are used by your on-premises organization. OnPremises connectors are used to grant special rights to an email that matches the connector and additional requirements, such as allowing relaying through the tenant to internet destinations, promoting emails from on-premises or other environments as internal (in a hybrid configuration), or enabling other more complex mail flows.
+- OnPremises: The connector services domains that are used by your on-premises organization. OnPremises connectors grant special rights to an email that matches the connector and additional requirements. For example: allowing relay through the tenant to internet destinations, promoting emails from on-premises or other environments as internal (in a hybrid configuration), or enabling other more complex mail flows.
 
 ```yaml
 Type: TenantConnectorType
@@ -328,13 +328,13 @@ Accept wildcard characters: False
 ```
 
 ### -RequireTls
-The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by the connector.
-
-**Note**: This parameter is only applicable to a Partner connector type.
+The RequireTLS parameter specifies whether to require TLS transmission for all messages that are received by a Partner type connector. Valid values are:
 
 - $true: Reject messages if they aren't sent over TLS. This is the default value
 - $false: Allow messages if they aren't sent over TLS.
 
+**Note**: This parameter applies only to Partner type connectors.
+
 ```yaml
 Type: Boolean
 Parameter Sets: (All)
@@ -349,13 +349,13 @@ Accept wildcard characters: False
 ```
 
 ### -RestrictDomainsToCertificate
-The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the connector.
-
-**Note**: This parameter is only applicable to a Partner connector type.
+The RestrictDomainsToCertificate parameter specifies whether the Subject value of the TLS certificate is checked before messages can use the Partner type connector. Valid values are:
 
 - $true: Mail is allowed to use the connector only if the Subject value of the TLS certificate that the source email server uses to authenticate matches the TlsSenderCertificateName parameter value.
 - $false: The Subject value of the TLS certificate that the source email server uses to authenticate doesn't control whether mail from that source uses the connector. This is the default value.
 
+**Note**: This parameter applies only to Partner type connectors.
+
 ```yaml
 Type: Boolean
 Parameter Sets: (All)
@@ -370,13 +370,13 @@ Accept wildcard characters: False
 ```
 
 ### -RestrictDomainsToIPAddresses
-The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses.
-
-**Note**: This parameter is only applicable to a Partner connector type.
+The RestrictDomainsToIPAddresses parameter specifies whether to reject mail that comes from unknown source IP addresses for Partner type connectors. Valid values are:
 
 - $true: Automatically reject mail from domains that are specified by the SenderDomains parameter if the source IP address isn't also specified by the SenderIPAddress parameter.
 - $false: Don't automatically reject mail from domains that are specified by the SenderDomains parameter based on the source IP address. This is the default value.
 
+**Note**: This parameter applies only to Partner type connectors.
+
 ```yaml
 Type: Boolean
 Parameter Sets: (All)
@@ -407,7 +407,7 @@ Accept wildcard characters: False
 ```
 
 ### -SenderDomains
-The SenderDomains parameter specifies the source domains from which a Partner type connector accepts messages, thereby limiting its scope. A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all its subdomains (for example, `*.contoso.com`). However, you can't embed the wildcard character (for example, `domain.*.contoso.com` is not valid).
+The SenderDomains parameter specifies the source domains that a Partner type connector accepts messages for (limits the scope of a Partner type connector). A valid value is an SMTP domain. Wildcards are supported to indicate a domain and all subdomains (for example, `*.contoso.com`). However, you can't embed the wildcard character (for example, `domain.*.contoso.com` isn't valid).
 
 You can specify multiple domains separated by commas.
 
@@ -425,14 +425,15 @@ Accept wildcard characters: False
 ```
 
 ### -SenderIPAddresses
-The SenderIPAddresses parameter specifies the remote IPv4 IP addresses from which this connector accepts messages.
-
-**Note**: This parameter is only applicable to a Partner connector type and only if [RestrictDomainsToIPAddresses](#-restrictdomainstoipaddresses) is enabled.
+The SenderIPAddresses parameter specifies the source IPV4 IP addresses that the Partner type connector accepts messages from when the value of the RestrictDomainsToIPAddresses parameter is $true. Valid values are:
 
 - Single IP address: For example, 192.168.1.1.
 - Classless InterDomain Routing (CIDR) IP address range: For example, 192.168.0.1/25. Valid subnet mask values are /24 through /32.
+@@ -435,6 +441,8 @@ You can specify multiple IP addresses separated by commas.
 
-You can specify multiple values separated by commas.
+IPv6 addresses are not supported.
+
+**Note**: This parameter applies to Partner type connectors only if the value of the RestrictDomainsToIPAddresses parameter is $true.
 
 ```yaml
 Type: MultiValuedProperty