update README for transacted consumers

solace-spring-cloud-starters/solace-spring-cloud-stream-starter/README.adoc

@@ -872,8 +872,15 @@ Consumer<Message<List<Payload>>> input() {
 <1> A batch of messages is really just a single Spring `Message` whose payload is a list of individual message payloads.
 <2> The `solace_scst_batchedHeaders` message header contains the consolidated list of message headers for each of the individual messages in the batch.
 
-IMPORTANT: Message batches are non-transacted. A batch that this binder creates is fundamentally a collection of individual messages and must not be treated as a single consistent unit.
+.Transacted Batch Consumers
+[TIP]
+====
+By default, message batches are non-transacted (i.e. `transacted` is set to `false`). When in this mode, a batch that this binder creates is fundamentally a collection of individual messages and must not be treated as a single consistent unit.
+
+When `transacted` is set to `true`, a local transaction is used to process the batched message. The batch of messages is then automatically committed (or is rolled back on errors) when the message handler returns.
+====
 
+.Resolving Batch Message Conversion Issues
 [TIP]
 ====
 If the Spring Cloud Stream framework fails to convert the batch message, consider setting one of the following consumer config options: