Added the description move to next discovery version

Author: akarasavov

modules/ROOT/pages/clustering/setup/discovery.adoc

@@ -272,7 +272,7 @@ One possible reason for failure is that some servers might have had inconsistent
 +
 [source,cypher]
 ----
-CALL internal.dbms.cluster.moveToNextDiscoveryVersion();
+CALL dbms.cluster.moveToNextDiscoveryVersion();
 ----
 . Check the state again:
 +
@@ -297,7 +297,7 @@ If they are not, wait and try again till matching.
 +
 [source,cypher]
 ----
-CALL internal.dbms.cluster.moveToNextDiscoveryVersion();
+CALL dbms.cluster.moveToNextDiscoveryVersion();
 ----
 . Check that transition to `V2_OVER_V1` was successful:
 +
@@ -322,7 +322,7 @@ If they are not, wait and try again till matching.
 +
 [source,cypher]
 ----
-CALL internal.dbms.cluster.moveToNextDiscoveryVersion();
+CALL dbms.cluster.moveToNextDiscoveryVersion();
 ----
 . Check that transition to `V2_ONLY` was successful:
 +

modules/ROOT/pages/reference/procedures.adoc

@@ -293,6 +293,11 @@ In 4.2, signature changed to `db.listLocks() :: (mode :: STRING, resourceType ::
 | label:yes[]
 | label:new[Introduced in 5.22] label:admin-only[]
 
+| xref:reference/procedures.adoc#procedure_dbms_cluster_movetonextdiscoveryversion[`dbms.cluster.moveToNextDiscoveryVersion()`]
+| label:no[]
+| label:yes[]
+| label:new[Introduced in 5.26] label:admin-only[]
+
 | xref:reference/procedures.adoc#procedure_dbms_cluster_deallocateDatabaseFromServer[`dbms.cluster.deallocateDatabaseFromServer()`]
 | label:no[]
 | label:yes[]
@@ -1913,6 +1918,20 @@ m| dbms.cluster.showParallelDiscoveryState() :: (mode :: STRING, stateComparison
 m|DBMS
 |===
 
+[[procedure_dbms_cluster_movetonextdiscoveryversion]]
+[role=label--enterprise-edition label--new-5.26 label--admin-only ]
+.dbms.cluster.moveToNextDiscoveryVersion()
+[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).
+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
+|===
+
 [[procedure_dbms_cluster_deallocateDatabaseFromServer]]
 [role=label--enterprise-edition label--new-5.23]
 .dbms.cluster.deallocateDatabaseFromServer()