Fix documentation typos

Signed-off-by: Nayan Hajratwala <[email protected]>

Resolves #3110

Author: nhajratw

docs/modules/ROOT/pages/kafka/kafka-reactive-binder/examples.adoc

@@ -11,7 +11,7 @@ public Function<Flux<String>, Flux<String>> 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<Flux<Message<String>> consume() {
+public Consumer<Flux<Message<String>>> consume() {
     return msg -> {
         process(msg.getPayload());
         msg.getHeaders().get(KafkaHeaders.ACKNOWLEDGMENT, ReceiverOffset.class).acknowledge();