Improve the 5th level headings (#2124) (#2129)

Author: NataliaIvakina

modules/ROOT/pages/clustering/databases.adoc

@@ -320,35 +320,35 @@ If not used stores were more up to date than the used ones, this results in data
 ====
 
 [[specified-servers]]
-===== Specified servers
+Specified servers::
 
 You can specify a set of available servers.
 The stores on all allocations will be synchronized to the most up-to-date store from the defined servers.
 The number of defined servers cannot exceed the number of total allocations in the desired topology.
-
++
 [source, shell]
 ----
 CALL dbms.cluster.recreateDatabase("neo4j", {seedingServers: ["serverId1", "serverId2", "serverId3"]});
 ----
 
 [[undefined-servers]]
-===== Undefined servers
+Undefined servers::
 
 If you provide an empty list of seeding servers and do not specify a `seedURI`, Neo4j automatically selects all available allocations of the database as seeders.
 The store will be replaced by the most up-to-date seeder available in the cluster.
-
++
 [source, shell]
 ----
 CALL dbms.cluster.recreateDatabase("neo4j", {seedingServers: []});
 ----
 
 [[undefined-servers-backup]]
-===== Undefined servers with fallback backup
+Undefined servers with fallback backup::
 
 If both an empty list of seeding servers and a `seedURI` are provided, Neo4j finds all available allocations of the database and use those as seeders.
 However, if no available servers can be found, the database is recreated based on the backup or the dump defined by the URI.
 This means the store is replaced by the most up-to-date seeder if available; otherwise, the backup is used.
-
++
 [source, shell]
 ----
 CALL dbms.cluster.recreateDatabase("neo4j", {seedingServers: [], seedURI: "s3:/myBucket/myBackup.backup"});
@@ -570,28 +570,27 @@ CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 'azb://myStorageAcco
 Starting from Neo4j 2025.01, the `CloudSeedProvider` supports seeding up to a specific date or transaction ID using the `seedRestoreUntil` option.
 
 [role=label--new-2025.01]
-===== Seed up to a specific date
+Seed up to a specific date::
 
 To seed up to a specific date, you need to pass the differential backup, which contains the data up to that date.
-
-
++
 [source,shell]
 ----
 CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup', seedRestoreUntil: datetime("2019-06-01T18:40:32.142+0100") }
 ----
-
++
 This will seed the database with transactions committed before the provided timestamp.
 
 [role=label--new-2025.01]
-===== Seed up to a specific transaction ID
+Seed up to a specific transaction ID::
 
 To seed up to a specific transaction ID, you need to pass the differential backup that contains the data up to that transaction ID.
-
++
 [source,shell]
 ----
 CREATE DATABASE foo OPTIONS { existingData: 'use', seedURI: 's3:/myBucket/myBackup.backup', seedRestoreUntil: 123 }
 ----
-
++
 This will seed the database with transactions up to, but not including transaction 123.
 
 [role=label--deprecated]