diff --git a/docs/src/main/asciidoc/spring-cloud-stream.adoc b/docs/src/main/asciidoc/spring-cloud-stream.adoc
index 79dda2c13..10ea55f92 100644
--- a/docs/src/main/asciidoc/spring-cloud-stream.adoc
+++ b/docs/src/main/asciidoc/spring-cloud-stream.adoc
@@ -256,9 +256,9 @@ public class SampleApplication {
 }
 ----
 The above example looks no different then any vanilla spring-boot application. It defines a single bean of type `Function`
-and that it is. So, how does it became spring-cloud-stream application?
-It becomes spring-cloud-stream application simply based on the presence of spring-cloud-stream and binder dependencies
-and auto-configuration classes on the classpath effectively setting the context for your boot application as spring-cloud-stream application.
+and that is it. So, how does it become a spring-cloud-stream application?
+It becomes a spring-cloud-stream application simply because of the presence of spring-cloud-stream and binder dependencies
+and auto-configuration classes on the classpath, effectively setting the context for your boot application as a spring-cloud-stream application.
 And in this context beans of type `Supplier`, `Function` or `Consumer` are treated as defacto message handlers triggering
 binding of to destinations exposed by the provided binder following certain naming conventions and
 rules to avoid extra configuration.