removed section on connecting to a rr (neo4j#774)

Author: AlexicaWright

modules/ROOT/pages/clustering/deploy.adoc

@@ -1,7 +1,7 @@
 [role=enterprise-edition]
 [[causal-clustering-deploy]]
 = Deploy a cluster
-:description: How to deploy a new Neo4j Causal Cluster. 
+:description: How to deploy a new Neo4j Causal Cluster.
 
 
 [[causal-clustering-new-cluster-introduction]]
@@ -204,31 +204,31 @@ A way to ensure that a Read Replica contains a snapshot of a database in the clu
 See xref:reference/procedures.adoc#procedure_dbms_cluster_readreplicatoggle[`dbms.cluster.readReplicaToggle()`] for more information.
 ====
 
-[[causal-clustering-connect-to-a-read-replica]]
-== Connect to a Read Replica
-
-It is important to use the correct URI scheme when connecting to a Read Replica since it only allows read sessions/transactions.
-The following table illustrates the supported URI schemes (the `+s` indicates that TLS has been configured for the cluster):
-
-[cols="4", options="header"]
-|===
-|
-| `bolt+s://`
-| `neo4j+s://` read session/tx
-| `neo4j+s://` write session/tx
-
-| Cypher Shell
-| {check-mark}
-| {cross-mark}
-| {cross-mark}
-
-| Browser
-| {check-mark}
-| {cross-mark}
-| {cross-mark}
-
-| Neo4j Driver
-| {check-mark}
-| {check-mark}
-| {cross-mark}
-|===
+// [[causal-clustering-connect-to-a-read-replica]]
+// == Connect to a Read Replica
+
+// It is important to use the correct URI scheme when connecting to a Read Replica since it only allows read sessions/transactions.
+// The following table illustrates the supported URI schemes (the `+s` indicates that TLS has been configured for the cluster):
+
+// [cols="4", options="header"]
+// |===
+// |
+// | `bolt+s://`
+// | `neo4j+s://` read session/tx
+// | `neo4j+s://` write session/tx
+
+// | Cypher Shell
+// | {check-mark}
+// | {cross-mark}
+// | {cross-mark}
+
+// | Browser
+// | {check-mark}
+// | {cross-mark}
+// | {cross-mark}
+
+// | Neo4j Driver
+// | {check-mark}
+// | {check-mark}
+// | {cross-mark}
+// |===