fix table formatting

shainaraskas · shainaraskas · commit fff8a78220f7 · 2025-03-20T17:15:41.000-04:00
diff --git a/deploy-manage/autoscaling/autoscaling-in-ece-and-ech.md b/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 | ✓ | ✕ | ✕ |
diff --git a/deploy-manage/deploy/elastic-cloud/azure-marketplace-pricing.md b/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 |
diff --git a/deploy-manage/monitor/orchestrators/ece-proxy-log-fields.md b/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 |
diff --git a/deploy-manage/reference-architectures.md b/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. |  |
 
diff --git a/deploy-manage/reference-architectures/hotfrozen-high-availability.md b/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 |
diff --git a/deploy-manage/security/elastic-cloud-static-ips.md b/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 |
diff --git a/deploy-manage/security/fips-140-2.md b/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+ |
diff --git a/deploy-manage/security/secure-your-elastic-cloud-enterprise-installation/configure-tls-version.md b/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` |
 
diff --git a/deploy-manage/users-roles/cloud-organization/user-roles.md b/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 |
diff --git a/explore-analyze/machine-learning/nlp/ml-nlp-lang-ident.md b/explore-analyze/machine-learning/nlp/ml-nlp-lang-ident.md
@@ -20,9 +20,8 @@ The longer the text passed into the {{lang-ident}} model, the more accurately th
 
 The table below contains the ISO codes and the English names of the languages that {{lang-ident}} supports. If a language has a 2-letter `ISO 639-1` code, the table contains that identifier. Otherwise, the 3-letter `ISO 639-2` code is used. The `Latn` subtag indicates that the language is transliterated into Latin script.
 
-|     |     |     |     |     |     |
-| --- | --- | --- | --- | --- | --- |
 | Code | Language | Code | Language | Code | Language |
+| --- | --- | --- | --- | --- | --- |
 | af | Afrikaans | hr | Croatian | pa | Punjabi |
 | am | Amharic | ht | Haitian | pl | Polish |
 | ar | Arabic | hu | Hungarian | ps | Pashto |
diff --git a/explore-analyze/numeral-formatting.md b/explore-analyze/numeral-formatting.md
@@ -32,9 +32,8 @@ The display of these patterns is affected by the [advanced setting](kibana://ref
 
 Most basic examples:
 
-|     |     |     |     |
+| Input | Pattern | Locale | Output |
 | --- | --- | --- | --- |
-| **Input*** | ***Pattern*** | ***Locale*** | ***Output** |
 | 10000.23 | 0,0 | en (English) | 10,000 |
 | 10000.23 | 0.0 | en (English) | 10000.2 |
 | 10000.23 | 0,0.0 | fr (French) | 10 000,2 |
@@ -50,9 +49,8 @@ By adding the `%` symbol to any of the previous patterns, the value is multiplie
 
 The default percentage formatter in {{kib}} is `0,0.[000]%`, which shows up to three decimal places.
 
-|     |     |     |     |
+| Input | Pattern | Locale | Output |
 | --- | --- | --- | --- |
-| **Input*** | ***Pattern*** | ***Locale*** | ***Output** |
 | 0.43 | 0,0.[000]% | en (English) | 43.00% |
 | 0.43 | 0,0.[000]% | fr (French) | 43,00% |
 | 1 | 0% | en (English) | 100% |
@@ -80,9 +78,8 @@ The bytes and bits formatters will shorten the input by adding a suffix like `GB
 
 Suffixes are not localized with this formatter.
 
-|     |     |     |     |
+| Input | Pattern | Locale | Output |
 | --- | --- | --- | --- |
-| **Input*** | ***Pattern*** | ***Locale*** | ***Output** |
 | 2000 | 0.00b | en (English) | 1.95KB |
 | 2000 | 0.00bb | en (English) | 1.95KiB |
 | 2000 | 0.00bd | en (English) | 2.00kB |
@@ -95,9 +92,8 @@ Suffixes are not localized with this formatter.
 
 Currency formatting is limited in {{kib}} due to the limitations of the pattern syntax. To enable currency formatting, use the symbol `$` in the pattern syntax. The number formatting locale will affect the result.
 
-|     |     |     |     |
+| Input | Pattern | Locale | Output |
 | --- | --- | --- | --- |
-| **Input*** | ***Pattern*** | ***Locale*** | ***Output** |
 | 1000.234 | $0,0.00 | en (English) | $1,000.23 |
 | 1000.234 | $0,0.00 | fr (French) | €1 000,23 |
 | 1000.234 | $0,0.00 | chs (Simplified Chinese) | ¥1,000.23 |
@@ -107,9 +103,8 @@ Currency formatting is limited in {{kib}} due to the limitations of the pattern
 
 Converts a value in seconds to display hours, minutes, and seconds.
 
-|     |     |     |
+| Input | Pattern | Output |
 | --- | --- | --- |
-| **Input*** | ***Pattern*** | ***Output** |
 | 25 | 00:00:00 | 0:00:25 |
 | 25 | 00:00 | 0:00:25 |
 | 238 | 00:00:00 | 0:03:58 |
@@ -121,9 +116,8 @@ Converts a value in seconds to display hours, minutes, and seconds.
 
 The `a` pattern will look for the shortest abbreviation for your number, and use a locale-specific display for it. The abbreviations `aK`, `aM`, `aB`, and `aT` can indicate that the number should be abbreviated to a specific order of magnitude.
 
-|     |     |     |     |
+| Input | Pattern | Locale | Output |
 | --- | --- | --- | --- |
-| **Input*** | ***Pattern*** | ***Locale*** | ***Output** |
 | 2000000000 | 0.00a | en (English) | 2.00b |
 | 2000000000 | 0.00a | ja (Japanese) | 2.00十億 |
 | -5444333222111 | 0,0 aK | en (English) | -5,444,333,222 k |
@@ -136,9 +130,8 @@ The `a` pattern will look for the shortest abbreviation for your number, and use
 
 The `o` pattern will display a locale-specific positional value like `1st` or `2nd`. This pattern has limited support for localization, especially in languages with multiple forms, such as German.
 
-|     |     |     |     |
+| Input | Pattern | Locale | Output |
 | --- | --- | --- | --- |
-| **Input*** | ***Pattern*** | ***Locale*** | ***Output** |
 | 3 | 0o | en (English) | 3rd |
 | 34 | 0o | en (English) | 34th |
 | 3 | 0o | es (Spanish) | 2er |
@@ -149,9 +142,8 @@ The `o` pattern will display a locale-specific positional value like `1st` or `2
 
 These number formats, combined with the previously described patterns, produce the complete set of options for numeral formatting. The output here is all for the `en` locale.
 
-|     |     |     |
+| Input | Pattern | Output |
 | --- | --- | --- |
-| **Input*** | ***Pattern*** | ***Output** |
 | 10000 | 0,0.0000 | 10,000.0000 |
 | 10000.23 | 0,0 | 10,000 |
 | -10000 | 0,0.0 | -10,000.0 |
diff --git a/explore-analyze/query-filter/languages/esql-rest.md b/explore-analyze/query-filter/languages/esql-rest.md
@@ -63,9 +63,8 @@ The URL parameter takes precedence over the HTTP headers. If neither is specifie
 ::::
 
 
-|     |     |     |
+| `format` | HTTP header | Description |
 | --- | --- | --- |
-| **`format`** | **HTTP header** | **Description** |
 | Human readable |
 | `csv` | `text/csv` | [Comma-separated values](https://en.wikipedia.org/wiki/Comma-separated_values) |
 | `json` | `application/json` | [JSON](https://www.json.org/) (JavaScript Object Notation) human-readable format |
diff --git a/explore-analyze/query-filter/languages/sql-data-types.md b/explore-analyze/query-filter/languages/sql-data-types.md
@@ -8,9 +8,8 @@ mapped_pages:
 
 # Data Types [sql-data-types]
 
-|     |     |     |     |
+| {{es}} type | Elasticsearch SQL type | SQL type | SQL precision |
 | --- | --- | --- | --- |
-| **{{es}} type** | **Elasticsearch SQL type** | **SQL type** | **SQL precision** |
 | Core types |
 | [`null`](elasticsearch://reference/elasticsearch/mapping-reference/null-value.md) | `null` | NULL | 0 |
 | [`boolean`](elasticsearch://reference/elasticsearch/mapping-reference/boolean.md) | `boolean` | BOOLEAN | 1 |
@@ -47,9 +46,8 @@ In addition to the types above, Elasticsearch SQL also supports at *runtime* SQL
 $$$es-sql-only-types$$$
 The table below indicates these types:
 
-|     |     |
+| SQL type | SQL precision |
 | --- | --- |
-| **SQL type** | **SQL precision** |
 | `date` | 29 |
 | `time` | 18 |
 | `interval_year` | 7 |
diff --git a/explore-analyze/query-filter/languages/sql-functions-aggs.md b/explore-analyze/query-filter/languages/sql-functions-aggs.md
@@ -167,9 +167,8 @@ SELECT FIRST(a) FROM t
 
 will result in:
 
-|     |
+| FIRST(a) |
 | --- |
-| **FIRST(a)** |
 | 1 |
 
 and
@@ -180,9 +179,8 @@ SELECT FIRST(a, b) FROM t
 
 will result in:
 
-|     |
+| FIRST(a, b) |
 | --- |
-| **FIRST(a, b)** |
 | 100 |
 
 ```sql
@@ -288,9 +286,8 @@ SELECT LAST(a) FROM t
 
 will result in:
 
-|     |
+| LAST(a) |
 | --- |
-| **LAST(a)** |
 | 200 |
 
 and
@@ -301,9 +298,8 @@ SELECT LAST(a, b) FROM t
 
 will result in:
 
-|     |
+| LAST(a, b) |
 | --- |
-| **LAST(a, b)** |
 | 2 |
 
 ```sql
diff --git a/explore-analyze/query-filter/languages/sql-functions-datetime.md b/explore-analyze/query-filter/languages/sql-functions-datetime.md
@@ -18,9 +18,8 @@ A common requirement when dealing with date/time in general revolves around the
 
 The table below shows the mapping between {{es}} and Elasticsearch SQL:
 
-|     |     |
+| {{es}} | Elasticsearch SQL |
 | --- | --- |
-| **{{es}}** | **Elasticsearch SQL** |
 | Index/Table datetime math |
 | `<index-{now/M{YYYY.MM}}>` |
 | Query date/time math |
@@ -41,9 +40,8 @@ Elasticsearch SQL accepts also the plural for each time unit (e.g. both `YEAR` a
 
 Example of the possible combinations below:
 
-|     |     |
+| Interval | Description |
 | --- | --- |
-| **Interval** | **Description** |
 | `INTERVAL '1-2' YEAR TO MONTH` | 1 year and 2 months |
 | `INTERVAL '3 4' DAYS TO HOURS` | 3 days and 4 hours |
 | `INTERVAL '5 6:12' DAYS TO MINUTES` | 5 days, 6 hours and 12 minutes |
diff --git a/explore-analyze/query-filter/languages/sql-index-patterns.md b/explore-analyze/query-filter/languages/sql-index-patterns.md
@@ -88,9 +88,8 @@ Notice how now `emp%` does not match any tables because `%`, which means match z
 
 In a nutshell, the differences between the two type of patterns are:
 
-|     |     |     |
+| Feature | Multi index | SQL `LIKE` |
 | --- | --- | --- |
-| **Feature** | **Multi index** | **SQL `LIKE`** |
 | Type of quoting | `"` | `'` |
 | Inclusion | Yes | Yes |
 | Exclusion | Yes | No |
diff --git a/explore-analyze/query-filter/languages/sql-lexical-structure.md b/explore-analyze/query-filter/languages/sql-lexical-structure.md
@@ -126,9 +126,8 @@ To escape single or double quotes, one needs to use that specific quote one more
 
 A few characters that are not alphanumeric have a dedicated meaning different from that of an operator. For completeness these are specified below:
 
-|     |     |
+| Char | Description |
 | --- | --- |
-| **Char** | **Description** |
 | `*` | The asterisk (or wildcard) is used in some contexts to denote all fields for a table. Can be also used as an argument to some aggregate functions. |
 | `,` | Commas are used to enumerate the elements of a list. |
 | `.` | Used in numeric constants or to separate identifiers qualifiers (catalog, table, column names, etc…​). |
@@ -141,9 +140,8 @@ Most operators in Elasticsearch SQL have the same precedence and are left-associ
 
 The following table indicates the supported operators and their precedence (highest to lowest);
 
-|     |     |     |
+| Operator/Element | Associativity | Description |
 | --- | --- | --- |
-| **Operator/Element** | **Associativity** | **Description** |
 | `.` | left | qualifier separator |
 | `::` | left | PostgreSQL-style type cast |
 | `+ -` | right | unary plus and minus (numeric literal sign) |
diff --git a/explore-analyze/query-filter/languages/sql-like-rlike-operators.md b/explore-analyze/query-filter/languages/sql-like-rlike-operators.md
@@ -95,9 +95,8 @@ When using `LIKE`/`RLIKE`, do consider using [full-text search predicates](sql-f
 
 For example:
 
-|     |     |
+| LIKE/RLIKE | QUERY/MATCH |
 | --- | --- |
-| **LIKE/RLIKE** | **QUERY/MATCH** |
 | ``foo LIKE 'bar'`` | ``MATCH(foo, 'bar')`` |
 | ``foo LIKE 'bar' AND tar LIKE 'goo'`` | ``MATCH('foo^2, tar^5', 'bar goo', 'operator=and')`` |
 | ``foo LIKE 'barr'`` | ``QUERY('foo: bar~')`` |
diff --git a/explore-analyze/query-filter/languages/sql-rest-format.md b/explore-analyze/query-filter/languages/sql-rest-format.md
@@ -17,9 +17,8 @@ The URL parameter takes precedence over the `Accept` HTTP header. If neither is
 ::::
 
 
-|     |     |     |
+| format | `Accept` HTTP header | Description |
 | --- | --- | --- |
-| **format** | **`Accept` HTTP header** | **Description** |
 | Human Readable |
 | `csv` | `text/csv` | [Comma-separated values](https://en.wikipedia.org/wiki/Comma-separated_values) |
 | `json` | `application/json` | [JSON](https://www.json.org/) (JavaScript Object Notation) human-readable format |
diff --git a/explore-analyze/query-filter/languages/sql-syntax-reserved.md b/explore-analyze/query-filter/languages/sql-syntax-reserved.md
@@ -16,9 +16,8 @@ The following table lists all of the keywords that are reserved in Elasticsearch
 SELECT "AS" FROM index
 ```
 
-|     |     |     |
+| Keyword | SQL:2016 | SQL-92 |
 | --- | --- | --- |
-| **Keyword** | **SQL:2016** | **SQL-92** |
 | `ALL` | reserved | reserved |
 | `AND` | reserved | reserved |
 | `ANY` | reserved | reserved |
diff --git a/reference/index.md b/reference/index.md
diff --git a/reference/ingestion-tools/fleet/add-fleet-server-kubernetes.md b/reference/ingestion-tools/fleet/add-fleet-server-kubernetes.md
diff --git a/reference/ingestion-tools/fleet/elastic-agent-standalone-logging-config.md b/reference/ingestion-tools/fleet/elastic-agent-standalone-logging-config.md
diff --git a/reference/ingestion-tools/fleet/fleet-server-scalability.md b/reference/ingestion-tools/fleet/fleet-server-scalability.md
diff --git a/reference/ingestion-tools/fleet/install-elastic-agents.md b/reference/ingestion-tools/fleet/install-elastic-agents.md
diff --git a/reference/ingestion-tools/fleet/scaling-on-kubernetes.md b/reference/ingestion-tools/fleet/scaling-on-kubernetes.md
diff --git a/solutions/observability/apps/collect-application-data.md b/solutions/observability/apps/collect-application-data.md
diff --git a/solutions/observability/infra-and-hosts/get-started-with-universal-profiling.md b/solutions/observability/infra-and-hosts/get-started-with-universal-profiling.md
