Update docs/txn-advanced-features.md

docs/txn-advanced-features.md

@@ -44,7 +44,7 @@ To enhance the flexibility of Pulsar transactions, they support two distinct iso
 - `READ_UNCOMMITTED`: The consumer can consume all messages, even transactional messages that have been aborted.
 
 For different scenarios, they use different subscriptions and choose different isolation levels. One needs transaction, one does not. In general, multiple subscriptions of the same topic do not all
-require transaction guarantees. Some want low latency without the exact-once semantic guarantee (like Real-Time Monitoring System), and some must require the exactly-once guarantee (like Business Processing System).
+require transaction guarantees. Some want low latency without the exact-once semantic guarantee (like a real-time monitoring system), and some must require the exactly-once guarantee (e.g., business processing systems).
 Users can freely choose different isolation levels according to different scenarios.
 
 Note that this is a subscription dimension configuration, and all consumers under the same subscription need to be configured with the same IsolationLevel.