diff --git a/spring-cloud-function-context/src/main/java/org/springframework/cloud/function/context/config/RoutingFunction.java b/spring-cloud-function-context/src/main/java/org/springframework/cloud/function/context/config/RoutingFunction.java
index dd6b965b3..5e74de8dd 100644
--- a/spring-cloud-function-context/src/main/java/org/springframework/cloud/function/context/config/RoutingFunction.java
+++ b/spring-cloud-function-context/src/main/java/org/springframework/cloud/function/context/config/RoutingFunction.java
@@ -197,7 +197,7 @@ public class RoutingFunction implements Function<Object, Object> {
 		Assert.hasText(functionName, "Failed to resolve function name based on routing expression '" + functionProperties.getRoutingExpression() + "'");
 		FunctionInvocationWrapper function = functionCatalog.lookup(functionName);
 		Assert.notNull(function, "Failed to lookup function to route to based on the expression '"
-				+ functionProperties.getRoutingExpression() + "' whcih resolved to '" + functionName + "' function name.");
+				+ functionProperties.getRoutingExpression() + "' which resolved to '" + functionName + "' function name.");
 		if (logger.isInfoEnabled()) {
 			logger.info("Resolved function from provided [routing-expression]  " + routingExpression);
 		}
diff --git a/spring-cloud-function-rsocket/README.md b/spring-cloud-function-rsocket/README.md
index 5ce6c0c2e..aad21631b 100644
--- a/spring-cloud-function-rsocket/README.md
+++ b/spring-cloud-function-rsocket/README.md
@@ -49,7 +49,7 @@ payload via `data` operation. Then we use one of the `retrieve` operations that
 
 As you can see from the preceding examples, we provide function definition as a value to `route(..)` operator of `RSocketRequester.Builder`.
 However that is not the only way. You can also use standard `spring.cloud.function.definition` property as well as `spring.cloud.function.routing-expression` or property or `MessageRoutingCallback` on the server side of the RSocket interaction (see "Function Routing and Filtering" section of reference manual). 
-This raises a question of _order_ and _priorities_ when it comes to reconsiling a conflict in the event several ways of providing definition are used. So it is a mater of clearly stating the rule whcih is:
+This raises a question of _order_ and _priorities_ when it comes to reconsiling a conflict in the event several ways of providing definition are used. So it is a mater of clearly stating the rule which is:
 
 ***1 - MessageRoutingCallback***
 The `MessageRoutingCallback` takes precedence over all other ways of providing function definition resolution.
@@ -96,4 +96,4 @@ So you can see `--spring.cloud.function.definition=reverse>localhost:" + portA +
 
 ### Samples
 
-You can also look at one of the [RSocket samples](https://github.com/spring-cloud/spring-cloud-function/tree/master/spring-cloud-function-samples/function-sample-cloudevent-rsocket) that is also introduces you to Cloud Events 
\ No newline at end of file
+You can also look at one of the [RSocket samples](https://github.com/spring-cloud/spring-cloud-function/tree/master/spring-cloud-function-samples/function-sample-cloudevent-rsocket) that is also introduces you to Cloud Events