Apply suggestions from automated review

Author: kbatuigas

modules/develop/pages/transactions.adoc

@@ -264,7 +264,7 @@ Redpanda’s default configuration supports exactly-once processing. To preserve
 
 * `enable_idempotence = true`
 * `enable_transactions = true`
-* `transaction_coordinator_delete_retention_ms >= transactional_id_expiration_ms`
+* `transaction_coordinator_delete_retention_ms` is not lower than `transactional_id_expiration_ms`
 
 == Best practices
 
@@ -279,7 +279,7 @@ The total number of transactions in the cluster at any one time is `max_transact
 Be aware that if you keep the default as 50 and your clients create a new ID for every transaction, the total continues to accumulate, which bloats memory.
 * Transactional metadata is stored in the internal topic `kafka_internal/tx`. Over time, this topic can consume disk space. You can manage its disk usage by tuning the `transaction_coordinator_delete_retention_ms` and `transactional_id_expiration_ms` cluster properties.
 +
-See also: xref:manage:cluster-maintenance/disk-utilization.adoc#manage_transaction_coordinator_disk_usage[Manage Disk Space]
+See also: xref:manage:cluster-maintenance/disk-utilization.adoc#manage-transaction-coordinator-disk-usage[Manage Disk Space]
 * When upgrading a self-managed deployment, make sure to use maintenance mode with a glossterm:rolling upgrade[].
 endif::[]
 

modules/manage/pages/cluster-maintenance/disk-utilization.adoc

@@ -165,7 +165,7 @@ Redpanda supports group offset deletion with the Kafka OffsetDelete API through
 
 == Manage transaction coordinator disk usage
 
-Redpanda uses the internal topic `kafka_internal/tx` to store transaction metadata for exactly-once and transactional producers. Over time, this topic can consume an excessive disk space in niche use cases that generate a large number of transactional sessions.
+Redpanda uses the internal topic `kafka_internal/tx` to store transaction metadata for exactly-once and transactional producers. Over time, this topic can consume excessive disk space in niche use cases that generate a large number of transactional sessions.
 
 You can manage the disk usage of `kafka_internal/tx` by tuning the following cluster properties: