DOC-5064 removed incorrect tcpKeepAlive section

Author: andy-stark-redis

content/develop/clients/jedis/produsage.md

@@ -29,7 +29,6 @@ progress in implementing the recommendations.
     {{< checklist-item "#client-side-caching" >}}Client-side caching{{< /checklist-item >}}
     {{< checklist-item "#timeouts" >}}Timeouts{{< /checklist-item >}}
     {{< checklist-item "#health-checks" >}}Health checks{{< /checklist-item >}}
-    {{< checklist-item "#tcp-keepalive" >}}TCP keepalive{{< /checklist-item >}}
     {{< checklist-item "#exception-handling" >}}Exception handling{{< /checklist-item >}}
     {{< checklist-item "#dns-cache-and-redis" >}}DNS cache and Redis{{< /checklist-item >}}
 {{< /checklist >}}
@@ -103,27 +102,6 @@ try (Jedis jedis = jedisPool.getResource()) {
 Health checks help to detect problems as soon as possible without
 waiting for a user to report them.
 
-### TCP keepalive
-
-[TCP keepalive](https://en.wikipedia.org/wiki/Keepalive) is a technique
-where TCP packets are periodically sent on an otherwise idle connection
-to check that it is still working. You can enable TCP keepalive for a
-connection using an option on the connection config builder:
-
-```java
-JedisClientConfig clientConfig = DefaultJedisClientConfig.builder()
-  .connectionTimeoutMillis(2000)
-  .socketTimeoutMillis(2000)
-  .tcpKeepAlive(true)
-  .build();
-
-JedisPool pool = new JedisPool(poolConfig, "redis-host", clientConfig);
-```
-
-TCP keepalive can be especially useful to detect when unused connections
-in a [connection pool](#connection-pooling) have been dropped due to
-inactivity.
-
 ### Exception handling
 
 Redis handles many errors using return values from commands, but there