Update modules/develop/pages/transactions.adoc

kbatuigas · Feediver1 · web-flow · commit d9d51dddf7b3 · 2025-08-01T12:18:01.000-07:00
Co-authored-by: Joyce Fee &lt;102751339+Feediver1@users.noreply.github.com&gt;
diff --git a/modules/develop/pages/transactions.adoc b/modules/develop/pages/transactions.adoc
@@ -270,7 +270,7 @@ Redpanda’s default configuration supports exactly-once processing. To preserve
 
 To help avoid common pitfalls and optimize performance, consider the following when configuring transactional workloads in Redpanda:
 
-* Ongoing transactions can prevent consumers from advancing. To avoid this, don't set transaction timeout (`transaction.timeout.ms` in Java client) to high values: the higher the timeout, the longer consumers may be blocked. By default, it's about a minute, but it's a client setting that depends on the client.
+* Ongoing transactions can prevent consumers from advancing. To avoid this, don't set transaction timeout (`transaction.timeout.ms` in Java client) to high values: the longer the timeout, the longer consumers may be blocked. By default, it's about a minute, but it's a client setting that depends on the client.
 ifndef::env-cloud[]
 * When running transactional workloads from clients, tune xref:reference:cluster-properties#max_transactions_per_coordinator[`max_transactions_per_coordinator`] to the number of active transactions that you expect your clients to run at any given time (if your client transaction IDs are not reused). 
 +

Original file line number	Diff line number	Diff line change
`@@ -270,7 +270,7 @@ Redpanda’s default configuration supports exactly-once processing. To preserve`
`270`	`270`
`271`	`271`	`To help avoid common pitfalls and optimize performance, consider the following when configuring transactional workloads in Redpanda:`
`272`	`272`
`273`		-* Ongoing transactions can prevent consumers from advancing. To avoid this, don't set transaction timeout (`transaction.timeout.ms` in Java client) to high values: the higher the timeout, the longer consumers may be blocked. By default, it's about a minute, but it's a client setting that depends on the client.
	`273`	+* Ongoing transactions can prevent consumers from advancing. To avoid this, don't set transaction timeout (`transaction.timeout.ms` in Java client) to high values: the longer the timeout, the longer consumers may be blocked. By default, it's about a minute, but it's a client setting that depends on the client.
`274`	`274`	`ifndef::env-cloud[]`
`275`	`275`	* When running transactional workloads from clients, tune xref:reference:cluster-properties#max_transactions_per_coordinator[`max_transactions_per_coordinator`] to the number of active transactions that you expect your clients to run at any given time (if your client transaction IDs are not reused).
`276`	`276`	`+`