Update websocket-api.md

Removed stale limit and pointed to Limits page for updated value.
Removed limitation for self-hosted gateway.

Author: dlepow

articles/api-management/websocket-api.md

@@ -114,12 +114,12 @@ For example, the following screenshot shows  recent WebSocket API responses with
 Below are the current restrictions of WebSocket support in API Management:
 
 * WebSocket APIs are not supported yet in the Consumption tier.
-* WebSocket APIs are not supported yet in the [self-hosted gateway](./self-hosted-gateway-overview.md).
-* 200 active connections limit per unit.
 * WebSocket APIs support the following valid buffer types for messages: Close, BinaryFragment, BinaryMessage, UTF8Fragment, and UTF8Message.
 * Currently, the [set-header](set-header-policy.md) policy doesn't support changing certain well-known headers, including `Host` headers, in onHandshake requests.
 * During the TLS handshake with a WebSocket backend, API Management validates that the server certificate is trusted and that its subject name matches the hostname. With HTTP APIs, API Management validates that the certificate is trusted but doesn’t validate that hostname and subject match.
 
+For WebSocket connection limits, see [API Management limits](../azure-resource-manager/management/azure-subscription-service-limits.md#api-management-limits).
+
 ### Unsupported policies
 
 The following policies are not supported by and cannot be applied to the onHandshake operation: