DOCS-1351 with edits

Author: Michael Paik

source/faq/diagnostics.txt

@@ -35,10 +35,10 @@ Does TCP ``keepalive`` time affect MongoDB Deployments?
 If you experience socket errors between clients and servers or between
 members of a sharded cluster or replica set that do not have other
 reasonable causes, check the TCP keepalive value, which Linux systems
-store as the ``tcp_keepalive_time`` value. A common keepalive period
+store as ``tcp_keepalive_time``. A common keepalive period
 is ``7200`` seconds (2 hours); however, different distributions and OS
 X may have different settings. For MongoDB, you will have better
-experiences with shorter keepalive periods, on the order of ``120``
+results with shorter keepalive periods, on the order of ``120``
 seconds (two minutes).
 
 If your MongoDB deployment experiences keepalive-related issues, you
@@ -59,7 +59,7 @@ their own sockets.
 The above methods of setting the TCP keepalive are not persistent; you
 will need to reset the new ``tcp_keepalive_time`` value each time you
 reboot or restart a system. see your operating system's documentation
-for setting the TCP keepalive value persistently.
+for instructions on setting the TCP keepalive value persistently.
 
 .. include:: /includes/fact-tcp-keepalive-windows.rst