From 3c5113f3dacbe50ff4c3396f35db1f48c3fb6323 Mon Sep 17 00:00:00 2001 From: Nayan Hajratwala Date: Fri, 25 Apr 2025 14:23:33 -0400 Subject: [PATCH] Fix documentation typos Signed-off-by: Nayan Hajratwala Resolves #3110 --- .../ROOT/pages/kafka/kafka-reactive-binder/examples.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/modules/ROOT/pages/kafka/kafka-reactive-binder/examples.adoc b/docs/modules/ROOT/pages/kafka/kafka-reactive-binder/examples.adoc index 50a38d1a0..c952ed12d 100644 --- a/docs/modules/ROOT/pages/kafka/kafka-reactive-binder/examples.adoc +++ b/docs/modules/ROOT/pages/kafka/kafka-reactive-binder/examples.adoc @@ -11,7 +11,7 @@ public Function, Flux> uppercase() { } ---- -You can use the above `upppercase` function with both message channel based Kafka binder (`spring-cloud-stream-binder-kafka`) as well as the reactive Kafka binder (`spring-cloud-stream-binder-kafka-reactive`), the topic of discussion in this section. +You can use the above `uppercase` function with both message channel based Kafka binder (`spring-cloud-stream-binder-kafka`) as well as the reactive Kafka binder (`spring-cloud-stream-binder-kafka-reactive`), the topic of discussion in this section. When using this function with the regular Kafka binder, although you are using reactive types in the application (i.e., in the `uppercase` function), you only get the reactive streams within the execution of your function. Outside the function's execution context, there is no reactive benefits since the underlying binder is not based on the reactive stack. Therefore, although this might look like it is bringing a full end-to-end reactive stack, this application is only partially reactive. @@ -34,7 +34,7 @@ Starting with version 4.0.2, the `KafkaHeaders.ACKNOWLEDGMENT` header contains a [source, java] ---- @Bean -public Consumer> consume() { +public Consumer>> consume() { return msg -> { process(msg.getPayload()); msg.getHeaders().get(KafkaHeaders.ACKNOWLEDGMENT, ReceiverOffset.class).acknowledge();