JS feedback

Author: mcmorisi

source/connect/connection-options/server-selection.txt

@@ -1,3 +1,5 @@
+.. _csharp-server-selection:
+
 ==========================
 Customize Server Selection
 ==========================
@@ -24,7 +26,7 @@ customize this algorithm to choose the server that works best for your applicati
 
 .. important::
 
-   Customizing the server-selection algorithm can have unintended consequences,
+   Customizing the server selection algorithm might have unintended consequences,
    such as degraded read or write performance.
 
 Default Algorithm
@@ -33,46 +35,45 @@ Default Algorithm
 When the {+driver-short+} executes a read operation, it performs the following steps,
 in order, to select a MongoDB deployment:
 
-1. From the list of known servers, the {+driver-short+} selects all servers
-   that match the active read preference.
+1. Selects all servers that match the active read preference from the list of known servers.
 
-#. If at least one readable server exists, the {+driver-short+} calls the user-defined
+#. If at least one readable server exists, the driver calls the user-defined
    server-selector function and passes in the list from the previous step.
 
-#. The {+driver-short+} applies the ``LocalThreshold`` connection setting to the list of
+#. Applies the ``LocalThreshold`` connection setting to the list of
    servers returned from the function.
 
-#. The {+driver-short+} selects a server at random from the servers still on the list and
+#. Selects a server at random from the servers still on the list and
    executes the operation against this server.
 
 When the {+driver-short+} executes a write operation, it begins by selecting all writeable
 servers, not just those that match the active read preference. The remaining steps are
 identical.
 
-To learn more about the default server-selection algorithm, which the driver follows
-when you don't specify any custom server-selection logic, see
+To learn more about the default server selection algorithm, which the driver follows
+when you don't specify any custom server selection logic, see
 :manual:`Server Selection Algorithm </core/read-preference-mechanics/>` in the
-MongoDB Server manual.
+{+mdb-server+} manual.
 
 .. _csharp-server-selection-algorithm:
 
 Specifying Other Server Selection Algorithms
 --------------------------------------------
 
-You can specify different server-selection logic by passing an instance of a server selector
+You can specify different server selection logic by passing an instance of a server selector
 class to the ``PreServerSelector`` or ``PostServerSelector`` property of the ``ClusterConfigurator``. The
 ``PreServerSelector`` property specifies a server selector that runs before the
 standard server selection logic runs, while the ``PostServerSelector`` property
 specifies a server selector that runs after standard server selection logic runs. You can
 then pass your ``ClusterConfigurator`` instance to the ``MongoClientSettings`` object when you create a
-``MongoClient`` instance to apply your custom server-selection logic.
+``MongoClient`` instance to apply your custom server selection logic.
 
 The following table lists the different types of server selectors you can pass to the
 ``ClusterConfigurator`` property:
 
 .. list-table::
    :header-rows: 1
-   :widths: 30 70
+   :widths: 40 60
 
    * - Server Selector
      - Description
@@ -113,7 +114,7 @@ To learn more about the different server selector classes, see the
 Implementing Custom Server Selection Logic
 ------------------------------------------
 
-You can also implement your own custom server-selection logic by creating a class that
+You can implement your own custom server selection logic by creating a class that
 inherits from the ``IServerSelector`` interface and overrides the
 ``SelectServers()`` method. The following example shows a simple custom server
 selection class that selects servers with a ``ServerType`` of
@@ -153,7 +154,7 @@ in your connection URI:
 
    * - ``ReadPreference``
      - | The client's default read-preference settings. ``MaxStaleness`` represents the
-       | longest replication lag (in wall-clock time) that a secondary can experience and
+       | longest replication lag (in real time) that a secondary can experience and
        | still be eligible for server selection. Specifying ``-1`` means no maximum.
        | See :ref:`read preference <read-preference>` for more information.
        |

source/includes/troubleshooting/server-selection-timeout.rst

@@ -47,7 +47,7 @@ The error message consists of multiple parts:
    The following heartbeat exceptions are common:
 
    * ``No connection could be made because the target machine actively
-     refused it``: The driver cannot see this cluster node. This can be
+     refused it``: The driver cannot see this cluster node. This might be
      because the cluster node has crashed, a firewall is preventing
      network traffic from reaching the cluster node or port, or some other
      network error is preventing traffic from being successfully routed to
@@ -57,7 +57,7 @@ The error message consists of multiple parts:
      network error, misconfigured firewall, or other network issue. To
      address this exception, ensure that all cluster nodes are reachable.
      This error commonly occurs when the client machine’s IP address is
-     not configured in the Atlas IPs Access List, which can be found under
+     not configured in the Atlas IPs Access List, which you can find under
      the :guilabel:`Network Access` tab for your Atlas Project.
    * ``The remote certificate is invalid according to the validation
      procedure``: This error typically indicates a TLS/SSL-related problem