DOC-4037 implemented PR feedback

Author: andy-stark-redis

content/develop/connect/clients/client-side-caching.md

@@ -36,7 +36,7 @@ can satisfy the read requests from the cache instead of the database:
 {{< image filename="images/csc/CSCWithCache.drawio.svg" >}}
 
 Accessing the cache is much faster than communicating with the database over the
-network and it reduces network traffic. Client-side cacheing reduces
+network and it reduces network traffic. Client-side caching reduces
 the load on the database server, so you may be able to run it using less hardware
 resources.
 
@@ -94,7 +94,7 @@ server activity if client-side caching is working correctly.
 
 ## What data gets cached for a command?
 
-Broadly speaking, the data from the *specific response* to a command invocation
+Broadly speaking, the data from the specific response to a command invocation
 gets cached after it is used for the first time. Subsets of that data
 or values calculated from it are retrieved from the server as usual and
 then cached separately. For example:

content/develop/connect/clients/java/jedis.md

@@ -198,7 +198,7 @@ public class Main {
 
 ## Connect using client-side caching
 
-*Client-side caching* is a technique to reduce network traffic between
+Client-side caching is a technique to reduce network traffic between
 the client and server, resulting in better performance. See
 [Client-side caching introduction]({{< relref "/develop/connect/clients/client-side-caching" >}})
 for more information about how client-side caching works and how to use it effectively.

content/develop/connect/clients/python/redis-py.md

@@ -121,7 +121,7 @@ For more information, see [redis-py TLS examples](https://redis-py.readthedocs.i
 
 ## Connect using client-side caching
 
-*Client-side caching* is a technique to reduce network traffic between
+Client-side caching is a technique to reduce network traffic between
 the client and server, resulting in better performance. See
 [Client-side caching introduction]({{< relref "/develop/connect/clients/client-side-caching" >}})
 for more information about how client-side caching works and how to use it effectively.
@@ -174,7 +174,7 @@ If you run the code again with `cache_config` uncommented, you will see
 1723110248.713607 [...] "GET" "city"
 ```
 
-This shows that the first `get("city")` call contacted the server but the second
+The first `get("city")` call contacted the server but the second
 call was satisfied by the cache.
 
 ### Removing items from the cache