diff --git a/go-manual/modules/ROOT/pages/query-simple.adoc b/go-manual/modules/ROOT/pages/query-simple.adoc index cee99153..7e901015 100644 --- a/go-manual/modules/ROOT/pages/query-simple.adoc +++ b/go-manual/modules/ROOT/pages/query-simple.adoc @@ -221,7 +221,7 @@ neo4j.ExecuteQuery(ctx, driver, [NOTE] ==== -Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* The difference between the two modes is that _read_ transactions will be routed to any node of a cluster, whereas _write_ ones will be directed to the leader. +Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* The difference between the two modes is that _read_ transactions will be routed to any node of a cluster, whereas _write_ ones are directed to primaries. In other words, there is no guarantee that a write query submitted in read mode will be rejected. ==== diff --git a/go-manual/modules/ROOT/pages/transactions.adoc b/go-manual/modules/ROOT/pages/transactions.adoc index 490c70c2..53108529 100644 --- a/go-manual/modules/ROOT/pages/transactions.adoc +++ b/go-manual/modules/ROOT/pages/transactions.adoc @@ -486,7 +486,7 @@ session := driver.NewSession(ctx, neo4j.SessionConfig{ // .Routing ≠ Access control [NOTE] ==== -Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* The difference between the two modes is that _read_ transactions will be routed to any node of a cluster, whereas _write_ ones will be directed to the leader. +Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* The difference between the two modes is that _read_ transactions will be routed to any node of a cluster, whereas _write_ ones are directed to primaries. In other words, there is no guarantee that a write query submitted in read mode will be rejected. Similar remarks hold for the `.ExecuteRead()` and `.ExecuteWrite()` methods. diff --git a/java-manual/modules/ROOT/pages/query-simple.adoc b/java-manual/modules/ROOT/pages/query-simple.adoc index 013396a9..ae6db218 100644 --- a/java-manual/modules/ROOT/pages/query-simple.adoc +++ b/java-manual/modules/ROOT/pages/query-simple.adoc @@ -228,7 +228,7 @@ var result = driver.executableQuery("MATCH (p:Person) RETURN p.name") [NOTE] ==== -Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* The difference between the two modes is that _read_ transactions will be routed to any node of a cluster, whereas _write_ ones will be directed to the leader. +Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* The difference between the two modes is that _read_ transactions will be routed to any node of a cluster, whereas _write_ ones are directed to primaries. In other words, there is no guarantee that a write query submitted in read mode will be rejected. ==== diff --git a/java-manual/modules/ROOT/pages/transactions.adoc b/java-manual/modules/ROOT/pages/transactions.adoc index 2320a3a9..3ffdf785 100644 --- a/java-manual/modules/ROOT/pages/transactions.adoc +++ b/java-manual/modules/ROOT/pages/transactions.adoc @@ -439,7 +439,7 @@ var session = driver.session(SessionConfig.builder() [NOTE] ==== Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* -The difference between the two modes is that _read_ transactions are routed to any node of a cluster, whereas _write_ ones are directed to the leader. +The difference between the two modes is that _read_ transactions are routed to any node of a cluster, whereas _write_ ones are directed to primaries. In other words, there is no guarantee that a write query submitted in read mode will be rejected. Similar remarks hold for the `.executeRead()` and `.executeWrite()` methods. diff --git a/javascript-manual/modules/ROOT/pages/query-simple.adoc b/javascript-manual/modules/ROOT/pages/query-simple.adoc index ee14d8df..7c276c22 100644 --- a/javascript-manual/modules/ROOT/pages/query-simple.adoc +++ b/javascript-manual/modules/ROOT/pages/query-simple.adoc @@ -204,7 +204,7 @@ await driver.executeQuery( [NOTE] ==== -Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* The difference between the two modes is that _read_ transactions will be routed to any node of a cluster, whereas _write_ ones will be directed to the leader. +Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* The difference between the two modes is that _read_ transactions will be routed to any node of a cluster, whereas _write_ ones are directed to primaries. In other words, there is no guarantee that a write query submitted in read mode will be rejected. ==== diff --git a/javascript-manual/modules/ROOT/pages/transactions.adoc b/javascript-manual/modules/ROOT/pages/transactions.adoc index c6e4fde3..be1b2453 100644 --- a/javascript-manual/modules/ROOT/pages/transactions.adoc +++ b/javascript-manual/modules/ROOT/pages/transactions.adoc @@ -322,7 +322,7 @@ const session = driver.session({ [NOTE] ==== Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* -The difference between the two modes is that _read_ transactions are routed to any node of a cluster, whereas _write_ ones are directed to the leader. +The difference between the two modes is that _read_ transactions are routed to any node of a cluster, whereas _write_ ones are directed to primaries. In other words, there is no guarantee that a write query submitted in read mode will be rejected. Similar remarks hold for the `.executeRead()` and `.executeWrite()` methods. diff --git a/python-manual/modules/ROOT/pages/query-simple.adoc b/python-manual/modules/ROOT/pages/query-simple.adoc index fb421c3a..740bd7a2 100644 --- a/python-manual/modules/ROOT/pages/query-simple.adoc +++ b/python-manual/modules/ROOT/pages/query-simple.adoc @@ -210,7 +210,7 @@ driver.execute_query( [NOTE] ==== -Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* The difference between the two modes is that _read_ transactions will be routed to any node of a cluster, whereas _write_ ones will be directed to the leader. +Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* The difference between the two modes is that _read_ transactions will be routed to any node of a cluster, whereas _write_ ones are directed to primaries. In other words, there is no guarantee that a write query submitted in read mode will be rejected. ==== diff --git a/python-manual/modules/ROOT/pages/transactions.adoc b/python-manual/modules/ROOT/pages/transactions.adoc index 6f237f76..361cd87e 100644 --- a/python-manual/modules/ROOT/pages/transactions.adoc +++ b/python-manual/modules/ROOT/pages/transactions.adoc @@ -402,7 +402,7 @@ with driver.session( [NOTE] ==== Although executing a _write_ query in read mode likely results in a runtime error, *you should not rely on this for access control.* -The difference between the two modes is that _read_ transactions are routed to any node of a cluster, whereas _write_ ones are directed to the leader. +The difference between the two modes is that _read_ transactions are routed to any node of a cluster, whereas _write_ ones are directed to primaries. In other words, there is no guarantee that a write query submitted in read mode will be rejected. Similar remarks hold for the `.executeRead()` and `.executeWrite()` methods.