Revert "(DOCSP-53992) Predictive auto-scaling private preview for AKO CRD (#1…" (#14795)

This reverts commit 1ffc810.

Author: JuliaMongo

content/atlas-operator/current/source/ak8so-stream-processing.txt

@@ -33,7 +33,7 @@ to do the following tasks:
 
 {+atlas-sp+} components belong directly to |service| projects and
 operate independent of |service| {+clusters+}. To learn more, see 
-:atlas:`{+atlas-sp+} <what-is-atlas-sp>`.
+:ref:`what-is-atlas-sp`.
 
 .. _ak8so-spi-connections:
 

content/atlas-operator/current/source/atlasdeployment-custom-resource.txt

@@ -917,8 +917,8 @@ examples, and the |api| documentation.
    Flag that indicates whether this {+database-deployment+} enables 
    disk autoscaling. This parameter defaults to ``true``.
 
-   - Set to ``true`` to enable disk auto-scaling.
-   - Set to ``false`` to disable disk auto-scaling.
+   - Set to ``true`` to enable disk autoscaling.
+   - Set to ``false`` to disable disk autoscaling.
 
    .. include:: /includes/cluster-settings/ram-to-storage-ratio.rst
 
@@ -928,13 +928,13 @@ examples, and the |api| documentation.
 
    *Optional*
 
-   Flag that indicates whether instance size auto-scaling is
+   Flag that indicates whether instance size autoscaling is
    enabled. This parameter defaults to ``false``.
 
-   - Set to ``true`` to enable instance size auto-scaling. If
+   - Set to ``true`` to enable instance size autoscaling. If
      enabled, you must specify a value for :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.maxInstanceSize`.
 
-   - Set to ``false`` to disable instance size auto-scaling.
+   - Set to ``false`` to disable instance size autoscaling.
 
 .. setting:: spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.maxInstanceSize
 
@@ -950,7 +950,7 @@ examples, and the |api| documentation.
    .. note::
 
       If you set a maximum instance size smaller than the
-      {+database-deployment+}\'s current instance size with auto-scaling
+      {+database-deployment+}\'s current instance size with autoscaling
       enabled, |service| automatically scales the current instance
       size to the maximum value you specify.
 
@@ -963,7 +963,7 @@ examples, and the |api| documentation.
       change the 
       :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.electableSpecs.instanceSize`
       in |ak8so| to match the new instance size, |ak8so| displays a
-      warning in the logs but doesn't prevent auto-scaling.
+      warning in the logs but doesn't prevent autoscaling.
 
 .. setting:: spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.minInstanceSize
 
@@ -980,7 +980,7 @@ examples, and the |api| documentation.
    .. note::
 
       If you set a minimum instance size larger than the
-      {+database-deployment+}\'s current instance size with auto-scaling
+      {+database-deployment+}\'s current instance size with autoscaling
       enabled, |service| automatically scales the current instance size
       to the minimum value you specify.
 
@@ -993,7 +993,7 @@ examples, and the |api| documentation.
       change the 
       :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.electableSpecs.instanceSize`
       in |ak8so| to match the new instance size, |ak8so| displays a
-      warning in the logs but doesn't prevent auto-scaling.
+      warning in the logs but doesn't prevent autoscaling.
 
 .. setting:: spec.deploymentSpec.replicationSpecs.regionConfigs.electableSpecs
 
@@ -1039,7 +1039,7 @@ examples, and the |api| documentation.
 
    .. note::
 
-      If you have auto-scaling enabled for the compute field, you can't 
+      If you have autoscaling enabled for the compute field, you can't 
       edit this option. To learn more, see :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.enabled`.
 
    .. note::

content/atlas-operator/current/source/atlasstreamconnection-custom-resource.txt

@@ -13,7 +13,7 @@
    :class: singlecol
 
 The ``AtlasStreamConnection`` custom resource configures 
-:atlas:`{+atlas-sp+} <what-is-atlas-sp>` :ref:`connections 
+:ref:`{+atlas-sp+} <what-is-atlas-sp>` :ref:`connections 
 <ak8so-spi-connections>`. You can configure a sample connection, a 
 connection to an {+service+} :manual:`change stream </changeStreams>`, 
 or a connection to an {+kafka+} system.

content/atlas-operator/current/source/atlasstreaminstance-custom-resource.txt

@@ -13,7 +13,7 @@
    :class: singlecol
 
 The ``AtlasStreamInstance`` custom resource configures 
-:atlas:`{+atlas-sp+} <what-is-atlas-sp>` :ref:`instances 
+:ref:`{+atlas-sp+} <what-is-atlas-sp>` :ref:`instances 
 <ak8so-spi-connections>`.
 
 .. _atlasstreaminstance-example:

content/atlas-operator/current/source/includes/steps-upgrade-v1-to-v2.rst

@@ -4,7 +4,7 @@
    .. step:: Deploy a new |k8s| cluster.
 
       With this new cluster deployed, you now have two |k8s| clusters. The 
-      following steps require that you run ``kubectl`` commands against each of
+      following steps require that you run ``kubectl`` commmands against each of
       these |k8s| clusters. To simplify this, you can configure each of the |k8s| 
       contexts with the following commands:
 
@@ -19,7 +19,7 @@
    .. step:: Deploy |ak8so| ``v2.x`` to your new K8s cluster.
 
       Replace the ``<version>`` placeholder in the following command with your 
-      desired |ak8so| version, and run the command to deploy |ak8so| to your newly provisioned 
+      desired |ak8so| version, and run the command to deploy |ak8so| to your newly provsioned 
       |k8s| cluster.
 
       .. code-block:: sh

content/atlas-operator/upcoming/source/ak8so-stream-processing.txt

@@ -33,7 +33,7 @@ to do the following tasks:
 
 {+atlas-sp+} components belong directly to |service| projects and
 operate independent of |service| {+clusters+}. To learn more, see 
-:atlas:`what-is-atlas-sp`.
+:ref:`what-is-atlas-sp`.
 
 .. _ak8so-spi-connections:
 

content/atlas-operator/upcoming/source/atlasdeployment-custom-resource.txt

@@ -165,7 +165,7 @@ Configuration Example
 ~~~~~~~~~~~~~~~~~~~~~
 
 The following example shows an ``AtlasDeployment`` custom resource 
-specification configured for auto-scaling multi-region {+clusters+}:
+specification configured for autoscaling multi-region {+clusters+}:
 
 .. code-block::
 
@@ -665,7 +665,7 @@ examples, and the |api| documentation.
 
    .. note::
 
-      If you enable auto-scaling for ``diskGB`` in any region, you can't edit
+      If you enable autoscaling for ``diskGB`` in any region, you can't edit
       this option. To learn more, see :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.diskGB.enabled`.
 
    The minimum disk size for {+dedicated-clusters+} is 10 GB for |aws| and
@@ -931,10 +931,10 @@ examples, and the |api| documentation.
    *Optional*
 
    Flag that indicates whether this {+database-deployment+} enables 
-   disk auto-scaling. This parameter defaults to ``true``.
+   disk autoscaling. This parameter defaults to ``true``.
 
-   - Set to ``true`` to enable disk auto-scaling.
-   - Set to ``false`` to disable disk auto-scaling.
+   - Set to ``true`` to enable disk autoscaling.
+   - Set to ``false`` to disable disk autoscaling.
 
    .. include:: /includes/cluster-settings/ram-to-storage-ratio.rst
 
@@ -944,13 +944,13 @@ examples, and the |api| documentation.
 
    *Optional*
 
-   Flag that indicates whether instance size auto-scaling is
+   Flag that indicates whether instance size autoscaling is
    enabled. This parameter defaults to ``false``.
 
-   - Set to ``true`` to enable instance size auto-caling. If
+   - Set to ``true`` to enable instance size autoscaling. If
      enabled, you must specify a value for :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.maxInstanceSize`.
 
-   - Set to ``false`` to disable instance size auto-scaling.
+   - Set to ``false`` to disable instance size autoscaling.
 
 .. setting:: spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.maxInstanceSize
 
@@ -966,7 +966,7 @@ examples, and the |api| documentation.
    .. note::
 
       If you set a maximum instance size smaller than the
-      {+database-deployment+}\'s current instance size with auto-scaling
+      {+database-deployment+}\'s current instance size with autoscaling
       enabled, |service| automatically scales the current instance
       size to the maximum value you specify.
 
@@ -979,7 +979,7 @@ examples, and the |api| documentation.
       change the 
       :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.electableSpecs.instanceSize`
       in |ak8so| to match the new instance size, |ak8so| displays a
-      warning in the logs but doesn't prevent auto-scaling.
+      warning in the logs but doesn't prevent autoscaling.
 
 .. setting:: spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.minInstanceSize
 
@@ -996,7 +996,7 @@ examples, and the |api| documentation.
    .. note::
 
       If you set a minimum instance size larger than the
-      {+database-deployment+}\'s current instance size with auto-scaling
+      {+database-deployment+}\'s current instance size with autoscaling
       enabled, |service| automatically scales the current instance size
       to the minimum value you specify.
 
@@ -1009,28 +1009,7 @@ examples, and the |api| documentation.
       change the 
       :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.electableSpecs.instanceSize`
       in |ak8so| to match the new instance size, |ak8so| displays a
-      warning in the logs but doesn't prevent auto-scaling.
-
-.. setting:: spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.predictiveEnabled
-
-   *Type*: boolean
-     
-   *Optional*
-
-   Flag that indicates whether predictive instance size auto-scaling is enabled.
-   This parameter defaults to ``false``.
-
-   .. important::
-
-      This feature is in private preview  and is available only for certain |service|
-      customers. To request access, contact your MongoDB support representative.
-      Setting this parameter to ``true`` without having access has no effect.
-    
-   Set to ``true`` to enable predictive instance size auto-scaling.
-   |service| requires to set the :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.enabled`
-   to ``true`` in order to enable this setting.
-
-   Set to ``false`` to disable predictive instance size auto-scaling.
+      warning in the logs but doesn't prevent autoscaling.
 
 .. setting:: spec.deploymentSpec.replicationSpecs.regionConfigs.electableSpecs
 
@@ -1069,14 +1048,14 @@ examples, and the |api| documentation.
    :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.minInstanceSize` 
    and 
    :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.maxInstanceSize` 
-   with auto-scaling enabled. To learn more, see 
+   with autoscaling enabled. To learn more, see 
    :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.minInstanceSize` 
    and 
    :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.maxInstanceSize`.
 
    .. note::
 
-      If you have auto-scaling enabled for the compute field, you can't 
+      If you have autoscaling enabled for the compute field, you can't 
       edit this option. To learn more, see :setting:`spec.deploymentSpec.replicationSpecs.regionConfigs.autoScaling.compute.enabled`.
 
    .. note::

content/atlas-operator/upcoming/source/atlasstreamconnection-custom-resource.txt

@@ -13,7 +13,7 @@
    :class: singlecol
 
 The ``AtlasStreamConnection`` custom resource configures 
-:atlas:`{+atlas-sp+} <what-is-atlas-sp>` :ref:`connections 
+:ref:`{+atlas-sp+} <what-is-atlas-sp>` :ref:`connections 
 <ak8so-spi-connections>`. You can configure a sample connection, a 
 connection to an {+service+} :manual:`change stream </changeStreams>`, 
 or a connection to an {+kafka+} system.

content/atlas-operator/upcoming/source/atlasstreaminstance-custom-resource.txt

@@ -13,7 +13,7 @@
    :class: singlecol
 
 The ``AtlasStreamInstance`` custom resource configures 
-:atlas:`{+atlas-sp+} <what-is-atlas-sp>` :ref:`instances 
+:ref:`{+atlas-sp+} <what-is-atlas-sp>` :ref:`instances 
 <ak8so-spi-connections>`.
 
 .. _atlasstreaminstance-example:

content/atlas-operator/upcoming/source/includes/steps-upgrade-v1-to-v2.rst

@@ -4,7 +4,7 @@
    .. step:: Deploy a new |k8s| cluster.
 
       With this new cluster deployed, you now have two |k8s| clusters. The 
-      following steps require that you run ``kubectl`` commands against each of
+      following steps require that you run ``kubectl`` commmands against each of
       these |k8s| clusters. To simplify this, you can configure each of the |k8s| 
       contexts with the following commands:
 
@@ -19,7 +19,7 @@
    .. step:: Deploy |ak8so| ``v2.x`` to your new K8s cluster.
 
       Replace the ``<version>`` placeholder in the following command with your 
-      desired |ak8so| version, and run the command to deploy |ak8so| to your newly provisioned 
+      desired |ak8so| version, and run the command to deploy |ak8so| to your newly provsioned 
       |k8s| cluster.
 
       .. code-block:: sh