Merge pull request #195276 from carlost-MSFT/patch-24

Update vpn-gateway-troubleshoot-site-to-site-cannot-connect.md

Author: PRMerger4

articles/vpn-gateway/vpn-gateway-troubleshoot-site-to-site-cannot-connect.md

@@ -91,8 +91,8 @@ If the Internet-facing IP address of the VPN device is included in the **Local n
 
     `https://<YourVirtualNetworkGatewayIP>:8081/healthprobe`
 
-> [!NOTE]
-> For Active/Acive Gateways use the following to check the second public IP: https://<YourVirtualNetworkGatewayIP2>:8083/healthprobe
+    _For Active/Acive gateways use the following to check the second public IP:_ <br>
+    `https://<YourVirtualNetworkGatewayIP2>:8083/healthprobe`
 
 2. Click through the certificate warning.
 3. If you receive a response, the VPN gateway is considered healthy. If you don't receive a response, the gateway might not be healthy or an NSG on the gateway subnet is causing the problem. The following text is a sample response: