DOCS-16222 Removed unused parameter from sh.removeTagRange() (#4973) (#5090)

* DOCS-16222 Removed unused parameter from sh.removeTagRange() (#4973)

* Removed unused parameter from sh.removeTagRange()

* Removed self references

* Some PR feedback

* External review feedback

* Empty rebuild

* Empty rebuild

Author: nvillahermosa-mdb

source/includes/steps-sharding-segmenting-data-by-location-update.yaml

@@ -44,15 +44,13 @@ action:
       * The full namespace of the target collection. 
       * The inclusive lower bound of the range. 
       * The exclusive upper bound of the range. 
-      * The name of the zone.
       
     language: javascript
     code: |
       sh.removeTagRange(
         "chat.messages",
         { "country" : "UK", "userid" : MinKey },
         { "country" : "UK", "userid" : MaxKey }
-        "EU"
       )
 ---
 stepnum: 4

source/includes/steps-sharding-tiered-hardware-for-varying-slas-update.yaml

@@ -29,15 +29,13 @@ action:
       * the full namespace of the target collection.
       * the inclusive lower bound of the range. 
       * the exclusive upper bound of the range. 
-      * the zone.
       
     language: javascript
     code: |
       sh.removeTagRange( 
         "photoshare.data",
         { "creation_date" : ISODate("2016-01-01") },
-        { "creation_date" : MaxKey }, 
-        "recent"
+        { "creation_date" : MaxKey }
       )
   - pre: |
       Remove the old ``archive`` zone range using the 
@@ -46,15 +44,13 @@ action:
       * the full namespace of the target collection.
       * the inclusive lower bound of the range. 
       * the exclusive upper bound of the range. 
-      * the zone.
       
     language: javascript
     code: |
       sh.removeTagRange( 
         "photoshare.data",
         { "creation_date" : MinKey },
-        { "creation_date" : ISODate("2016-01-01") }, 
-        "archive"
+        { "creation_date" : ISODate("2016-01-01") }
       )
 post: |
   :bsontype:`MinKey` and :bsontype:`MaxKey` are reserved special values for

source/reference/method/sh.removeRangeFromZone.txt

@@ -18,7 +18,7 @@ Definition
    Removes the association between a range of shard key values and a
    :term:`zone`.
 
-   :method:`sh.removeRangeFromZone()` takes the following arguments:
+   ``sh.removeRangeFromZone()`` takes the following fields:
 
 
    .. list-table::
@@ -60,25 +60,22 @@ Definition
 
           Specify each field of the shard key in the form of ``<fieldname> : <value>``.
           The value must be of the same BSON type or types as the shard key.
-          
-          
-   
 
 
-   Use :method:`sh.removeRangeFromZone()` to remove the association between
-   unused, out of date, or conflicting ranges and a zone.
+   Use ``sh.removeRangeFromZone()`` to remove the association between
+   unused, out of date, or conflicting shard key ranges and a zone.
 
    If no range matches the minimum and maximum bounds passed to
-   :method:`~sh.removeShardFromZone()`, nothing is removed.
+   ``sh.removeRangeFromZone()``, nothing is removed.
 
-   Only issue :method:`sh.removeTagRange()` when connected to a
+   Only run ``sh.removeRangeFromZone()`` when connected to a
    :binary:`~bin.mongos` instance.
 
 Behavior
 --------
 
-:method:`sh.removeShardFromZone()` does not remove the zone associated to the
-specified range.
+``sh.removeRangeFromZone()`` doesn't remove the association between
+a zone and a shard. It also doesn't remove the zone itself.
 
 See the :ref:`zone <zone-sharding>` manual page for more information on zones
 in sharded clusters.
@@ -112,11 +109,10 @@ must authenticate as either:
   or, alternatively
 
 - a user whose privileges include :authaction:`enableSharding` on the
-  :ref:`cluster <resource-specific-collection>` resource (available
-  starting in version 4.2.2, 4.0.14, 3.6.16).
+  :ref:`cluster <resource-specific-collection>` resource.
 
 The :authrole:`clusterAdmin` or :authrole:`clusterManager` built-in roles have
-the appropriate permissions for issuing :method:`sh.removeRangeFromZone()`.
+the appropriate permissions for running ``sh.removeRangeFromZone()``.
 See the documentation page for :ref:`Role-Based Access Control
 <authorization>` for more information.
 
@@ -152,7 +148,7 @@ specifies ``{ a : 0 }`` as the ``min`` bound:
 
 While the range of ``{ a : 0 }`` and ``{ a : 10 }`` encompasses the existing
 range, it is not an exact match and therefore
-:method:`sh.removeRangeFromZone()` does not remove anything.
+``sh.removeRangeFromZone()`` does not remove anything.
 
 Compound Shard Key
 ~~~~~~~~~~~~~~~~~~
@@ -171,5 +167,5 @@ bound of ``{ a : 1, b : 1}`` and an upper bound of ``{ a : 10, b : 10 }``:
 Given the previous example, if there was an existing range with a lower bound
 of ``{ a : 1, b : 5 }`` and an upper bound of ``{ a : 10, b : 1 }``, the
 operation would *not* remove that range, as it is not an exact match of the
-minimum and maximum passed to :method:`sh.removeRangeFromZone()`.
+minimum and maximum passed to ``sh.removeRangeFromZone()``.
 

source/reference/method/sh.removeTagRange.txt

@@ -13,7 +13,7 @@ sh.removeTagRange()
 Definition
 ----------
 
-.. method:: sh.removeTagRange(namespace, minimum, maximum, tag)
+.. method:: sh.removeTagRange(namespace, minimum, maximum)
 
    .. |method| replace:: :method:`sh.removeRangeFromZone()`
 
@@ -58,24 +58,12 @@ Definition
         - The maximum value of the shard key range from the tag.
           Specify the maximum value in the form of ``<fieldname>:<value>``. This
           value must be of the same BSON type or types as the shard key.
-          
-          
-   
-      * - ``tag``
-   
-        - string
-   
-        - The name of the tag attached to the range specified by the ``minimum``
-          and ``maximum`` arguments to.
-          
-          
-   
 
 
-   Use :method:`sh.removeShardTag()` to ensure that unused or out of
+   Use ``sh.removeTagRange()`` to ensure that unused or out of
    date ranges are removed and hence chunks are balanced as required.
 
-   Only issue :method:`sh.removeTagRange()` when connected to a
+   Only run ``sh.removeTagRange()`` when connected to a
    :binary:`~bin.mongos` instance.
 
 Example
@@ -88,6 +76,5 @@ removes an existing tag range covering zip codes in New York State:
 
    sh.removeTagRange( "exampledb.collection",
                    { state: "NY", zip: MinKey },
-                   { state: "NY", zip: MaxKey },
-                   "NY"
+                   { state: "NY", zip: MaxKey }
                  )