Update features.md

Author: jaesoni

articles/application-gateway/features.md

@@ -106,11 +106,9 @@ For more information, see [WebSocket support](application-gateway-websocket.md)
 
 Connection draining helps you achieve graceful removal of backend pool members during planned service updates or problems with backend health. This setting is enabled via the [Backend Setting](configuration-http-settings.md) and is applied to all backend pool members during rule creation. Once enabled, the application gateway ensures all deregistering instances of a backend pool don't receive any new requests while allowing existing requests to complete within a configured time limit. It applies to cases where backend instances are explicitly removed from the backend pool after a configuration change by a user.
 
-The only exception is when requests continue to be proxied to the deregistering instances because of gateway-managed session affinity. 
-
 The connection draining is honored for WebSocket connections as well. Connection draining is invoked for every single update to the gateway. To prevent connection loss to existing members of the backend pool, make sure to enable connection draining.
 
-For information on time limits, see [Backend Settings configuration](configuration-http-settings.md#connection-draining).
+For more details, see [Backend Settings configuration](configuration-http-settings.md#connection-draining).
 
 ## Custom error pages