fix anchors

shainaraskas · shainaraskas · commit 545873ca7ebd · 2025-03-03T15:28:02.000-05:00
diff --git a/deploy-manage/manage-spaces.md b/deploy-manage/manage-spaces.md
@@ -40,10 +40,10 @@ The maximum number of spaces that you can have differs by deployment type:
 
 To create a space: 
 
-::::{tab-set}
+:::::{tab-set}
 :group: stack-serverless
 
-:::{tab-item} {{serverless-short}}
+::::{tab-item} {{serverless-short}}
 :sync: serverless
 
 1. Click **Create space** or select the space you want to edit.
@@ -54,9 +54,9 @@ To create a space:
 
 3. Customize the avatar of the space to your liking.
 4. Save the space.
-:::
+::::
 
-:::{tab-item} {{stack}}
+::::{tab-item} {{stack}}
 :sync: stack
 
 1. Select **Create space** and provide a name, description, and URL identifier.
@@ -70,15 +70,16 @@ To create a space:
 
 3. If you selected the **Classic** solution view, you can customize the **Feature visibility** as you need it to be for that space.
 
-   % This is hacking since proper admonition blocks are currently breaking my tabs
-   > **Note:** Even when disabled in this menu, some Management features can remain visible to some users depending on their privileges. Additionally, controlling feature visibility is not a security feature. To secure access to specific features on a per-user basis, you must configure [{{kib}} Security](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md).
+   :::{note}
+   Even when disabled in this menu, some Management features can remain visible to some users depending on their privileges. Additionally, controlling feature visibility is not a security feature. To secure access to specific features on a per-user basis, you must configure [{{kib}} Security](/deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md).
+   :::
 
 4. Customize the avatar of the space to your liking.
 5. Save your new space by selecting **Create space**.
-:::
-
 ::::
 
+:::::
+
 You can edit all of the space settings you just defined at any time, except for the URL identifier.
 
 Elastic also allows you to manage spaces using APIs: 
diff --git a/explore-analyze/machine-learning/setting-up-machine-learning.md b/explore-analyze/machine-learning/setting-up-machine-learning.md
@@ -66,7 +66,7 @@ Granting `All` or `Read` {{kib}} feature privilege for {{ml-app}} will also gran
 
 #### Feature visibility in Spaces [kib-visibility-spaces]
 
-In {{kib}}, the {{ml-features}} must be visible in your [space](../../deploy-manage/manage-spaces.md#spaces-control-feature-visibility). To manage which features are visible in your space, go to **{{stack-manage-app}}** > **{{kib}}** > **Spaces** or use the [global search field](../find-and-organize/find-apps-and-objects.md) to locate **Spaces** directly.
+In {{kib}}, the {{ml-features}} must be visible in your [space](../../deploy-manage/manage-spaces.md). To manage which features are visible in your space, go to **{{stack-manage-app}}** > **{{kib}}** > **Spaces** or use the [global search field](../find-and-organize/find-apps-and-objects.md) to locate **Spaces** directly.
 
 :::{image} ../../images/machine-learning-spaces.jpg
 :alt: Manage spaces in {{kib}}
diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-administering-deployments.md b/raw-migrated-files/cloud/cloud-enterprise/ece-administering-deployments.md
diff --git a/raw-migrated-files/cloud/cloud/ec-faq-technical.md b/raw-migrated-files/cloud/cloud/ec-faq-technical.md
@@ -2,14 +2,6 @@
 
 This frequently-asked-questions list answers some of your more common questions about configuring {{ech}}.
 
-* [Can I implement a Hot-Warm architecture?](../../../deploy-manage/index.md#faq-hw-architecture)
-* [What about dedicated master nodes?](../../../deploy-manage/index.md#faq-master-nodes)
-* [Can I use a Custom SSL certificate?](../../../deploy-manage/index.md#faq-ssl)
-* [Can {{ech}} autoscale?](../../../deploy-manage/index.md#faq-autoscale)
-* [Do you support IP sniffing?](../../../deploy-manage/index.md#faq-ip-sniffing)
-* [Does {{ech}} support encryption at rest?](../../../deploy-manage/index.md#faq-encryption-at-rest)
-* [Can I find the static IP addresses for my endpoints on {{ech}}?](../../../deploy-manage/index.md#faq-static-ip-elastic-cloud)
-
     $$$faq-hw-architecture$$$Can I implement a hot-warm architecture?
     :   [*hot-warm architecture*](https://www.elastic.co/blog/hot-warm-architecture) refers to an Elasticsearch setup for larger time-data analytics use cases with two different types of nodes, hot and warm. {{ech}} supports hot-warm architectures in all of the solutions provided by allowing you to add warm nodes to any of your deployments.
 
diff --git a/raw-migrated-files/toc.yml b/raw-migrated-files/toc.yml
@@ -26,7 +26,6 @@ toc:
       - file: cloud/cloud-enterprise/ece-access-kibana.md
       - file: cloud/cloud-enterprise/ece-add-custom-bundle-plugin.md
       - file: cloud/cloud-enterprise/ece-add-user-settings.md
-      - file: cloud/cloud-enterprise/ece-administering-deployments.md
       - file: cloud/cloud-enterprise/ece-api-console.md
       - file: cloud/cloud-enterprise/ece-autoscaling.md
       - file: cloud/cloud-enterprise/ece-change-deployment.md
diff --git a/reference/glossary/index.md b/reference/glossary/index.md
@@ -286,7 +286,7 @@ $$$glossary-external-alert$$$ external alert
 ## F [f-glos]
 
 $$$glossary-feature-controls$$$ Feature Controls
-:   Enables administrators to customize which features are available in each [space](/reference/glossary/index.md#glossary-space). See [Feature Controls](/deploy-manage/manage-spaces.md#spaces-control-feature-visibility).
+:   Enables administrators to customize which features are available in each [space](/reference/glossary/index.md#glossary-space). See [](/deploy-manage/manage-spaces.md).
 
 $$$glossary-feature-importance$$$ feature importance
 :   In supervised {{ml}} methods such as {{regression}} and {{classification}}, feature importance indicates the degree to which a specific feature affects a prediction. See [{{regression-cap}} feature importance](/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-regression.md#dfa-regression-feature-importance) and [{{classification-cap}} feature importance](/explore-analyze/machine-learning/data-frame-analytics/ml-dfa-classification.md#dfa-classification-feature-importance).
@@ -302,7 +302,7 @@ $$$glossary-field-reference$$$ field reference
 
 $$$glossary-field$$$ field
 :   1. Key-value pair in a [document](/reference/glossary/index.md#glossary-document). See [Mapping](/manage-data/data-store/mapping.md).
-2. In {{ls}}, this term refers to an [event](/reference/glossary/index.md#glossary-event) property. For example, each event in an apache access log has properties, such as a status code (200, 404), request path ("/", "index.html"), HTTP verb (GET, POST), client IP address, and so on. {{ls}} uses the term "fields" to refer to these properties.
+1. In {{ls}}, this term refers to an [event](/reference/glossary/index.md#glossary-event) property. For example, each event in an apache access log has properties, such as a status code (200, 404), request path ("/", "index.html"), HTTP verb (GET, POST), client IP address, and so on. {{ls}} uses the term "fields" to refer to these properties.
 
 
 $$$glossary-filter-plugin$$$ filter plugin
diff --git a/solutions/security/detect-and-alert/detections-requirements.md b/solutions/security/detect-and-alert/detections-requirements.md
@@ -50,7 +50,7 @@ After changing the `xpack.encryptedSavedObjects.encryptionKey` value and restart
 
 ## Enable and access detections [enable-detections-ui]
 
-To use the Detections feature, it must be enabled, your role must have access to rules and alerts, and your {{kib}} space must have **Data View Management** [feature visibility](/deploy-manage/manage-spaces.md#spaces-control-feature-visibility). If your role doesn’t have the cluster and index privileges needed to enable this feature, you can request someone who has these privileges to visit your {{kib}} space, which will turn it on for you.
+To use the Detections feature, it must be enabled, your role must have access to rules and alerts, and your {{kib}} space must have **Data View Management** [feature visibility](/deploy-manage/manage-spaces.md). If your role doesn’t have the cluster and index privileges needed to enable this feature, you can request someone who has these privileges to visit your {{kib}} space, which will turn it on for you.
 
 ::::{note}
 For instructions about using {{ml}} jobs and rules, refer to [Machine learning job and rule requirements](/solutions/security/advanced-entity-analytics/machine-learning-job-rule-requirements.md).
diff --git a/solutions/security/get-started/data-views-elastic-security.md b/solutions/security/get-started/data-views-elastic-security.md
@@ -50,7 +50,7 @@ The default {{data-source}} is defined by the `securitySolution:defaultIndex` se
 The first time a user visits {{elastic-sec}} within a given {{kib}} [space](/deploy-manage/manage-spaces.md), the default {{data-source}} generates in that space and becomes active.
 
 ::::{note}
-In {{stack}}, your {{kib}} space must have the **Data View Management** [feature visibility](/deploy-manage/manage-spaces.md#spaces-control-feature-visibility) setting enabled for the default {{data-source}} to generate and become active in your space.
+In {{stack}}, your {{kib}} space must have the **Data View Management** [feature visibility](/deploy-manage/manage-spaces.md) setting enabled for the default {{data-source}} to generate and become active in your space.
 ::::
 
 
