minor fix

EnterpriseDB · Jun 25, 2024 · 0828001 · 0828001
1 parent 6761b7a
commit 0828001
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/...biganimal/release/getting_started/creating_a_cluster/creating_a_dha_cluster.mdx b/...biganimal/release/getting_started/creating_a_cluster/creating_a_dha_cluster.mdx
@@ -178,7 +178,7 @@ The following options aren't available when creating your cluster:
 
    !!! Important 
 
-       When configuring a read-only connection string with your application, read-only workloads are routed to shadow nodes (non-write leaders). The connection is read-only because it accepts read-only queries through the shadow nodes. However, commands that run on read-only connections aren't filtered by BigAnimal, so shadow nodes can still perfom write operations to the contents of database tables. We recommend that you use a Postgres role with minimal read-only privileges for your application or pass `default_transaction_read_only=on` in the connection string. This way, you can avoid write operations on shadow nodes that could cause conflicts between the write leader and the shadow nodes. 
+       Once you have configured a read-only connection string with your application, read-only workloads are routed to shadow nodes (non-write leaders). The connection is read-only because it accepts read-only queries through the shadow nodes. However, commands that run on read-only connections aren't filtered by BigAnimal, so shadow nodes can still perfom write operations to the contents of database tables. We recommend that you use a Postgres role with minimal read-only privileges for your application or pass `default_transaction_read_only=on` in the connection string. This way, you can avoid write operations on shadow nodes that could cause conflicts between the write leader and the shadow nodes. 
        See [PGD Proxy read-only routing rules](/pgd/latest/routing/readonly/) for more information.
 
    !!! Note

diff --git a/...iganimal/release/overview/02_high_availability/distributed_highavailability.mdx b/...iganimal/release/overview/02_high_availability/distributed_highavailability.mdx
@@ -67,7 +67,7 @@ Since the infrastructure of a Distributed High Availability cluster is almost en
 
 !!! Important 
 
-    When configuring a read-only connection string with your application, read-only workloads are routed to shadow nodes (non-write leaders). The connection is read-only because it accepts read-only queries through the shadow nodes. However, commands that run on read-only connections aren't filtered by BigAnimal, so shadow nodes can still perfom write operations to the contents of database tables. We recommend that you use a Postgres role with minimal read-only privileges for your application or pass `default_transaction_read_only=on` in the connection string. This way, you can avoid write operations on shadow nodes that could cause conflicts between the write leader and the shadow nodes. 
+    Once you have configured a read-only connection string with your application, read-only workloads are routed to shadow nodes (non-write leaders). The connection is read-only because it accepts read-only queries through the shadow nodes. However, commands that run on read-only connections aren't filtered by BigAnimal, so shadow nodes can still perfom write operations to the contents of database tables. We recommend that you use a Postgres role with minimal read-only privileges for your application or pass `default_transaction_read_only=on` in the connection string. This way, you can avoid write operations on shadow nodes that could cause conflicts between the write leader and the shadow nodes. 
 
 ## For more information