done

Author: igormq

spring-kafka-docs/src/main/antora/modules/ROOT/pages/kafka/micrometer.adoc

@@ -123,13 +123,10 @@ When it is `null` (default), the admin will invoke the `describeCluster` admin o
 [[batch-listener-obs]]
 === Batch Listener Observations
 
-When using a batch listener, by default, no observations are created, even if a
-`ObservationRegistry` is present.
-This is because the scope of an observation is tied to the thread, and with a batch
-listener, there is no one-to-one mapping between an observation and a record.
+When using a batch listener, by default, no observations are created, even if a `ObservationRegistry` is present.
+This is because the scope of an observation is tied to the thread, and with a batch listener, there is no one-to-one mapping between an observation and a record.
 
-To enable per-record observations in a batch listener, set the container factory
-property `recordObservationsInBatch` to `true`.
+To enable per-record observations in a batch listener, set the container factory property `recordObservationsInBatch` to `true`.
 
 [source,java]
 ----
@@ -145,7 +142,5 @@ ConcurrentKafkaListenerContainerFactory<?, ?> kafkaListenerContainerFactory(
 }
 ----
 
-When this property is `true`, an observation will be created for each record in the
-batch, but the observation is not propagated to the listener method.
-This allows you to have visibility into the processing of each record, even within a
-batch context.
+When this property is `true`, an observation will be created for each record in the batch, but the observation is not propagated to the listener method.
+This allows you to have visibility into the processing of each record, even within a batch context.