Fix more whitespace issues around enum tables.

docs/cloud-providers/aws-sdk.md

@@ -40,6 +40,7 @@ with the naming guidelines for RPC client spans.
 **[2]:** This is the logical name of the service from the RPC interface perspective, which can be different from the name of any implementing class. The `code.namespace` attribute may be used to store the latter (despite the attribute name, it may include a class name; e.g., class with method actually executing the call on the server side, RPC client stub class on the client side).
 
 
+
 `rpc.system` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
 
 | Value  | Description | Stability |
@@ -49,7 +50,7 @@ with the naming guidelines for RPC client spans.
 | `dotnet_wcf` | .NET WCF | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `apache_dubbo` | Apache Dubbo | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `connect_rpc` | Connect RPC | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
- 
+
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 <!-- prettier-ignore-end -->

docs/database/cassandra.md

@@ -40,6 +40,7 @@ described on this page.
 **[4]:** If a database operation involved multiple network calls (for example retries), the address of the last contacted node SHOULD be used.
 
 
+
 `db.cassandra.consistency_level` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
 
 | Value  | Description | Stability |
@@ -55,7 +56,7 @@ described on this page.
 | `any` | any | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `serial` | serial | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `local_serial` | local_serial | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
- 
+
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 

docs/database/cosmosdb.md

@@ -40,13 +40,15 @@ Cosmos DB instrumentation includes call-level (public API) surface spans and net
    Default value is "NS".
 
 
+
 `db.cosmosdb.connection_mode` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
 
 | Value  | Description | Stability |
 |---|---|---|
 | `gateway` | Gateway (HTTP) connections mode | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `direct` | Direct connection. | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
- `db.cosmosdb.operation_type` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
+
+`db.cosmosdb.operation_type` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
 
 | Value  | Description | Stability |
 |---|---|---|
@@ -65,7 +67,7 @@ Cosmos DB instrumentation includes call-level (public API) surface spans and net
 | `Batch` | batch | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `QueryPlan` | query_plan | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `ExecuteJavaScript` | execute_javascript | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
- 
+
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 

docs/database/database-metrics.md

@@ -100,6 +100,7 @@ If a database operation involved multiple network calls (for example retries), t
 **[9]:** When observed from the client side, and when communicating through an intermediary, `server.address` SHOULD represent the server address behind any intermediaries, for example proxies, if it's available.
 
 
+
 `db.system` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
 
 | Value  | Description | Stability |
@@ -156,12 +157,13 @@ If a database operation involved multiple network calls (for example retries), t
 | `clickhouse` | ClickHouse | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `spanner` | Cloud Spanner | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `trino` | Trino | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
- `error.type` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
+
+`error.type` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
 
 | Value  | Description | Stability |
 |---|---|---|
 | `_OTHER` | A fallback error value to be used when the instrumentation doesn't define a custom value. | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
- 
+
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
@@ -193,13 +195,14 @@ This metric is [required][MetricRequired].
 |---|---|---|---|---|---|
 | [`db.client.connections.pool.name`](/docs/attributes-registry/db.md) | string | The name of the connection pool; unique within the instrumented application. In case the connection pool implementation doesn't provide a name, instrumentation should use a combination of `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | [`db.client.connections.state`](/docs/attributes-registry/db.md) | string | The state of a connection in the pool | `idle` | `Required` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
+
 `db.client.connections.state` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
 
 | Value  | Description | Stability |
 |---|---|---|
 | `idle` | idle | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `used` | used | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
- 
+
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 ### Metric: `db.client.connection.idle.max`

docs/database/database-spans.md

@@ -114,6 +114,7 @@ If a database operation involved multiple network calls (for example retries), t
 If a parameter has no name and instead is referenced only by index, then `<key>` SHOULD be the 0-based index.
 
 
+
 `db.system` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
 
 | Value  | Description | Stability |
@@ -170,12 +171,13 @@ If a parameter has no name and instead is referenced only by index, then `<key>`
 | `clickhouse` | ClickHouse | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `spanner` | Cloud Spanner | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 | `trino` | Trino | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
- `error.type` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
+
+`error.type` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
 
 | Value  | Description | Stability |
 |---|---|---|
 | `_OTHER` | A fallback error value to be used when the instrumentation doesn't define a custom value. | ![Stable](https://img.shields.io/badge/-stable-lightgreen) |
- 
+
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->