Update cache-best-practices-connection.md

Add motivation for server side timeout

Author: shpathak-msft

articles/azure-cache-for-redis/cache-best-practices-connection.md

@@ -85,10 +85,10 @@ Apply design patterns for resiliency. For more information, see [How do I make m
 
 ## Idle timeout
 
-Azure Cache for Redis currently has a 10-minute idle timeout for connections, so the idle timeout setting in your client application should be less than 10 minutes. Most common client libraries have a configuration setting that allows client libraries to send Redis `PING` commands to a Redis server automatically and periodically. However, when using client libraries without this type of setting, customer applications themselves are responsible for keeping the connection alive.
+Azure Cache for Redis currently has a 10-minute idle timeout for connections, so the idle timeout setting in your client application should be less than 10 minutes. This idle timeout for connections helps automatically clean up connection leaks and most common client libraries have a configuration setting that allows client libraries to send Redis `PING` commands to a Redis server periodically. However, when using client libraries without this type of setting, customer applications themselves are responsible for keeping the connection alive.
 
 ## Next steps
 
 - [Best practices for development](cache-best-practices-development.md)
 - [Azure Cache for Redis development FAQ](cache-development-faq.yml)
-- [Failover and patching](cache-failover.md)
+- [Failover and patching](cache-failover.md)