Merge pull request #1155 from VictorPongolino/typo-doc-fix

Doc and Javadoc typos fix

Author: olegz

docs/modules/ROOT/pages/spring-cloud-function/programming-model.adoc

@@ -195,8 +195,9 @@ The `MessageRoutingCallback` is a strategy to assist with determining the name o
 [source, java]
 ----
 public interface MessageRoutingCallback {
-	FunctionRoutingResult routingResult(Message<?> message);
-	. . .
+    default String routingResult(Message<?> message) {
+	    return (String) message.getHeaders().get(FunctionProperties.FUNCTION_DEFINITION);
+    }
 }
 ----
 
@@ -739,4 +740,4 @@ private final static JsonMasker masker = JsonMasker.INSTANCE();
 . . .
 
 logger.info("Received: " + masker.mask(new String(payload, StandardCharsets.UTF_8)));
-----
+----

spring-cloud-function-context/src/main/java/org/springframework/cloud/function/context/MessageRoutingCallback.java

@@ -33,7 +33,7 @@
 public interface MessageRoutingCallback {
 
 	/**
-	 * Computes and returns the instance of {@link FunctionRoutingResult} which encapsulates,
+	 * Computes and returns the instance of {@link String} which encapsulates,
 	 * at the very minimum, function definition.
 	 * <br><br>
 	 * Providing such message is primarily an optimization feature. It could be useful for cases
@@ -42,7 +42,7 @@ public interface MessageRoutingCallback {
 	 * message for downstream use didn't exist, resulting in repeated transformation, type conversion etc.
 	 *
 	 * @param message input message
-	 * @return instance of {@link FunctionRoutingResult} containing the result of the routing computation
+	 * @return instance of {@link String} containing the result of the routing computation
 	 */
 	default String routingResult(Message<?> message) {
 		return (String) message.getHeaders().get(FunctionProperties.FUNCTION_DEFINITION);