update the tables formatting

Author: renetapopova

modules/ROOT/pages/clustering/databases.adoc

@@ -229,13 +229,13 @@ neo4j@neo4j> DRYRUN REALLOCATE DATABASES;
 [[recreate-databases]]
 == Recreate a database
 
-Neo4j 5.24 introduces the xref:reference/procedures.adoc#procedure_dbms_cluster_recreateDatabase[`dbms.cluster.recreateDatabase()`] procedure, which allows you:
+Neo4j 5.24 introduces the xref:procedures.adoc#procedure_dbms_cluster_recreateDatabase[`dbms.cluster.recreateDatabase()`] procedure, which allows you:
 
 * To change the database store to a specified backup, while keeping all the associated privileges for the database.
 
 * To make your database write-available again after it has been lost (for example, due to a disaster).
 // See xref:clustering/disaster-recovery.adoc[] for more information.
- 
+
 [CAUTION]
 ====
 The recreate procedure works only for real user databases and not for composite databases, or the `system` database.
@@ -304,7 +304,7 @@ If not used stores were more up to date than the used ones, this results in data
 
 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. 
+The number of defined servers cannot exceed the number of total allocations in the desired topology.
 
 [source, shell]
 ----
@@ -341,7 +341,7 @@ There is an option to define a new topology when recreating a database.
 This can be beneficial during a disaster, if enough servers are not available to recreate the database with the original topology.
 When altering the total number of allocations down during a recreation, it is important to remember that the number of seeding servers cannot exceed the number of total allocations of the database.
 This also holds true when using recreate with an empty list of seeders.
-If there are more available servers in the cluster hosting the database than the number of new allocations, the recreation will fail. 
+If there are more available servers in the cluster hosting the database than the number of new allocations, the recreation will fail.
 
 [source, shell]
 ----

modules/ROOT/pages/clustering/monitoring/status-check.adoc

@@ -4,7 +4,7 @@
 [[monitoring-replication]]
 = Monitor replication status
 
-Neo4j 5.24 introduces the xref:reference/procedures.adoc#procedure_dbms_cluster_statusCheck[`dbms.cluster.statusCheck()`] procedure, which can be used to monitor the ability to replicate in clustered databases. 
+Neo4j 5.24 introduces the xref:procedures.adoc#procedure_dbms_cluster_statusCheck[`dbms.cluster.statusCheck()`] procedure, which can be used to monitor the ability to replicate in clustered databases.
 In most cases this means a clustered database is write available.
 The procedure identifies which members of a clustered database are up-to-date and can participate in successful replication.
 Therefore, it is useful in determining the fault tolerance of a clustered database.
@@ -36,7 +36,7 @@ CALL dbms.cluster.statusCheck(databases :: LIST<STRING>, timeoutMilliseconds = n
 | databases           | List<String> | Databases for which the status check should run.
 Providing an empty list runs the status check for all *clustered* databases on that server, i.e. it won't run on singles or secondaries.
 | timeoutMilliseconds | Integer | How long to allow for replication, before returning it was unsuccessful.
-Default value is 1000 milliseconds. 
+Default value is 1000 milliseconds.
 |===
 
 *Returns:*
@@ -53,10 +53,10 @@ The procedure returns a row for all primary members of all the requested databas
 | replicationSuccessful | Boolean      | Indicates if the server (on which the procedure is run) can replicate a transaction.
 | memberStatus          | String       | The status of each primary member.
 | recognisedLeader      | String       | The server id of the perceived leader of each primary member.
-| recognisedLeaderTerm  | Integer      | The term of the perceived leader of each primary member. 
+| recognisedLeaderTerm  | Integer      | The term of the perceived leader of each primary member.
 If the members report different leaders, the one with the highest term should be trusted.
 | requester             | Boolean      | Whether a server is the requester or not.
-| error                 | String       | Contains the error message if one is present. 
+| error                 | String       | Contains the error message if one is present.
 An example of an error is that one or more of the requested databases do not exist on the requester.
 |===