Skip to content

Commit 7178dbf

Browse files
authored
Merge pull request #3074 from tautologicc/fix-docs-typo
Fix typos in documentation
2 parents b5b8b30 + fe6a0ab commit 7178dbf

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/modules/ROOT/pages/spring-cloud-stream/bindings.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ public class SampleApplication {
2525
}
2626
}
2727
----
28-
The above example looks no different then any vanilla spring-boot application. It defines a single bean of type `Function`
28+
The above example looks no different than any vanilla spring-boot application. It defines a single bean of type `Function`
2929
and that is it. So, how does it become a spring-cloud-stream application?
3030
It becomes a spring-cloud-stream application simply because of the presence of spring-cloud-stream and binder dependencies
3131
and auto-configuration classes on the classpath, effectively setting the context for your boot application as a spring-cloud-stream application.

docs/modules/ROOT/pages/spring-cloud-stream/producing-and-consuming-messages.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ we recommend using functional implementations.
1313
[[overview]]
1414
=== Overview
1515

16-
Since Spring Cloud Stream v2.1, another alternative for defining _stream handlers_ and _sources_ is to use build-in
16+
Since Spring Cloud Stream v2.1, another alternative for defining _stream handlers_ and _sources_ is to use built-in
1717
support for https://cloud.spring.io/spring-cloud-function/[Spring Cloud Function] where they can be expressed as beans of
1818
type `java.util.function.[Supplier/Function/Consumer]`.
1919

0 commit comments

Comments
 (0)