DOCS 23751 making tag set terminology consistent (#1518) (#1523)

* DOCS-23751 making tag set terminology consistent with Drivers

* DOCS-23751 making tag set terminology consistent with Drivers

* DOCS-23751 making tag set terminology consistent with Drivers

* DOCS-23751 taking out ie

* DOCS-23751 small fixes

Author: ltran-mdb

source/core/read-preference-tags.txt

@@ -2,9 +2,9 @@
 
 .. _replica-set-read-preference-tag-sets:
 
-========================
-Read Preference Tag Sets
-========================
+=============================
+Read Preference Tag Set Lists
+=============================
 
 .. default-domain:: mongodb
 
@@ -15,8 +15,8 @@ Read Preference Tag Sets
    :class: singlecol
 
 If a replica set member or members are associated with
-:rsconf:`~members[n].tags`, you can specify a tag set (array of tag
-specification documents) in the read preference to target those members.
+:rsconf:`~members[n].tags`, you can specify a tag set list (array of tag
+sets) in the read preference to target those members.
 
 To :ref:`configure <replica-set-configuration-document>` a member with
 tags, set :rsconf:`members[n].tags` to a document that contains the tag
@@ -27,9 +27,9 @@ name and value pairs. The value of the tags must be a string.
 
    { "<tag1>": "<string1>", "<tag2>": "<string2>",... }
 
-Then, you can include a tag set in the read preference to target tagged
-members. A tag set is an array of tag specification documents, where
-each tag specification document contains one or more tag/value pairs.
+Then, you can include a tag set list in the read preference to target
+tagged members. A tag set list is an array of tag sets, where each 
+tag set contains one or more tag/value pairs.
 
 .. code-block:: javascript
    :copyable: false
@@ -46,8 +46,8 @@ For example, if a secondary member has the following
 
    { "region": "South", "datacenter": "A" }
 
-Then, the following tags sets can direct read operations to the aforementioned
-secondary (or other members with the same tags):
+Then, the following tag set lists can direct read operations to the 
+aforementioned secondary (or other members with the same tags):
 
 .. code-block:: javascript
    :copyable: false
@@ -65,21 +65,20 @@ secondary (or other members with the same tags):
 Order of Tag Matching
 ---------------------
 
-If the tag set lists multiple documents, MongoDB tries each document in
-succession until a match is found. Once a match is found, that tag
-specification document is used to find all eligible matching members,
-and the remaining tag specification documents are ignored. If no
-members match any of the tag specification documents, the read
-operation returns with an error.
+If the tag set list contains multiple documents, MongoDB tries each 
+document in succession until a match is found. Once a match is found,
+that tag set is used to find all eligible matching members, and the 
+remaining tag sets are ignored. If no members match any of the tag 
+sets, the read operation returns with an error.
 
 .. tip::
 
    To avoid an error if no members match any of the tag specifications,
    you can add an empty document ``{ }`` as the last element of the tag
-   set to read from any eligible member.
+   set list to read from any eligible member.
 
-For example, consider the following tag set with three tag
-specification documents:
+For example, consider the following tag set list with three tag
+sets:
 
 .. code-block:: javascript
    :copyable: false
@@ -95,9 +94,8 @@ First, MongoDB tries to find members tagged with both ``"region":
    { "region": "South", "datacenter": "A" }
 
 
-- If a member is found, the remaining tag specification documents are
-  not considered. Instead, MongoDB uses this tag specification document
-  to find all eligible members.
+- If a member is found, the remaining tag sets are not considered. 
+  Instead, MongoDB uses this tag set to find all eligible members.
 
 - Else, MongoDB tries to find members with the tags specified in the
   second document
@@ -107,9 +105,8 @@ First, MongoDB tries to find members tagged with both ``"region":
 
      { "rack": "rack-1" }
 
-  - If a member is found tagged, the remaining tag specification
-    document is not considered. Instead, MongoDB uses this tag
-    specification document to find all eligible members.
+  - If a member is found tagged, the remaining tag set is not considered.
+    Instead, MongoDB uses this tag set to find all eligible members.
 
   - Else, the third document is considered. 
 
@@ -120,13 +117,13 @@ First, MongoDB tries to find members tagged with both ``"region":
 
     The empty document matches any eligible member.
 
-Tag Set and Read Preference Modes
----------------------------------
+Tag Set List and Read Preference Modes
+--------------------------------------
 
 Tags are not compatible with mode :readmode:`primary`, and in general,
 only apply when :ref:`selecting <replica-set-read-preference-behavior-member-selection>`
 a :term:`secondary` member of a set for a read operation. However, the
-:readmode:`nearest` read mode, when combined with a tag set, selects
+:readmode:`nearest` read mode, when combined with a tag set list, selects
 the matching member with the lowest network latency. This member may be a
 primary or secondary.
 
@@ -138,22 +135,22 @@ primary or secondary.
      - Notes
 
    * - :readmode:`primaryPreferred`
-     - Specified tag set only applies if selecting eligible secondaries.
+     - Specified tag set list only applies if selecting eligible secondaries.
 
    * - :readmode:`secondary`
-     - Specified tag set always applies.
+     - Specified tag set list always applies.
 
    * - :readmode:`secondaryPreferred`
-     -  Specified tag set only applies if selecting eligible secondaries.
+     -  Specified tag set list only applies if selecting eligible secondaries.
 
    * - :readmode:`nearest`
 
-     -  Specified tag set applies whether selecting either primary or eligible secondaries.
+     -  Specified tag set list applies whether selecting either primary or eligible secondaries.
 
 For information on the interaction between the :ref:`modes
-<replica-set-read-preference-modes>` and tag sets, refer to the
+<replica-set-read-preference-modes>` and tag set lists, refer to the
 :ref:`specific read preference mode documentation
 <replica-set-read-preference-modes>`.
 
-For information on configuring tag sets, see the
+For information on configuring tag set lists, see the
 :doc:`/tutorial/configure-replica-set-tag-sets` tutorial.

source/core/read-preference.txt

@@ -19,7 +19,7 @@ Read Preference
 .. include:: /includes/introduction-read-preference.rst
 
 Read preference consists of the :ref:`read preference mode
-<read-pref-modes-summary>` and optionally, a :ref:`tag set
+<read-pref-modes-summary>` and optionally, a :ref:`tag set list
 <replica-set-read-preference-tag-sets>`, the :ref:`maxStalenessSeconds
 <replica-set-read-preference-max-staleness>` option, and the
 :ref:`hedged read <read-preference-hedged-read>` option. :ref:`Hedged read
@@ -85,10 +85,10 @@ Read Preference Modes
    error or throw an exception.
 
    The :readmode:`primary` read preference mode is not compatible with
-   read preference modes that use :ref:`tag sets
+   read preference modes that use :ref:`tag set lists
    <replica-set-read-preference-tag-sets>` or :ref:`maxStalenessSeconds 
    <replica-set-read-preference-max-staleness>`. 
-   If you specify tag sets or a ``maxStalenessSeconds`` value
+   If you specify tag set lists or a ``maxStalenessSeconds`` value
    with :readmode:`primary`, the driver will produce an error.
 
    .. include:: /includes/extracts/transactions-read-pref.rst
@@ -99,7 +99,7 @@ Read Preference Modes
    of the set. However, if the primary is unavailable, as is the case
    during :term:`failover` situations, operations read from :term:`secondary`
    members that satisfy the read preference's ``maxStalenessSeconds`` and
-   tag sets.
+   tag set lists.
 
    .. include:: /includes/extracts/maxStaleness-primaryPreferred.rst
 
@@ -181,9 +181,9 @@ Read Preference Modes
    :ref:`acceptable latency window
    <replica-set-read-preference-behavior-nearest>`.
 
-   If you specify a :ref:`tag set
+   If you specify a :ref:`tag set list
    <replica-set-read-preference-tag-sets>`, the client attempts to
-   find a replica set member that matches the specified tag sets and
+   find a replica set member that matches the specified tag set lists and
    directs reads to an arbitrary member from among the :ref:`nearest
    group <replica-set-read-preference-behavior-nearest>`.
 

source/includes/extracts-read-preference-modes.yaml

@@ -46,10 +46,10 @@ replacement:
 ---
 ref: _tagSets
 content: |
-  When the read preference includes a :ref:`tag set (i.e. a list of tag
-  specifications) <replica-set-read-preference-tag-sets>`{{noPrimary}},
+  When the read preference includes a :ref:`tag set list (an array of tag
+  sets) <replica-set-read-preference-tag-sets>`{{noPrimary}},
   the client attempts to find secondary members with matching tags
-  (trying the tag specifications in order until a match is found). If
+  (trying the tag sets in order until a match is found). If
   matching secondaries are found, the client selects a
   random secondary from the :ref:`nearest group
   <replica-set-read-preference-behavior-nearest>` of matching
@@ -82,7 +82,7 @@ replacement:
 ref: _maxStaleness-and-tagSets
 content: |
   When the read preference includes a ``maxStalenessSeconds`` value
-  **and** a tag set, the client filters by staleness first and
+  **and** a tag set list, the client filters by staleness first and
   then by the specified tags. {{nearestBehavior}}
 ---
 ref: maxStaleness-and-tagSets-general

source/includes/read-preference-modes-table.rst

@@ -44,7 +44,7 @@
        - The :ref:`maxStalenessSeconds
          <replica-set-read-preference-max-staleness>` read preference
          option
-       - Any specified :doc:`tag sets
+       - Any specified :doc:`tag set lists
          </tutorial/configure-replica-set-tag-sets>`
 
        Starting in version 4.4, :readmode:`nearest` supports