Change the titles of the sections

Author: akarasavov

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

@@ -224,7 +224,7 @@ It is important that both `dbms.kubernetes.service_port_name` and `dbms.kubernet
 For more information, see <<clustering-discovery-k8s>>.
 
 [[discovery-v1-to-v2-semi-automated-procedure]]
-=== Moving an entire cluster with a procedure
+=== Procedure for moving an entire cluster
 
 The first way to migrate from discovery service v1 to v2 is to use a semi-automated procedure, which simplifies the migration process.
 It automates the approach described in the xref:clustering/setup/discovery.adoc#discovery-v1-to-v2-procedures[next section].
@@ -354,7 +354,7 @@ are set as required, so that the servers start with v2 running on the next resta
 ====
 
 [[discovery-v1-to-v2-procedures]]
-=== Running a procedure on each server
+=== Per server procedure
 
 // By using just procedures, the nice thing is that during the user's normal version upgrade, they can also add the new settings required for v2 discovery service.
 // Then, when they are ready to migrate to v2, they can use the procedures and then finally, set the version to 'V2' in the neo4j.conf at the very end - which can just sit there till the next restart