Merge pull request #195989 from GitaraniSharma-MSFT/patch-40

(AzureCXP) MicrosoftDocs/azure-docs#91761

Author: PRMerger5

articles/frontdoor/rules-match-conditions.md

@@ -499,7 +499,7 @@ The **remote address** match condition identifies requests based on the requeste
 * When you specify multiple IP addresses and IP address blocks, 'OR' logic is applied.
     * **IPv4 example**: if you add two IP addresses `1.2.3.4` and `10.20.30.40`, the condition is matched for any requests that arrive from either address 1.2.3.4 or 10.20.30.40.
     * **IPv6 example**: if you add two IP addresses `1:2:3:4:5:6:7:8` and `10:20:30:40:50:60:70:80`, the condition is matched for any requests that arrive from either address 1:2:3:4:5:6:7:8 or 10:20:30:40:50:60:70:80.
-* The remote address represents the original client IP that is either from the network connection or typically the X-Forwarded-For request header if the user is behind a proxy. Use the [socket address](#socket-address) match condition if you need to match based on the TCP request's IP address.
+* The remote address represents the original client IP that is either from the network connection or typically the X-Forwarded-For request header if the user is behind a proxy. Use the [socket address](#socket-address) match condition (available in Standard/Premium), if you need to match based on the TCP request's IP address.
 
 ### Properties