DOCSP-24594 copy edits

Author: ltran-mdb2

source/connect/advanced-connection-options/advanced-connection.txt

@@ -78,14 +78,6 @@ Procedure
                read preference option. 
              - Any specified tag sets. 
 
-      The following screenshot shows the :guilabel:`Advanced`
-      tab configured with the read preference of :guilabel:`Secondary
-      Preferred`. 
-
-      .. figure:: /images/authentication/secondary-preferred.png
-         :figwidth: 662px
-         :alt: Screenshot of Compass configured to connect with read preference of secondary preferred
-
       .. seealso::
 
          - :manual:`Read Preferrence </core/read-preference/#read-preference>`.
@@ -121,3 +113,16 @@ Procedure
 .. seealso::
 
    To disconnect from your deployment, see :ref:`<disconnect-tab>`. 
+
+Example
+-------
+
+The following screenshot shows the :guilabel:`Advanced`
+tab configured with the read preference of :guilabel:`Secondary
+Preferred`. The :guilabel:`Secondary
+Preferred` read pereference helps avoid queries overloading the primary
+node. 
+
+.. figure:: /images/authentication/secondary-preferred.png
+   :figwidth: 662px
+   :alt: Screenshot of Compass configured to connect with read preference of secondary preferred

source/connect/advanced-connection-options/authentication-connection.txt

@@ -266,19 +266,30 @@ Procedure
 
       - (Optional) AWS Session Token
 
-      The following screenshot shows the :guilabel:`Authentication`
-      tab configured for username and password authentication with
-      SCRAM-SHA-256. 
-
-      .. figure:: /images/authentication/authentication-configuration.png
-         :figwidth: 662px
-         :alt: Screenshot of Compass configured to authenticate with username and password
-
    .. step:: (Optional) For advanced connection configuration options, click the :ref:`Advanced <advanced-connection-tab>` tab.
 
    .. step:: Click Connect.
 
-
 .. seealso::
 
    To disconnect from your deployment, see :ref:`<disconnect-tab>`.
+
+Example
+-------
+
+The following screenshot shows the :guilabel:`Authentication`
+tab configured for username and password authentication with
+SCRAM-SHA-256. 
+
+.. figure:: /images/authentication/authentication-configuration.png
+   :figwidth: 662px
+   :alt: Screenshot of Compass configured to authenticate with username
+   and password
+   
+Alternatively, the following screenshot shows the
+:guilabel:`Authentication` tab configured for :manual:`LDAP
+</core/security-ldap-external/>` authentication.  
+
+.. figure:: /images/authentication/ldap-configuration.png
+   :figwidth: 662px
+   :alt: Screenshot of Compass configured to authenticate with LDAP

source/connect/advanced-connection-options/general-connection.txt

@@ -60,7 +60,7 @@ Procedure
 
                 .. note::
 
-                   If you use the Standard Connection String Format to
+                   If you use the standard connection string format to
                    connect to an `Atlas
                    <https://www.mongodb.com/cloud/atlas>`__ deployment,
                    you must turn on TLS/SSL in the
@@ -99,16 +99,19 @@ Procedure
             of a replica set, your write operations fail because it is not the 
             primary member.
 
-      The following screenshot shows the :guilabel:`General` tab
-      configured for an Atlas cluster. 
-
-      .. figure:: /images/authentication/new-atlas-connection.png
-         :alt: Screenshot of Compass configured to connect to an example Atlas cluster
-
    .. step:: (Optional) For advanced connection configuration options, click the :ref:`Advanced <advanced-connection-tab>` tab.
 
    .. step:: Click Connect.
 
 .. seealso::
 
    To disconnect from your deployment, see :ref:`<disconnect-tab>`. 
+
+Example
+-------
+
+The following screenshot shows the :guilabel:`General` tab
+configured for an Atlas cluster. 
+
+.. figure:: /images/authentication/new-atlas-connection.png
+   :alt: Screenshot of Compass configured to connect to an example Atlas cluster

source/connect/advanced-connection-options/tls-ssl-connection.txt

@@ -107,13 +107,6 @@ Procedure
          Enabling ``tlsInsecure``, ``tlsAllowInvalidHostnames``, and 
          ``tlsAllowInvalidCertificates`` may cause a security
          vulnerabilty. 
-         
-      The following screenshot shows the :guilabel:`TLS /
-      SSL` tab configured for a cluster with TLS/SSL enabled.  
-
-      .. figure:: /images/authentication/tls-ssl-configuration.png
-         :figwidth: 662px
-         :alt: Screenshot of Compass configured to connect to an example cluster with TLS/SSL
 
    .. step:: (Optional) For advanced connection configuration options, click the :ref:`Advanced <advanced-connection-tab>` tab.
 
@@ -122,3 +115,13 @@ Procedure
 .. seealso::
 
    To disconnect from your deployment, see :ref:`<disconnect-tab>`.
+
+Example
+-------
+
+The following screenshot shows the :guilabel:`TLS /
+SSL` tab configured for a cluster with TLS/SSL enabled.  
+
+.. figure:: /images/authentication/tls-ssl-configuration.png
+   :figwidth: 662px
+   :alt: Screenshot of Compass configured to connect to an example cluster with TLS/SSL