DOCSP-26477 Replace x.509 - zones and zone ranges (#2277)

Author: jmd-mongo

source/core/authentication.txt

@@ -71,7 +71,7 @@ must meet the :ref:`client certificate requirements
 
 For more information on x.509 and MongoDB, see:
 
-- :doc:`x.509 Certificate Authentication </core/security-x.509>`
+- :ref:`x.509 Certificate Authentication <security-auth-x509>`
 - :ref:`x509-client-authentication`
 
 .. _security-auth-kerberos:

source/core/hashed-sharding.txt

@@ -96,7 +96,7 @@ Shard the Collection
 --------------------
 
 Use the :method:`sh.shardCollection()` method, specifying the full namespace
-of the collection and the target :doc:`hashed index</core/index-hashed>`
+of the collection and the target :ref:`hashed index <index-type-hashed>`
 to use as the :term:`shard key`.
 
 .. code-block:: javascript
@@ -142,7 +142,7 @@ Shard an Empty Collection
 .. include:: /includes/extracts/zoned-sharding-shard-operation-chunk-distribution.rst
 
 Sharding Empty Collection on Single Field Hashed Shard Key
-  - With no :doc:`zones and zone ranges </core/zone-sharding>` specified 
+  - With no :ref:`zones and zone ranges <zones-sharding>` specified 
     for the empty or non-existing collection:
 
     - The sharding operation creates empty chunks to cover the entire
@@ -156,7 +156,7 @@ Sharding Empty Collection on Single Field Hashed Shard Key
     - After the initial distribution, the balancer manages the chunk
       distribution going forward.
 
-  - With :doc:`zones and zone ranges </core/zone-sharding>` specified
+  - With zones and zone ranges specified
     for the empty or a non-existing collection (Available starting in 
     MongoDB 4.0.3):
 
@@ -173,7 +173,7 @@ Sharding Empty Collection on Compound Hashed Shard Key with Hashed Field Prefix
   If the compound hashed shard key has the hashed field as the prefix
   (i.e. the hashed field is the first field in the shard key):
 
-  - With no :doc:`zones and zone ranges </core/zone-sharding>` specified 
+  - With no zones and zone ranges specified 
     for the empty or non-existing collection:
 
     - The sharding operation creates empty chunks to cover the entire
@@ -188,7 +188,7 @@ Sharding Empty Collection on Compound Hashed Shard Key with Hashed Field Prefix
     - After the initial distribution, the balancer manages the chunk
       distribution going forward.
 
-  -  With a *single* :doc:`zone </core/zone-sharding>` with a 
+  -  With a *single* zone with a 
      range from ``MinKey`` to ``MaxKey`` specified
      for the empty or a non-existing collection *and* 
      the ``presplitHashedZones`` option specified to
@@ -208,21 +208,21 @@ Sharding Empty Collection on Compound Hashed Shard Key with Non-Hashed Prefix
   the prefix (i.e. the hashed field is *not* the first field in the
   shard key):
 
-  - With no :doc:`zones and zone ranges </core/zone-sharding>` specified 
+  - With no zones and zone ranges specified 
     for the empty or non-existing collection *and*
     :ref:`preSplitHashedZones
     <method-shard-collection-presplitHashedZones>` is ``false`` or
     omitted, MongoDB does not perform any initial chunk creation or
     distribution when sharding the collection.
 
-  - With no :doc:`zones and zone ranges </core/zone-sharding>` specified
+  - With no zones and zone ranges specified
     for the empty or non-existing collection *and*
     :ref:`preSplitHashedZones
     <method-shard-collection-presplitHashedZones>`,
     :method:`sh.shardCollection()` / :dbcommand:`shardCollection`
     returns an error.
 
-  -  With :doc:`zones and zone ranges </core/zone-sharding>` specified
+  -  With zones and zone ranges specified
      for the empty or a non-existing collection *and* the
      :ref:`preSplitHashedZones
      <method-shard-collection-presplitHashedZones>` option specified to

source/core/ranged-sharding.txt

@@ -73,7 +73,7 @@ Shard an Empty Collection
 
 If you shard an empty collection:
 
-- With no :doc:`zones and zone ranges </core/zone-sharding>` specified for the
+- With no :ref:`zones and zone ranges <zone-sharding>` specified for the
   empty or non-existing collection:
 
   - The sharding operation creates a single empty chunk to cover the
@@ -83,7 +83,7 @@ If you shard an empty collection:
     chunk across the shards as appropriate as well as manages the chunk
     distribution going forward.
 
-- With :doc:`zones and zone ranges </core/zone-sharding>` specified for the
+- With zones and zone ranges specified for the
   empty or a non-existing collection (Available starting in MongoDB
   4.0.3),
 

source/core/sharding-data-partitioning.txt

@@ -45,7 +45,7 @@ Populated Collection
 Empty Collection
 ~~~~~~~~~~~~~~~~
 
-- If you define :doc:`zones and zone ranges </core/zone-sharding>` defined
+- If you define :ref:`zones and zone ranges <zone-sharding>` defined
   for an empty or non-existing collection (Available starting in
   MongoDB 4.0.3):
 
@@ -59,7 +59,7 @@ Empty Collection
     distribution going forward.
 
 
-- If you do not have :doc:`zones and zone ranges </core/zone-sharding>` defined
+- If you do not have zones and zone ranges defined
   for an empty or non-existing collection:
 
   - For hashed sharding:
@@ -165,8 +165,7 @@ begins migrating data across the cluster to ensure an even distribution.
 
 You can :ref:`manage <sharded-cluster-balancer>` certain aspects of the 
 balancer. The balancer also respects any :term:`zones <zone>` created as 
-a part of configuring :ref:`zones <zone-sharding>` in a sharded 
-cluster.
+a part of configuring zones in a sharded cluster.
 
 See :ref:`sharding-balancing` for more information on the
 :term:`balancer`.

source/includes/steps-clear-jumbo-flag-refine-key.yaml

@@ -81,7 +81,7 @@ content: |
 
    The :dbcommand:`refineCollectionShardKey` command updates the
    :doc:`chunk ranges </core/sharding-data-partitioning>` and
-   :doc:`zone ranges </core/zone-sharding>` to incorporate the new
+   :ref:`zone ranges <zone-sharding>` to incorporate the new
    fields without modifying the range values of the existing key
    fields. That is, the refinement of the shard key does not
    immediately affect the distribution of chunks across shards or

source/reference/command/refineCollectionShardKey.txt

@@ -30,7 +30,7 @@ Definition
    As part of refining the shard key, the
    :dbcommand:`refineCollectionShardKey` command updates the
    :doc:`chunk ranges </core/sharding-data-partitioning>` and
-   :doc:`zone ranges </core/zone-sharding>` to incorporate the new
+   :ref:`zone ranges <zone-sharding>` to incorporate the new
    fields without modifying the range values of the existing key
    fields. That is, the refinement of the shard key does not
    immediately affect the distribution of chunks across shards or

source/reference/command/serverStatus.txt

@@ -4032,7 +4032,7 @@ security
    .. serverstatus:: security.authentication.mechanisms.MONGODB-X509
 
       A document that reports on the number of times
-      :doc:`x.509 </core/security-x.509/>` has been used to
+      :ref:`x.509 <security-auth-x509>` has been used to
       authenticate against the
       :binary:`~bin.mongod` or :binary:`~bin.mongos` instance.
 
@@ -4045,31 +4045,31 @@ security
    .. serverstatus:: security.authentication.mechanisms.MONGODB-X509.speculativeAuthenticate.received
 
       Number of speculative authentication attempts received using
-      :doc:`x.509 </core/security-x.509/>`. Includes both successful and
+      :ref:`x.509 <security-auth-x509>`. Includes both successful and
       failed speculative authentication attempts. [#speculative-auth]_
 
       .. versionadded:: 4.4
 
    .. serverstatus:: security.authentication.mechanisms.MONGODB-X509.speculativeAuthenticate.successful
 
       Number of successful speculative authentication attempts received
-      using :doc:`x.509 </core/security-x.509/>`. [#speculative-auth]_
+      using x.509. [#speculative-auth]_
 
       .. versionadded:: 4.4
 
    .. serverstatus:: security.authentication.mechanisms.MONGODB-X509.authenticate.received
 
       Number of successful and failed authentication attempts
-      received using :doc:`x.509 </core/security-x.509/>`. This value
-      includes speculative authentication attempts received using x.509.
+      received using x.509.  This value includes speculative 
+      authentication attempts received using x.509.
 
       .. versionadded:: 4.4
 
    .. serverstatus:: security.authentication.mechanisms.MONGODB-X509.authenticate.successful
 
       Number of successful authentication attempts received using
-      :doc:`x.509 </core/security-x.509/>`. This value includes
-      successful speculative authentication attempts which used x.509.
+      x.508. This value includes successful speculative authentication 
+      attempts which used x.509.
 
       .. versionadded:: 4.4
 

source/tutorial/deploy-replica-set-with-keyfile-access-control.txt

@@ -62,7 +62,7 @@ Keyfile Security
 
 Keyfiles are bare-minimum forms of security and are best suited for testing or
 development environments. For production environments we recommend using
-:doc:`x.509 certificates</core/security-x.509>`.
+:ref:`x.509 certificates<security-auth-x509>`.
 
 .. _security-repSetDeploy-access-control:
 

source/tutorial/deploy-sharded-cluster-with-keyfile-access-control.txt

@@ -60,7 +60,7 @@ Keyfile Security
 
 Keyfiles are bare-minimum forms of security and are best suited for testing or
 development environments. For production environments we recommend using
-:doc:`x.509 certificates</core/security-x.509>`.
+:ref:`x.509 certificates<security-auth-x509>`.
 
 .. _security-shardClust-deploy-access-control:
 

source/tutorial/enforce-keyfile-access-control-in-existing-replica-set.txt

@@ -60,7 +60,7 @@ Keyfile Security
 
 Keyfiles are bare-minimum forms of security and are best suited for testing or
 development environments. For production environments we recommend using
-:doc:`x.509 certificates</core/security-x.509>`.
+:ref:`x.509 certificates<security-auth-x509>`.
 
 .. _security-replSet-auth-access-control: