Apply suggestions from code review

Co-authored-by: Reneta Popova <[email protected]>

Author: yirensum

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

@@ -304,13 +304,14 @@ The discovery addresses should include addresses of the new members, and the pre
 +
 As an example, for those using the list resolver, the settings for the new servers should include:
 +
-```
+[source, parameters]
+----
 dbms.cluster.discovery.resolver_type=LIST
 dbms.cluster.discovery.version=V1_OVER_V2
 
 dbms.cluster.discovery.endpoints=server01.example.com:5000,server02.example.com:5000,server03.example.com:5000,server04.example.com:5000,server05.example.com:5000,server06.example.com:5000
 dbms.cluster.discovery.v2.endpoints=server01.example.com:6000,server02.example.com:6000,server03.example.com:6000,server04.example.com:6000,server05.example.com:6000,server06.example.com:6000
-```
+----
 +
 . Using `bolt://`, connect to the system database of servers 4, 5, 6, and run the following procedure.
 This can be done using via `./cypher-shell -a bolt://localhost:7685 -d system` for example.
@@ -343,13 +344,14 @@ The discovery addresses in the settings should include addresses of the new memb
 +
 As an example, for those using the list resolver, the settings for the new servers should include:
 +
-```
+[source, parameters]
+----
 dbms.cluster.discovery.resolver_type=LIST
 dbms.cluster.discovery.version=V2_OVER_V1
 
 dbms.cluster.discovery.endpoints=server04.example.com:5000,server05.example.com:5000,server06.example.com:5000,server07.example.com:5000,server08.example.com:5000,server09.example.com:5000
 dbms.cluster.discovery.v2.endpoints=server04.example.com:6000,server05.example.com:6000,server06.example.com:6000,server07.example.com:6000,server08.example.com:6000,server09.example.com:6000
-```
+----
 +
 . Using `bolt://`, connect to the system database of servers 7, 8, 9 and run the following procedure:
 +
@@ -358,7 +360,7 @@ dbms.cluster.discovery.v2.endpoints=server04.example.com:6000,server05.example.c
 CALL dbms.cluster.showParallelDiscoveryState();
 ----
 +
-The output should display `Matching` in the `stateComparison`.
+The output should display `Matching` in the `stateComparison` column.
 If they are not, wait and try again till matching.
 +
 .Expected result
@@ -382,12 +384,13 @@ Note that only the v2 settings are required.
 +
 As an example, for those using the list resolver, the settings for the new servers should include:
 +
-```
+[source, parameters]
+----
 dbms.cluster.discovery.resolver_type=LIST
 dbms.cluster.discovery.version=V2_ONLY
 
 dbms.cluster.discovery.v2.endpoints=server07.example.com:6000,server08.example.com:6000,server09.example.com:6000,server10.example.com:6000,server11.example.com:6000,server12.example.com:6000
-```
+----
 +
 . Deallocate, drop, and shut down servers 7, 8, 9.
 +
@@ -408,7 +411,6 @@ CALL dbms.cluster.showParallelDiscoveryState();
 +-------------------------------------------------------------+
 ----
 [[discovery-v1-to-v2-procedures]]
-
 === Using procedures
 
 // 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.
@@ -420,14 +422,15 @@ CALL dbms.cluster.showParallelDiscoveryState();
 +
 As an example, for those using the list resolver, the settings for all the servers should include:
 +
-```
+[source, parameters]
+----
 dbms.cluster.discovery.resolver_type=LIST
 
 dbms.cluster.discovery.endpoints=server01.example.com:5000,server02.example.com:5000,server03.example.com:5000
 dbms.cluster.discovery.v2.endpoints=server01.example.com:6000,server02.example.com:6000,server03.example.com:6000
-```
+----
 +
-. In Cypher Shell, connect to the system database of server01 using `bolt://`.
+. In Cypher Shell, connect to the `system` database of server01 using `bolt://`.
 It is important to connect via `bolt://` because otherwise the procedure might be routed and executed not on the intended server.
 +
 [source, shell, role=nocopy noplay]
@@ -491,7 +494,7 @@ This is no reason for worry.
 
 . Check the state on all servers again.
 It should show that the states are `Matching`.
-Both serverCounts should be 3.
+Both `serverCounts` should be 3.
 +
 .Expected result
 [queryresult]