js feedback

Author: shuangela

source/connect/connection-options.txt

@@ -405,7 +405,7 @@ Close Sockets After Connection
 ------------------------------
 
 If you experience unexpected network behavior or if a MongoDB process
-fails with an error, you may not receive confirmation that the
+fails with an error, you might not receive confirmation that the
 driver correctly closed the corresponding socket.
 
 To make sure that the driver correctly closes the socket in these cases,
@@ -436,7 +436,7 @@ The ``keepAlive`` connection option specifies whether to enable
 :wikipedia:`Transmission Control Protocol (TCP) keepalives
 <Keepalive#TCP_keepalive>` on a TCP socket. If you enable keepalives,
 the driver checks whether the connection is active by sending periodic pings
-to your MongoDB deployment. This functionality only works if your
+to your MongoDB deployment. This functionality works only if your
 operating system supports the ``SO_KEEPALIVE`` socket option.
 
 The ``keepAliveInitialDelay`` option specifies the number of

source/connect/connection-troubleshooting.txt

@@ -370,3 +370,35 @@ Confirm that your firewall exhibits the following behavior:
 
    To learn more about keepalive messages, see the :ref:`keepAlive Connection Option
    <node-faq-keepalive>` section in the Connection Options page.
+
+Connection String Errors for Replica Sets
+-----------------------------------------
+
+The connection string passed to the driver must use exact hostnames for
+the servers, as set in the :manual:`Replica Set Config </reference/replica-configuration/>`.
+Given the following configuration settings for your replica set, in
+order for the replica set discovery and :manual:`failover
+</reference/glossary/#term-failover>` to work, the driver must have access
+to ``server1``, ``server2``, and ``server3``.
+
+.. code-block:: JSON
+
+   {
+     "_id": "testSet",
+     "version": 1,
+     "protocolVersion": 1,
+     "members": [
+       {
+         "_id": 1,
+         "host": "server1:31000"
+       },
+       {
+         "_id": 2,
+         "host": "server2:31001"
+       },
+       {
+         "_id": 3,
+         "host": "server3:31002"
+       }
+     ]
+   }

source/crud/read-write-pref.txt

@@ -40,38 +40,6 @@ concern level set for the client.
 These options allow you to customize the causal consistency and availability of the data
 in your replica sets.
 
-Connection Strings for Replica Sets
------------------------------------
-
-The connection string passed to the driver must use exact hostnames for
-the servers as set in the :manual:`Replica Set Config </reference/replica-configuration/>`.
-Given the following configuration settings for your Replica Set, in
-order for the Replica Set discovery and :manual:`failover
-</reference/glossary/#term-failover>` to work, the driver must have access
-to ``server1``, ``server2``, and ``server3``.
-
-.. code-block:: JSON
-
-   {
-     "_id": "testSet",
-     "version": 1,
-     "protocolVersion": 1,
-     "members": [
-       {
-         "_id": 1,
-         "host": "server1:31000"
-       },
-       {
-         "_id": 2,
-         "host": "server2:31001"
-       },
-       {
-         "_id": 3,
-         "host": "server3:31002"
-       }
-     ]
-   }
-
 Write Concern
 -------------