Fix warnings (#1)

* docurl

* change doc role to atlas role

* fix more errors

* fix more stuff

* trying this again

Author: jwilliams-mongo

assets.toml

@@ -0,0 +1,10 @@
+[assets.output_paths]
+repository_path = "source/includes"
+
+[[assets.sources.repository]]
+repo = "mongodb/mongodb-atlas-cli"
+version = "atlascli/v1.14.0"
+
+[[assets.sources.repository.targets]]
+source = "docs/atlascli/command/atlas-kubernetes-operator-install.txt"
+output = "command/atlas-kubernetes-operator-install.txt"

source/ak8so-changelog.txt

@@ -214,7 +214,7 @@ New Features
 
 :ref:`atlasdeployment-custom-resource`:
 
-- Adds support for :doc:`Global {+Cluster+} </global-clusters>`
+- Adds support for :atlas:`Global {+Cluster+} </global-clusters>`
   parameters in ``spec.advancedDeploymentSpec.*`` and ``spec.deploymentSpec.*``.
   To learn more, see :ref:`AtlasDeployment custom resource parameters <atlasdeployment-crd-params>`.
   These Global Cluster parameters map zones to geographic regions and allow you

source/atlasdeployment-custom-resource.txt

@@ -408,7 +408,7 @@ documentation to customize your specifications.
         - Required
 
       * - You are deploying
-          :doc:`Global {+Clusters+} </global-clusters>`.
+          :atlas:`Global {+Clusters+} </global-clusters>`.
         - Required
 
       * - You are deploying non-Global replica sets and sharded
@@ -424,11 +424,11 @@ documentation to customize your specifications.
       * - Value
         - {+Cluster+} Type
       * - REPLICASET
-        - :term:`replica set`
+        - replica set
       * - SHARDED
-        - :term:`sharded cluster`
+        - sharded cluster
       * - GEOSHARDED
-        - :doc:`global {+cluster+} </global-clusters>`
+        - :atlas:`global {+cluster+} </global-clusters>`
 
 .. setting:: spec.deploymentSpec.customZoneMapping
 
@@ -707,7 +707,7 @@ documentation to customize your specifications.
         - Values
 
       * - You are deploying
-          :doc:`Global {+Clusters+} </global-clusters>`.
+          :atlas:`Global {+Clusters+} </global-clusters>`.
         - Required
         - Each object in the array represents a zone where
           |service| deploys your {+cluster+}'s nodes.
@@ -739,11 +739,11 @@ documentation to customize your specifications.
 
    - If you specify a value of ``1`` and you set 
      :setting:`spec.deploymentSpec.clusterType` to ``SHARDED``, 
-     |service| deploys a single-shard :term:`sharded cluster`.
+     |service| deploys a single-shard sharded cluster.
 
    - If you specify ``1`` and you set 
      :setting:`spec.deploymentSpec.clusterType` to ``REPLICASET``, 
-     |service| deploys a :term:`replica set`.
+     |service| deploys a replica set.
 
      .. include:: /includes/cluster-settings/single-shard-cluster-warning.rst
 
@@ -786,7 +786,7 @@ documentation to customize your specifications.
    Hardware specifications for :ref:`analytics nodes 
    <analytics-nodes-overview>` needed in the region. Analytics nodes 
    handle analytic data such as reporting queries from |bic|. Analytics 
-   nodes are read-only and can never become the :term:`primary`.
+   nodes are read-only and can never become the primary.
 
    If you don't specify this parameter, |service| deploys no analytics  
    to this region.
@@ -884,7 +884,7 @@ documentation to customize your specifications.
    *Optional*
 
    Hardware specifications for electable nodes in the region.
-   Electable nodes can become the :term:`primary` and can enable
+   Electable nodes can become the primary and can enable
    local reads.
 
    If you don't specify this option, |service| deploys no electable 
@@ -903,7 +903,7 @@ documentation to customize your specifications.
    :ref:`GCP <google-gcp>`, and :ref:`Azure <microsoft-azure>` custom 
    storage sizes.
 
-   If you deploy a :term:`sharded cluster`, or :doc:`global {+cluster+} 
+   If you deploy a sharded cluster, or :atlas:`global {+cluster+} 
    </global-clusters>`, you must choose an instance size of ``M30`` or 
    greater.
 
@@ -919,7 +919,7 @@ documentation to customize your specifications.
    *Conditional*
 
    Number of electable nodes for |service| to deploy to the region.
-   Electable nodes can become the :term:`primary` and can enable
+   Electable nodes can become the primary and can enable
    local reads.
 
    The combined ``electableSpecs.nodeCount`` across all
@@ -959,7 +959,7 @@ documentation to customize your specifications.
    have a priority of ``7``. The lowest possible priority is ``1``.
 
    The priority ``7`` region identifies the **Preferred Region** of
-   the {+cluster+}. |service| places the :term:`primary` node in the
+   the {+cluster+}. |service| places the primary node in the
    **Preferred Region**. Priorities ``1`` through ``7`` are
    exclusive: you can't assign a given priority to more than one
    region per {+cluster+}.
@@ -978,7 +978,7 @@ documentation to customize your specifications.
    *Optional*
 
    Hardware specifications for read-only nodes in the region.
-   Read-only nodes can never become the :term:`primary` member, but
+   Read-only nodes can never become the primary member, but
    can enable local reads.
 
    If you don't specify this parameter, |service| deploys no read-only 
@@ -991,7 +991,7 @@ documentation to customize your specifications.
    *Optional*
 
    Human-readable label that identifies the zone in a 
-   :doc:`Global {+Cluster+} </global-clusters>`. Provide this value 
+   :atlas:`Global {+Cluster+} </global-clusters>`. Provide this value 
    only if you set :setting:`spec.deploymentSpec.clusterType` to 
    ``GEOSHARDED``.
 

source/atlasproject-custom-resource.txt

@@ -1223,7 +1223,7 @@ This section describes the ``AtlasProject`` custom resource parameters:
 
    Human-readable label that identifies the privilege action. For a 
    complete list of actions available in the {+atlas-admin-api+}, see 
-   :doc:`/reference/custom-role-actions`.
+   :atlas:`/reference/custom-role-actions`.
 
 .. setting:: spec.customRoles.actions.resources
 

source/includes/cluster-settings/api-analytics-nodes-description.rst

@@ -1,4 +1,4 @@
 Number of :ref:`analytics nodes <analytics-nodes-overview>` for
 |service| to deploy to the region. Analytics nodes are useful for
 handling analytic data such as reporting queries from |bic|. Analytics
-nodes are read-only, and can never become the :term:`primary`.
+nodes are read-only, and can never become the primary.

source/includes/cluster-settings/global-cluster/extracts-settings.yaml

@@ -5,7 +5,7 @@ content: |
 
   *Required*
 
-  List that contains :doc:`Global {+Cluster+} </global-clusters>`
+  List that contains :atlas:`Global {+Cluster+} </global-clusters>`
   parameters that map zones to geographic regions. For a full list of
   available parameters, see the |service| :oas-atlas-tag:`Global
   {+Clusters+} API </Global-Clusters>`.
@@ -18,7 +18,7 @@ content: |
 
   *Required*
 
-  Code that represents a location that maps to a zone in your :doc:`Global
+  Code that represents a location that maps to a zone in your :atlas:`Global
   {+Cluster+} </global-clusters>`.
 
 ---
@@ -29,7 +29,7 @@ content: |
 
    *Required*
 
-   Human-readable label that identifies the zone in your :doc:`Global
+   Human-readable label that identifies the zone in your :atlas:`Global
    {+Cluster+} </global-clusters>`.
 
 ---
@@ -41,7 +41,7 @@ content: |
   *Required*
 
   List that contains information to create a managed namespace in a
-  specified :doc:`Global {+Cluster+} </global-clusters>` to create. For
+  specified :atlas:`Global {+Cluster+} </global-clusters>` to create. For
   a full list of available parameters, see the |service|
   :oas-atlas-tag:`Global {+Clusters+} API
   </Global-Clusters>`.
@@ -54,7 +54,7 @@ content: |
 
   *Required*
 
-  Human-readable label of the collection to manage in this :doc:`Global
+  Human-readable label of the collection to manage in this :atlas:`Global
   {+Cluster+} </global-clusters>`.
 
 ---
@@ -65,7 +65,7 @@ content: |
 
   *Required*
 
-  Human-readable label of the database to manage in this :doc:`Global
+  Human-readable label of the database to manage in this :atlas:`Global
   {+Cluster+} </global-clusters>`.
 
 ---

source/includes/cluster-settings/global-cluster/vpc/first-paid-cluster.rst

@@ -1,3 +1,3 @@
 If this is the first dedicated paid cluster for the selected region or
 regions *and* you plan on creating one or more
-:abbr:`VPC peering connections`, review :doc:`VPC Peering Connections </security-vpc-peering>` before continuing.
+:abbr:`VPC peering connections`, review :atlas:`VPC Peering Connections </security-vpc-peering>` before continuing.

source/includes/cluster-settings/group-region-association.rst

@@ -20,4 +20,4 @@ Multi-Region Clusters
   resides in the same region as the nodes to communicate with the
   peered |vpc|.
 
-To learn more, see :doc:`/security-vpc-peering`.
+To learn more, see :atlas:`/security-vpc-peering`.

source/includes/cluster-settings/instance-size-parameter-advanced.rst

@@ -5,7 +5,7 @@ size.
 
 **See Also:** :ref:`server-number-costs`.
 
-If you deploy a :doc:`Global Cluster </global-clusters>`, you must
+If you deploy a :atlas:`Global Cluster </global-clusters>`, you must
 choose a instance size of **M30** or greater.
 
 .. tabs-cloud-providers::

source/includes/cluster-settings/instance-size-parameter.rst

@@ -5,7 +5,7 @@ size.
 
 **See Also:** :ref:`server-number-costs`.
 
-If you deploy a :doc:`Global Cluster </global-clusters>`, you must
+If you deploy a :atlas:`Global Cluster </global-clusters>`, you must
 choose a instance size of **M30** or greater.
 
 .. tabs-cloud-providers::