Update connection opts (#422)

* wip

* wip

* revert image

* csot not implemented

* consistent wording

* no change to conneciton string image

* ref wording

* csot not implemented

* copy review

* feedback

Author: terakilobyte

source/fundamentals/authentication.txt

@@ -1,3 +1,5 @@
+.. _node-authentication-mechanisms:
+
 ==============
 Authentication
 ==============
@@ -26,9 +28,9 @@ MongoDB Community Edition which includes:
 - ``MONGODB-AWS``
 - ``X.509``
 
-The :doc:`Enterprise Authentication Mechanisms 
-</fundamentals/authentication/enterprise-mechanisms>` guide contains sample 
-connection code using authentication mechanisms available only in MongoDB 
+The :doc:`Enterprise Authentication Mechanisms
+</fundamentals/authentication/enterprise-mechanisms>` guide contains sample
+connection code using authentication mechanisms available only in MongoDB
 Enterprise Edition which includes:
 
 - ``Kerberos (GSSAPI/SSPI)``

source/fundamentals/authentication/mechanisms.txt

@@ -1,5 +1,3 @@
-.. _node-authentication-mechanisms:
-
 =========================
 Authentication Mechanisms
 =========================
@@ -124,7 +122,7 @@ in the following sample code.
    SCRAM </release-notes/3.0-scram/>`, any ``MONGODB-CR`` user
    authentication requests fail.
 
-.. _mongodb-aws: 
+.. _mongodb-aws:
 
 ``MONGODB-AWS``
 ---------------
@@ -144,7 +142,7 @@ user. If you do not already have the `AWS signature library
    npm install aws4
 
 To connect to a MongoDB instance with ``MONGODB-AWS`` authentication
-enabled, specify the ``MONGODB-AWS`` authentication mechanism. 
+enabled, specify the ``MONGODB-AWS`` authentication mechanism.
 
 The driver checks for your credentials in the following sources in order:
 
@@ -163,19 +161,19 @@ The driver checks for your credentials in the following sources in order:
       add your ``AWS_ACCESS_KEY_ID`` and ``AWS_SECRET_ACCESS_KEY``
       credentials to your environment variables. If your AWS
       login requires an ``AWS_SESSION_TOKEN``, add it to your
-      environment variables as well. 
+      environment variables as well.
 
       The following code shows an example of specifying the ``MONGODB-AWS``
       authentication mechanism with environment variables:
 
       .. note::
-      
+
          You don't need to specify these credentials in your connection URI
          because the driver automatically retrieves them when you attempt
          to connect.
 
       .. literalinclude:: /code-snippets/authentication/aws-env-variable.js
-         :language: javascript 
+         :language: javascript
 
    .. tab:: Connection String
       :tabid: connection string
@@ -189,13 +187,13 @@ The driver checks for your credentials in the following sources in order:
       authentication mechanism and credentials with a connection string:
 
       .. important::
-         
+
          Always **URI encode** the username and certificate file path using the
          ``encodeURIComponent`` method to ensure they are correctly parsed.
 
       .. literalinclude:: /code-snippets/authentication/aws.js
-         :language: javascript  
-   
+         :language: javascript
+
 ``X.509``
 ---------