SpringCloud/spring-cloud-stream
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typos in documentation

Browse Source 
Signed-off-by: F. Emerson <t@utologi.cc>
This commit is contained in:
F. Emerson
2025-01-30 17:38:35 -03:00
parent b5b8b3089d
commit fe6a0ab8b7
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -25,7 +25,7 @@ public class SampleApplication {
}
}
----
The above example looks no different then any vanilla spring-boot application. It defines a single bean of type `Function`
The above example looks no different than any vanilla spring-boot application. It defines a single bean of type `Function`
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.

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

@@ -13,7 +13,7 @@ we recommend using functional implementations.
[[overview]]
=== Overview
Since Spring Cloud Stream v2.1, another alternative for defining _stream handlers_ and _sources_ is to use build-in
Since Spring Cloud Stream v2.1, another alternative for defining _stream handlers_ and _sources_ is to use built-in
support for https://cloud.spring.io/spring-cloud-function/[Spring Cloud Function] where they can be expressed as beans of
type `java.util.function.[Supplier/Function/Consumer]`.