diff --git a/modules/ROOT/pages/clustering/setup/single-to-cluster.adoc b/modules/ROOT/pages/clustering/setup/single-to-cluster.adoc
index bc689715a..de3dabef9 100644
--- a/modules/ROOT/pages/clustering/setup/single-to-cluster.adoc
+++ b/modules/ROOT/pages/clustering/setup/single-to-cluster.adoc
@@ -95,10 +95,12 @@ Once all servers are enabled, you can scale up user databases using xref:cluster
 ======
 
 In this example, a standalone server named `server01` is running and two additional servers, `server02` and `server03`, are to be added to form a cluster.
-The two additional servers are configured according to xref:clustering/setup/deploy.adoc#cluster-example-configure-a-three-primary-cluster[Configure a cluster with three servers] and are _not_ running.
+The two additional servers are configured according to xref:clustering/setup/deploy.adoc#cluster-example-configure-a-three-primary-cluster[Configure a cluster with three servers].
+These two new servers should _not_ be started up yet.
 Neo4j Enterprise Edition is installed on all three servers.
 
-Start by stopping the standalone server and once it is stopped, edit the xref:configuration/file-locations.adoc[_neo4j.conf_] file to include the discovery endpoints of itself and the servers that will form the cluster.
+Start by stopping the standalone server.
+Once it is stopped, edit the xref:configuration/file-locations.adoc[_neo4j.conf_] file to include the discovery endpoints of itself and the servers that will form the cluster.
 
 ._neo4j.conf_ on server01.example.com:
 [source, properties]