DOCSP-13550 Update hostname inputs in connection form

kanchana-mongodb · kanchana-mongodb · commit 018835afb861 · 2021-01-20T13:51:11.000-08:00
diff --git a/source/includes/steps-starting-vsce-individual-fields.yaml b/source/includes/steps-starting-vsce-individual-fields.yaml
@@ -54,8 +54,7 @@ content: |
      For more information, see the **Paste Connection String** tab in 
      :ref:`vsce-connect-task`.
 
-  The :guilabel:`General` tab contains the following connection
-  field options:
+  The :guilabel:`General` tab contains the following options:
 
   .. list-table:: 
      :header-rows: 1
@@ -64,69 +63,116 @@ content: |
      * - Option
        - Description
 
-     * - :guilabel:`Hostname`
-       - Hostname of the machine where the deployment is
-         running.
+     * - :guilabel:`Connection Type`
+       - Type of connection. Select your connection type from the tabs 
+         below for specific instructions for defining that connection 
+         type:
+       
+         .. tabs:: 
+
+            .. tab:: Standalone
+               :tabid: standalone
+
+               For a :manual:`Standalone </reference/connection-string/#dns-seedlist-connection-format>`, 
+               specify the following: 
+
+               - :guilabel:`Hostname` of the machine where the 
+                 deployment is running. 
+         
+                 If you are running your deployment locally, this value 
+                 is ``localhost``. If you are connecting to an 
+                 |service| cluster, you can get your hostname from your 
+                 cluster detail view in |service|.
+
+                 If you are not sure of your hostname, contact your 
+                 Database Administrator for information.
+
+               - :guilabel:`Port` on which the deployment is running.
+                 
+                 By default, a standalone deployment operates on port 
+                 ``27017``. For more information on the default ports 
+                 MongoDB operates on, see :manual:`Default MongoDB Port 
+                 </reference/default-mongodb-port/>`.
+
+                 If you are not sure of the port where your deployment 
+                 operates, contact your Database Administrator for 
+                 information.
+
+               Click :icon-fa4:`plus` to specify additional hostnames 
+               and associated ports.
+
+            .. tab:: Replica Set 
+               :tabid: replicaset
+
+               For a :manual:`replica set </reference/connection-string/#dns-seedlist-connection-format>`, 
+               specify the following: 
+               
+               - :guilabel:`Hostname` of the machine where the 
+                 deployment is running.
          
-         If you are running your deployment locally, this value is
-         ``localhost``. If you are connecting to an |service| cluster,
-         you can get your hostname from your cluster detail view in
-         |service|.
+                 If you are running your deployment locally, this value 
+                 is ``localhost``. If you are connecting to an 
+                 |service| cluster, you can get your hostname from your 
+                 cluster detail view in |service|.
+
+                 If you are not sure of your hostname, contact your 
+                 Database Administrator for information.
+
+               - :guilabel:`Port` on which the deployment is running.
+                 
+                 For information on the default ports MongoDB operates 
+                 on, see :manual:`Default MongoDB Port 
+                 </reference/default-mongodb-port/>`.
 
-         If you are not sure of your hostname, contact your Database
-         Administrator for information.
+                 If you are not sure of the port where your deployment 
+                 operates, contact your Database Administrator for 
+                 information.
 
-     * - :guilabel:`Port`
-       - Port on which the deployment is running. Not required if
-         you are using an :guilabel:`SRV Record` to connect to
-         your MongoDB deployment.
+               - *Optional*. :guilabel:`Replica Set Name` as specified 
+                 in the :manual:`replica set configuration </reference/replica-configuration/>`. 
 
-         By default, a standalone deployment operates on port ``27017``.
-         If you are connecting to a replica set, your port may also be
-         ``27018`` or ``27019``. For more information on the default
-         ports MongoDB operates on, see :manual:`Default MongoDB Port
-         </reference/default-mongodb-port/>`.
+               Click :icon-fa4:`plus` to specify additional hostnames 
+               and associated ports.
 
-         If you are not sure of the port where your deployment operates,
-         contact your Database Administrator for information.
+            .. tab:: SRV Record 
+               :tabid: srvrecord 
 
-     * - :guilabel:`SRV Record`
-       - Indicates whether the provided :guilabel:`Hostname`
-         is an :manual:`SRV Record
-         </reference/connection-string/#dns-seedlist-connection-format>`.
-         If this toggle is enabled, you do not need to specify a port.
+               For an :manual:`SRV Record </reference/connection-string/#dns-seedlist-connection-format>`, 
+               specify the :guilabel:`Hostname`. You do not need to 
+               specify a port.
 
-         .. note::
+               .. note::
 
-           You can only use SRV connection strings to connect to
-           deployments running MongoDB 3.6 and later.
+                  You can only use SRV connection strings to connect to 
+                  deployments running MongoDB 3.6 and later.
 
-         SRV connection strings have a prefix of ``mongodb+srv:``. If
-         you are using an SRV connection string, you do not need to
-         include ``mongodb+srv`` in your :guilabel:`Hostname`.
+               SRV connection strings have a prefix of 
+               ``mongodb+srv:``. If you are using an SRV connection 
+               string, you do not need to include ``mongodb+srv`` in 
+               your :guilabel:`Hostname`.
 
-         .. example::
+               .. example::
 
-             If the following is your SRV connection string for your
-             MongoDB deployment:
+                  If the following is your SRV connection string for 
+                  your MongoDB deployment:
 
-             .. code-block:: shell
-                 :copyable: false
+                  .. code-block:: shell
+                     :copyable: false
 
-                 mongodb+srv://<username>:<password>@gettingstarted-7q2cs.mongodb.net/test
+                     mongodb+srv://<username>:<password>@gettingstarted-7q2cs.mongodb.net/test
 
-             Then, in |vsce|, you would specify your
-             :guilabel:`Hostname` as:
+                  Then, in |vsce|, you would specify your 
+                  :guilabel:`Hostname` as:
 
-             .. code-block:: shell
-                 :copyable: false
+                  .. code-block:: shell
+                     :copyable: false
 
-                 gettingstarted-7q2cs.mongodb.net
+                     gettingstarted-7q2cs.mongodb.net
 
      * - :guilabel:`Authentication`
-       - Authentication to use if the deployment
-         requires authentication. |service| clusters use
-         :guilabel:`Username / Password` authentication.
+       - Authentication to use if the deployment requires 
+         authentication. |service| clusters use :guilabel:`Username 
+         / Password` authentication.
          
          Select your authentication method from the tabs below for
          specific instructions:
@@ -382,59 +428,44 @@ content: |
            tunnel. |vsce| cannot establish a connection
            to multiple servers across the same SSH tunnel.
 ---
-title: "Specify replica set and security connection options."
+title: "Specify read preference in the :guilabel:`Advanced` tab."
 level: 4
 optional: true
 ref: connect-additional-options
 content: |
-  You can specify the following security connection options:
+  You can select the :guilabel:`Read Preference`, which specifies how 
+  |vsce| directs read operations. Options are:
 
   .. list-table::
      :header-rows: 1
+     :widths: 20 50
 
-     * - Option
+     * - Read Preference Mode
        - Description
-
-     * - :guilabel:`Replica Set Name`
-       - If your MongoDB deployment is a replica set, specify the
-         replica set name. Not required if you specify your replica
-         set :guilabel:`Hostname` as an :guilabel:`SRV Record`.
-
-     * - :guilabel:`Read Preference`
-       - Specifies how |vsce| directs read operations. Options are:
-
-         .. list-table::
-            :header-rows: 1
-            :widths: 20 50
-
-            * - Read Preference Mode
-              - Description
-
-            * - ``primary``
-              - Default mode. All operations read from the current 
-                replica set primary.
-
-            * - ``primaryPreferred``
-              - In most situations, operations read from the primary but
-                if it is unavailable, operations read from secondary
-                members.
-
-            * - ``secondary``
-              - All operations read from the secondary members of the
-                replica set.
-
-            * - ``secondaryPreferred``
-              - In most situations, operations read from secondary
-                members but if no secondary members are available,
-                operations read from the primary.
-
-            * - ``nearest``
-              - Operations read from member of the replica
-                set with the least network latency, irrespective of the 
-                member's type.
+       
+     * - :guilabel:`Primary`
+       - Default mode. All operations read from the current replica set 
+         primary.
+
+     * - :guilabel:`Primary Preferred`
+       - In most situations, operations read from the primary but if it 
+         is unavailable, operations read from secondary members.
+
+     * - :guilabel:`Secondary`
+       - All operations read from the secondary members of the replica 
+         set.
+
+     * - :guilabel:`Secondary Preferred`
+       - In most situations, operations read from secondary members but 
+         if no secondary members are available, operations read from 
+         the primary.
+
+     * - :guilabel:`Nearest`
+       - Operations read from member of the replica set with the least 
+         network latency, irrespective of the member's type.
          
-         To learn more about read preferences, see
-         :manual:`Read Preference </core/read-preference/>`.
+  If omitted, defaults to :guilabel:`Primary`. To learn more about read 
+  preferences, see :manual:`Read Preference </core/read-preference/>`. 
 
 ---
 ref: vsce-click-connect
