Remove redundant empty lines from documentation

docs/src/main/sphinx/admin/event-listeners-http.md

@@ -25,7 +25,6 @@ You need to perform the following steps:
 - Detail the events to send in the {ref}`http-event-listener-configuration` section.
 
 (http-event-listener-configuration)=
-
 ## Configuration
 
 To configure the HTTP event listener plugin, create an event listener properties
@@ -104,7 +103,6 @@ event-listener.config-files=etc/http-event-listener.properties,...
 :::
 
 (http-event-listener-custom-headers)=
-
 ### Custom HTTP headers
 
 Providing custom HTTP headers is a useful mechanism for sending metadata along with

docs/src/main/sphinx/admin/event-listeners-mysql.md

@@ -24,7 +24,6 @@ You need to perform the following steps:
   Port 3306 is the default port.
 
 (mysql-event-listener-configuration)=
-
 ## Configuration
 
 To configure the MySQL event listener plugin, create an event listener properties
@@ -68,4 +67,4 @@ string, user, catalog, and others with information about the query processing.
   - Description
 * - `mysql-event-listener.db.url`
   - JDBC connection URL to the database including credentials
-:::
+:::

docs/src/main/sphinx/admin/fault-tolerant-execution.md

@@ -85,7 +85,6 @@ Find further related properties in [](/admin/properties), specifically in
 [](/admin/properties-resource-management) and [](/admin/properties-exchange).
 
 (fte-retry-policy)=
-
 ## Retry policy
 
 The `retry-policy` configuration property designates whether Trino retries
@@ -376,7 +375,6 @@ fault-tolerant execution:
 :::
 
 (fte-exchange-manager)=
-
 ## Exchange manager
 
 Exchange spooling is responsible for storing and managing spooled data for
@@ -519,7 +517,6 @@ lifecycle rule to automatically expire abandoned objects in the event of a node
 crash.
 
 (fte-exchange-aws-s3)=
-
 #### AWS S3
 
 The following example `exchange-manager.properties` configuration specifies an
@@ -547,7 +544,6 @@ exchange.base-directories=s3://exchange-spooling-bucket-1,s3://exchange-spooling
 ```
 
 (fte-exchange-azure-blob)=
-
 #### Azure Blob Storage
 
 The following example `exchange-manager.properties` configuration specifies an
@@ -562,7 +558,6 @@ exchange.azure.connection-string=connection-string
 ```
 
 (fte-exchange-gcs)=
-
 #### Google Cloud Storage
 
 To enable exchange spooling on GCS in Trino, change the request endpoint to the
@@ -588,7 +583,6 @@ exchange.gcs.json-key-file-path=/path/to/gcs_keyfile.json
 ```
 
 (fte-exchange-hdfs)=
-
 #### HDFS
 
 The following `exchange-manager.properties` configuration example specifies HDFS
@@ -601,7 +595,6 @@ hdfs.config.resources=/usr/lib/hadoop/etc/hadoop/core-site.xml
 ```
 
 (fte-exchange-local-filesystem)=
-
 #### Local filesystem storage
 
 The following example `exchange-manager.properties` configuration specifies a

docs/src/main/sphinx/admin/properties-node-scheduler.md

@@ -90,7 +90,6 @@ across all worker nodes. Setting it too high may increase query
 latency and increase CPU usage on the coordinator.
 
 (node-scheduler-policy)=
-
 ## `node-scheduler.policy`
 
 - **Type:** {ref}`prop-type-string`

docs/src/main/sphinx/admin/properties-resource-management.md

@@ -1,7 +1,6 @@
 # Resource management properties
 
 (prop-resource-query-max-cpu-time)=
-
 ## `query.max-cpu-time`
 
 - **Type:** {ref}`prop-type-duration`
@@ -11,7 +10,6 @@ This is the max amount of CPU time that a query can use across the entire
 cluster. Queries that exceed this limit are killed.
 
 (prop-resource-query-max-memory-per-node)=
-
 ## `query.max-memory-per-node`
 
 - **Type:** {ref}`prop-type-data-size`
@@ -35,7 +33,6 @@ Does not apply for queries with task level retries enabled (`retry-policy=TASK`)
 :::
 
 (prop-resource-query-max-memory)=
-
 ## `query.max-memory`
 
 - **Type:** {ref}`prop-type-data-size`
@@ -58,7 +55,6 @@ Does not apply for queries with task level retries enabled (`retry-policy=TASK`)
 :::
 
 (prop-resource-query-max-total-memory)=
-
 ## `query.max-total-memory`
 
 - **Type:** {ref}`prop-type-data-size`
@@ -79,7 +75,6 @@ Does not apply for queries with task level retries enabled (`retry-policy=TASK`)
 :::
 
 (prop-resource-memory-heap-headroom-per-node)=
-
 ## `memory.heap-headroom-per-node`
 
 - **Type:** {ref}`prop-type-data-size`
@@ -95,7 +90,6 @@ maximum heap size in the JVM on the node. See {ref}`jvm-config`.
 :::
 
 (prop-resource-exchange-deduplication-buffer-size)=
-
 ## `exchange.deduplication-buffer-size`
 
 - **Type:** {ref}`prop-type-data-size`

docs/src/main/sphinx/admin/properties-write-partitioning.md

@@ -1,7 +1,6 @@
 # Write partitioning properties
 
 (preferred-write-partitioning)=
-
 ## `use-preferred-write-partitioning`
 
 - **Type:** {ref}`prop-type-boolean`

docs/src/main/sphinx/admin/properties-writer-scaling.md

@@ -21,7 +21,6 @@ Enable writer scaling by dynamically increasing the number of writer tasks on
 the cluster.
 
 (prop-task-scale-writers)=
-
 ## `task.scale-writers.enabled`
 
 - **Type:** {ref}`prop-type-boolean`

docs/src/main/sphinx/admin/properties.md

@@ -39,13 +39,11 @@ allowed values and syntax. Additional limitations apply on a per-property basis,
 and disallowed values result in a validation error.
 
 (prop-type-boolean)=
-
 ### `boolean`
 
 The properties of type `boolean` support two values, `true` or `false`.
 
 (prop-type-data-size)=
-
 ### `data size`
 
 The properties of type `data size` support values that describe an amount of
@@ -64,15 +62,13 @@ The `data size` type supports the following units:
 - `PB`: Petabytes
 
 (prop-type-double)=
-
 ### `double`
 
 The properties of type `double` support numerical values including decimals,
 such as `1.6`. `double` type values can be negative, if supported by the
 specific property.
 
 (prop-type-duration)=
-
 ### `duration`
 
 The properties of type `duration` support values describing an
@@ -97,7 +93,6 @@ These are handled as a fractional value of the specified unit. For example, the
 value `1.5m` equals one and a half minutes, or 90 seconds.
 
 (prop-type-integer)=
-
 ### `integer`
 
 The properties of type `integer` support whole numeric values, such as `5`
@@ -108,7 +103,6 @@ are not supported.
 Some `integer` type properties enforce their own minimum and maximum values.
 
 (prop-type-string)=
-
 ### `string`
 
 The properties of type `string` support a set of values that consist of a

docs/src/main/sphinx/admin/resource-groups.md

@@ -137,7 +137,6 @@ are reflected automatically for incoming queries.
 - `subGroups` (optional): list of sub-groups.
 
 (scheduleweight-example)=
-
 ### Scheduling weight example
 
 Schedule weighting is a method of assigning a priority to a resource. Sub-groups

docs/src/main/sphinx/admin/web-interface.md

@@ -8,7 +8,6 @@ HTTP or HTTPS, using the corresponding port number specified in the coordinator
 The Web UI can be disabled entirely with the `web-ui.enabled` property.
 
 (web-ui-authentication)=
-
 ## Authentication
 
 The Web UI requires users to authenticate. If Trino is not configured to require
@@ -50,7 +49,6 @@ The following Web UI authentication types are also supported:
 For these authentication types, the username is defined by {doc}`/security/user-mapping`.
 
 (web-ui-overview)=
-
 ## User interface overview
 
 The main page has a list of queries along with information like unique query ID, query text,

docs/src/main/sphinx/client/cli.md

@@ -18,7 +18,6 @@ newer. Older versions typically work, but only a subset is regularly tested.
 Versions before 350 are not supported.
 
 (cli-installation)=
-
 ## Installation
 
 Download {maven_download}`cli`, rename it to `trino`, make it executable with
@@ -214,7 +213,6 @@ to find out URL parameter names. For example:
 ```
 
 (cli-tls)=
-
 ## TLS/HTTPS
 
 Trino is typically available with an HTTPS URL. This means that all network
@@ -271,14 +269,12 @@ certificate usage:
 :::
 
 (cli-authentication)=
-
 ## Authentication
 
 The Trino CLI supports many {doc}`/security/authentication-types` detailed in
 the following sections:
 
 (cli-username-password-auth)=
-
 ### Username and password authentication
 
 Username and password authentication is typically configured in a cluster using
@@ -308,7 +304,6 @@ to provide a password to connect with the CLI.
 ```
 
 (cli-external-sso-auth)=
-
 ### External authentication - SSO
 
 Use the `--external-authentication` option for browser-based SSO
@@ -332,7 +327,6 @@ The detailed behavior is as follows:
 - Expired tokens force you to log in again.
 
 (cli-certificate-auth)=
-
 ### Certificate authentication
 
 Use the following CLI arguments to connect to a cluster that uses
@@ -357,14 +351,12 @@ authentication with the CLI; instead, they control the client's trust of the
 server's certificate.
 
 (cli-jwt-auth)=
-
 ### JWT authentication
 
 To access a Trino cluster configured to use {doc}`/security/jwt`, use the
 `--access-token=<token>` option to pass a JWT to the server.
 
 (cli-kerberos-auth)=
-
 ### Kerberos authentication
 
 The Trino CLI can connect to a Trino cluster that has {doc}`/security/kerberos`
@@ -415,7 +407,6 @@ The following table lists the available options for Kerberos authentication:
 :::
 
 (cli-kerberos-debug)=
-
 #### Additional Kerberos debugging information
 
 You can enable additional Kerberos debugging information for the Trino CLI
@@ -450,7 +441,6 @@ such as `more` or [pspg](https://github.com/okbob/pspg),
 or it can be set to an empty value to completely disable pagination.
 
 (cli-history)=
-
 ## History
 
 The CLI keeps a history of your previously used commands. You can access your
@@ -600,7 +590,6 @@ SELECT nationkey, name, region FROM tpch.sf1.nation LIMIT 3
 ```
 
 (cli-output-format)=
-
 ## Output formats
 
 The Trino CLI provides the options `--output-format`
@@ -645,7 +634,6 @@ and `CSV` in non-interactive mode.
 :::
 
 (cli-troubleshooting)=
-
 ## Troubleshooting
 
 If something goes wrong, you see an error message:

docs/src/main/sphinx/client/jdbc.md

@@ -86,7 +86,6 @@ classname is required.
 :::
 
 (jdbc-java-connection)=
-
 ## Connection parameters
 
 The driver supports various parameters that may be set as URL parameters,
@@ -112,7 +111,6 @@ while others are specified using properties. However, the same parameter
 may not be specified using both methods.
 
 (jdbc-parameter-reference)=
-
 ## Parameter reference
 
 :::{list-table}

docs/src/main/sphinx/connector/accumulo.md

@@ -661,7 +661,6 @@ WITH (
 ```
 
 (accumulo-type-mapping)=
-
 ## Type mapping
 
 Because Trino and Accumulo each support types that the other does not, this
@@ -761,7 +760,6 @@ mapping types following this table:
 No other types are supported
 
 (accumulo-sql-support)=
-
 ## SQL support
 
 The connector provides read and write access to data and metadata in

docs/src/main/sphinx/connector/bigquery.md

@@ -213,7 +213,6 @@ a few caveats:
 :::
 
 (bigquery-type-mapping)=
-
 ## Type mapping
 
 Because Trino and BigQuery each support types that the other does not, this
@@ -336,7 +335,6 @@ you can send query `SELECT * example_view$view_definition` to see the SQL
 which defines view in BigQuery.
 
 (bigquery-special-columns)=
-
 ## Special columns
 
 In addition to the defined columns, the BigQuery connector exposes
@@ -367,7 +365,6 @@ Two special partitions `__NULL__` and `__UNPARTITIONED__` are not supported.
 :::
 
 (bigquery-sql-support)=
-
 ## SQL support
 
 The connector provides read and write access to data and metadata in the
@@ -390,7 +387,6 @@ the following features:
 ```
 
 (bigquery-fte-support)=
-
 ## Fault-tolerant execution support
 
 The connector supports {doc}`/admin/fault-tolerant-execution` of query
@@ -402,7 +398,6 @@ The connector provides specific {doc}`table functions </functions/table>` to
 access BigQuery.
 
 (bigquery-query-function)=
-
 ### `query(varchar) -> table`
 
 The `query` function allows you to query the underlying BigQuery directly. It