rm feedback

Author: stephmarie17

source/connect/mongoclient.txt

@@ -57,7 +57,7 @@ A standard connection string includes the following components:
      - Optional. Authentication credentials. If you include these, the client
        authenticates the user against the database specified in ``authSource``.
        For more information about the ``authSource`` connection option, 
-       see :ref:`golang-connection-troubleshooting` in the Connection Troubleshooting guide.
+       see the :ref:`golang-connection-troubleshooting` guide.
 
    * - ``host[:port]``
 
@@ -79,6 +79,11 @@ A standard connection string includes the following components:
        :ref:`golang-connection-options` for a full description of
        these options.
 
+.. tip::
+
+   To retrieve a connection string for an Atlas deployment, follow the
+   :ref:`Quick Start guide <golang-connect-to-your-cluster>`.
+
 For more information about creating a connection string, see :manual:`Connection
 Strings </reference/connection-string>` in the MongoDB Server documentation.
 
@@ -95,14 +100,14 @@ To specify your connection URI, pass it to the ``ApplyURI()`` method, which
 returns a new ``ClientOptions`` instance. To set any other options, call the
 relevant helper method from the options package.
 
-.. tip:: Reuse Your Client
+.. tip:: Reuse Your Client with Connection Pools
 
-   We recommend that you reuse your client across sessions and operations. You
-   can use the same ``Client`` instance to perform multiple tasks, instead of
-   creating a new one each time. The ``Client`` type is safe for concurrent use
-   by multiple `goroutines <https://go.dev/tour/concurrency/1>`__. To learn more
-   about how connection pools work in the driver, see the
-   :ref:`golang-connection-pools` guide.
+   We recommend that you reuse your client across sessions and operations by
+   using a connection pool. You can use the same ``Client`` instance to perform
+   multiple tasks, instead of creating a new one each time. The ``Client`` type
+   is safe for concurrent use by multiple `goroutines
+   <https://go.dev/tour/concurrency/1>`__. To learn more about how connection
+   pools work in the driver, see the :ref:`golang-connection-pools` guide.
 
 To learn more about connection options, see the :ref:`Connection Options
 <golang-connection-options>` section. To learn more about creating a client, see
@@ -127,77 +132,24 @@ that the connection is successful:
    :copyable:
    :dedent:
 
-.. tip::
-
-   Follow the :ref:`Quick Start guide <golang-connect-to-your-cluster>`
-   to learn how to retrieve your Atlas connection string.
-
-.. note::
-
-   To learn about connecting to Atlas Serverless, see the
-   :ref:`Serverless Instance Limitations page
-   <atlas-serverless-drivers>` to identify the minimum driver version
-   required.
-
-Other Ways to Connect to MongoDB
---------------------------------
-
-If you are connecting to a single MongoDB server instance or replica set
-that is not hosted on Atlas, see the following sections to learn how to
-connect.
-
-Connect to a MongoDB Server on Your Local Machine
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. include:: /includes/localhost-connection.rst
-
-To test whether you can connect to your server, replace the connection string
-with your localhost connection string in the preceding `code example <go-connection-example-code>`.
-
-Connect to a Replica Set
-~~~~~~~~~~~~~~~~~~~~~~~~
-
-A MongoDB replica set deployment is a group of connected instances that
-store the same set of data. This configuration provides data
-redundancy and high data availability.
-
-To connect to a replica set deployment, specify the hostname and port numbers
-of each instance, separated by commas, and the replica set name as the value
-of the ``replicaSet`` parameter in the connection string. In the following
-example, the hostnames are ``host1``, ``host2``, and ``host3``, and the
-port numbers are all ``27017``. The replica set name is ``myRS``.
-
-.. code-block:: none
-
-   mongodb://host1:27017,host2:27017,host3:27017/?replicaSet=myRS
-
-When connecting to a replica set, the driver takes the following actions by default:
-
-- Discovers all replica set members when given the address of any one member.
-- Dispatches operations to the appropriate member, such as instructions
-  to write against the **primary**.
-
-.. tip::
-
-   You can specify just one host to connect to a replica set.
-   However, to ensure connectivity when the specified host
-   is unavailable, you must provide the full list of hosts.
-
-To learn more about replication in MongoDB, see the :manual:`Replication </replication>` section of Server manual.
+Additional Resources
+--------------------
 
-Direct Connection
-`````````````````
+For more information about the concepts in this guide, see the following
+documentation:
 
-To force operations on the host designated in the connection URI,
-specify the ``directConnection`` option. Direct connections exhibit the
-following behavior:
+- :manual:`Connection Strings </reference/connection-string>` in the Server
+  manual
+- :manual:`Connection String Options </reference/connection-string>` in the
+  Server manual
+- :atlas:`Connect via Drivers </driver-connection/>` in the Atlas documentation
+  and select :guilabel:`Go` from the language dropdown
 
-- They don't support SRV strings.
-- They fail on writes when the specified host is not the **primary**.
-- They require you to specify a :manual:`secondary read preference
-  </core/read-preference/#mongodb-readmode-secondary>` when the
-  specified host isn't the **primary** node.
+API Documentation
+~~~~~~~~~~~~~~~~~
 
-.. note:: Replica Set in Docker
+To learn more about the methods and types discussed in this guide, see the
+following API Documentation:
 
-   .. sharedinclude:: dbx/docker-replica-set.rst
+- `Client <{+api+}/mongo#Client>`__
+- `ClientOptions <{+api+}/options#ClientOptions>`__