Revert dbms.cluster.moveToNextDiscoveryVersion

Author: renetapopova

modules/ROOT/pages/procedures.adoc

@@ -334,20 +334,16 @@ Since Neo4j 5.23, it can be run with the `SERVER MANAGEMENT` privilege.
 It will still run with the `Admin` privilege, but that should be considered deprecated.
 ====
 
-[role=label--enterprise-edition label--new-5.26 label--admin-only]
+[role=label--enterprise-edition label--new-5.26 label--admin-only ]
 [[procedure_dbms_cluster_movetonextdiscoveryversion]]
 === dbms.cluster.moveToNextDiscoveryVersion()
 
 .Details
-[cols="<15s,<85"]
 |===
-| Description
-a| The procedure triggers a switch to the next discovery service version for all known members of the cluster (as listed in the system database and discovery).
+| *Syntax* 3+m| dbms.cluster.moveToNextDiscoveryVersion()
+| *Description* 3+a| The procedure triggers a switch to the next discovery service version for all known members of the cluster (as listed in the system database and discovery).
 For example, if the current member's discovery version is V1_ONLY, it will switch all members to V1_OVER_V2. In case of failure, the user must manually resolve the issue.
-| Signature
-m| dbms.cluster.moveToNextDiscoveryVersion()
-| Mode
-m|DBMS
+| *Mode* 3+| DBMS
 |===
 
 [role=label--enterprise-edition label--new-5.23]