Clean up raw files, fix malformed tables, rm unused subs (#860)

Author: shainaraskas

deploy-manage/autoscaling/autoscaling-deciders.md

@@ -122,7 +122,7 @@ The [autoscaling](../../deploy-manage/autoscaling.md) {{ml}} decider (`ml`) calc
 The {{ml}} decider is enabled for policies governing `ml` nodes.
 
 ::::{note}
-For {{ml}} jobs to open when the cluster is not appropriately scaled, set `xpack.ml.max_lazy_ml_nodes` to the largest number of possible {{ml}} nodes (refer to [Advanced machine learning settings](elasticsearch://reference/elasticsearch/configuration-reference/machine-learning-settings.md#advanced-ml-settings) for more information). In {{ess}}, this is automatically set.
+For {{ml}} jobs to open when the cluster is not appropriately scaled, set `xpack.ml.max_lazy_ml_nodes` to the largest number of possible {{ml}} nodes (refer to [Advanced machine learning settings](elasticsearch://reference/elasticsearch/configuration-reference/machine-learning-settings.md#advanced-ml-settings) for more information). In {{ech}}, this is automatically set.
 ::::
 
 

deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md

@@ -220,9 +220,8 @@ Note the following requirements when you run this API request:
 
 $$$ece-autoscaling-api-example-requirements-table$$$ 
 
-|     |     |     |     |
-| --- | --- | --- | --- |
 |  | `size` | `autoscaling_min` | `autoscaling_max` |
+| --- | --- | --- | --- |
 | data tier | ✓ | ✕ | ✓ |
 | machine learning node | ✕ | ✓ | ✓ |
 | coordinating and master nodes | ✓ | ✕ | ✕ |

deploy-manage/deploy/elastic-cloud.md

@@ -4,7 +4,7 @@ applies_to:
   deployment:
     ess: ga
 mapped_pages:
-  - https://www.elastic.co/guide/en/serverless/current/intro.html#general-what-is-serverless-elastic-differences-between-serverless-projects-and-hosted-deployments-on-ecloud
+  - https://www.elastic.co/guide/en/serverless/current/intro.html
 ---
 
 # Elastic Cloud [intro]
@@ -38,9 +38,8 @@ For more information, refer to [](/deploy-manage/cloud-organization.md).
 You can have multiple hosted deployments and serverless projects in the same {{ecloud}} organization, and each deployment type has its own specificities.
 
 
-|     |     |     |
-| --- | --- | --- |
 | Option | Serverless | Hosted |
+| --- | --- | --- |
 | **Cluster management** | Fully managed by Elastic. | You provision and manage your hosted clusters. Shared responsibility with Elastic. |
 | **Scaling** | Autoscales out of the box. | Manual scaling or autoscaling available for you to enable. |
 | **Upgrades** | Automatically performed by Elastic. | You choose when to upgrade. |

deploy-manage/deploy/elastic-cloud/azure-marketplace-pricing.md

@@ -23,9 +23,8 @@ The pricing plan update enables us to align with market trends and adapt to chan
 
 These pricing changes will apply to customers who are currently paying for Azure Marketplace services in non-USD currencies. If you are paying in USD, your pricing and billing will remain unchanged.
 
-|     |     |     |
-| --- | --- | --- |
 | Currency | Price | Elastic Billing Units for Azure† |
+| --- | --- | --- |
 | USD | 1.00 | $0.10 per 1000 units |
 | AUD | 1.60 | $0.16 per 1000 units |
 | BRL | 5.40 | R$0.54 per 1000 units |

deploy-manage/monitor/cloud-health-perf.md

@@ -74,7 +74,7 @@ deployment:
   ess:
 ```
 
-{{ess}} deployments offer an additional **Performance** page to get further information about your cluster performance. 
+{{ech}} deployments offer an additional **Performance** page to get further information about your cluster performance. 
 
 If you observe issues on search and ingest operations in terms of increased latency or throughput for queries, these might not be directly reported on the **Health** page, unless they are related to shard health or master node availability. 
 

deploy-manage/monitor/orchestrators/ece-proxy-log-fields.md

@@ -13,9 +13,8 @@ These fields *are* subject to change, though the vast majority of them are gener
 ::::
 
 
-|     |     |
-| --- | --- |
 | Field | Description |
+| --- | --- |
 | `proxy_ip` | the IP on the connection, i.e. a proxy IP if the request has been proxied |
 | `request_end` | the time the request was returned in ms since unix epoch |
 | `status_code` | the HTTP status returned to the client |

deploy-manage/reference-architectures.md

@@ -25,9 +25,8 @@ These reference architectures are recommendations and should be adapted to fit y
 
 ## Architectures [reference-architectures-time-series]
 
-|     |     |
+| Architecture | When to use |
 | --- | --- |
-| **Architecture** | **When to use** |
 | [*Hot/Frozen - High Availability*](/deploy-manage/reference-architectures/hotfrozen-high-availability.md)<br>A high availability architecture that is cost optimized for large time-series datasets. | * Have a requirement for cost effective long term data storage (many months or years).<br>* Provide insights and alerts using logs, metrics, traces, or various event types to ensure optimal performance and quick issue resolution for applications.<br>* Apply Machine Learning and Search AI to assist in dealing with the large amount of data.<br>* Deploy an architecture model that allows for maximum flexibility between storage cost and performance.<br> |
 | Additional architectures are on the way.<br>Stay tuned for updates. |  |
 

deploy-manage/reference-architectures/hotfrozen-high-availability.md

@@ -62,9 +62,8 @@ In the links provided above, Elastic has performance tested hardware for each of
 
 This table shows our specific recommendations for nodes in a Hot/Frozen architecture.
 
-|     |     |     |     |     |
+| Type | AWS | Azure | GCP | Physical |
 | --- | --- | --- | --- | --- |
-| **Type** | **AWS** | **Azure** | **GCP** | **Physical** |
 | ![Hot data node](../../images/reference-architectures-hot.png "") | c6gd | f32sv2 | N2 | 16-32 vCPU<br>64 GB RAM<br>2-6 TB NVMe SSD |
 | ![Frozen data node](../../images/reference-architectures-frozen.png "") | i3en | e8dsv4 | N2 | 8 vCPU<br>64 GB RAM<br>6-20+ TB NVMe SSD<br>Depending on days cached |
 | ![Machine learning node](../../images/reference-architectures-machine-learning.png "") | m6gd | f16sv2 | N2 | 16 vCPU<br>64 GB RAM<br>256 GB SSD |

deploy-manage/security/elastic-cloud-static-ips.md

@@ -39,9 +39,8 @@ Not suitable usage of egress static IPs to introduce network controls:
 ## Supported Regions [ec-regions] 
 
 ::::{dropdown} AWS
-|     |     |     |
+| Region | Ingress Static IPs | Egress Static IPs |
 | --- | --- | --- |
-| **Region** | **Ingress Static IPs** | **Egress Static IPs** |
 | aws-af-south-1 | No | Yes |
 | aws-ap-east-1 | No | Yes |
 | aws-ap-northeast-1 | No | Yes |
@@ -67,9 +66,8 @@ Not suitable usage of egress static IPs to introduce network controls:
 
 
 ::::{dropdown} Azure
-|     |     |     |
+| Region | Ingress Static IPs | Egress Static IPs |
 | --- | --- | --- |
-| **Region** | **Ingress Static IPs** | **Egress Static IPs** |
 | azure-australiaeast | Yes | Yes |
 | azure-brazilsouth | Yes | Yes |
 | azure-canadacentral | Yes | Yes |
@@ -91,9 +89,8 @@ Not suitable usage of egress static IPs to introduce network controls:
 
 
 ::::{dropdown} GCP
-|     |     |     |
+| Region | Ingress Static IPs | Egress Static IPs |
 | --- | --- | --- |
-| **Region** | **Ingress Static IPs** | **Egress Static IPs** |
 | gcp-asia-east1 | Yes | No |
 | gcp-asia-northeast1 | Yes | No |
 | gcp-asia-northeast3 | Yes | No |

deploy-manage/security/fips-140-2.md

@@ -111,9 +111,8 @@ FIPS 140-2 compliance dictates that the length of the public keys used for TLS m
 
 $$$comparable-key-strength$$$
 
-|     |     |     |
-| --- | --- | --- |
 | Symmetric Key Algorithm | RSA key Length | ECC key length |
+| --- | --- | --- |
 | `3DES` | 2048 | 224-255 |
 | `AES-128` | 3072 | 256-383 |
 | `AES-256` | 15630 | 512+ |

deploy-manage/security/secure-your-elastic-cloud-enterprise-installation/configure-tls-version.md

@@ -10,9 +10,8 @@ mapped_pages:
 
 Elastic Cloud Enterprise 2.4.0 and later defaults to minimum TLS version 1.2 with a modern set of cipher suites.
 
-|     |     |     |
+| Elastic Cloud Enterprise version | Default minimum TLS version | Default allowed cipher suites |
 | --- | --- | --- |
-| **Elastic Cloud Enterprise version** | **Default minimum TLS version** | **Default allowed cipher suites** |
 | 2.4.0 and later | TLS 1.2 | `ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256` |
 | 2.3.1 and earlier | TLS 1.0 | `CDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:ECDHE-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA` |
 

deploy-manage/users-roles/cloud-organization/user-roles.md

@@ -73,7 +73,7 @@ There are two ways for a user to access {{kib}} instances of an {{ech}} deployme
 
 The following table shows the default mapping:
 
-|  Cloud role  |  Cloud API `role_id`  |  Stack role   |
+| Cloud role | Cloud API `role_id` | Stack role |
 | --- | --- | --- |
 | Organization owner | `organization-admin` | superuser |
 | Billing admin | `billing-admin` | none |