diff --git a/2.1.0.RC1/spring-cloud-stream.xml b/2.1.0.RC1/spring-cloud-stream.xml index c0fcc4830..5105bed30 100644 --- a/2.1.0.RC1/spring-cloud-stream.xml +++ b/2.1.0.RC1/spring-cloud-stream.xml @@ -120,7 +120,7 @@ Preface A Brief History of Spring’s Data Integration Journey -Spring’s journey on Data Integration started with Spring Integration. With its programming model, it provided a consistent developer experience to build applications that can embrace Enterprise Integration Patterns to connect with external systems such as, databases, message brokers, and among others. +Spring’s journey on Data Integration started with Spring Integration. With its programming model, it provided a consistent developer experience to build applications that can embrace Enterprise Integration Patterns to connect with external systems such as, databases, message brokers, and among others. Fast forward to the cloud-era, where microservices have become prominent in the enterprise setting. Spring Boot transformed the way how developers built Applications. With Spring’s programming model and the runtime responsibilities handled by Spring Boot, it became seamless to develop stand-alone, production-grade Spring-based microservices. To extend this to Data Integration workloads, Spring Integration and Spring Boot were put together into a new project. Spring Cloud Stream was born. With Spring Cloud Stream, developers can: @@ -767,7 +767,7 @@ private MessageChannel output; You can write a Spring Cloud Stream application by using either Spring Integration annotations or Spring Cloud Stream native annotation.
Spring Integration Support -Spring Cloud Stream is built on the concepts and patterns defined by Enterprise Integration Patterns and relies +Spring Cloud Stream is built on the concepts and patterns defined by Enterprise Integration Patterns and relies in its internal implementation on an already established and popular implementation of Enterprise Integration Patterns within the Spring portfolio of projects: Spring Integration framework. So its only natural for it to support the foundation, semantics, and configuration options that are already established by Spring Integration @@ -2342,7 +2342,7 @@ The spring.cloud.stream.schema.server.path property can be us The spring.cloud.stream.schema.server.allowSchemaDeletion boolean property enables the deletion of a schema. By default, this is disabled. The schema registry server uses a relational database to store the schemas. By default, it uses an embedded database. -You can customize the schema storage by using the Spring Boot SQL database and JDBC configuration options. +You can customize the schema storage by using the Spring Boot SQL database and JDBC configuration options. The following example shows a Spring Boot application that enables the schema registry: @SpringBootApplication @EnableSchemaRegistryServer @@ -2866,7 +2866,7 @@ a STREAM_CLOUD_STREAM_VERSION header set to 2.x Deploying Stream Applications on CloudFoundry On CloudFoundry, services are usually exposed through a special environment variable called VCAP_SERVICES. -When configuring your binder connections, you can use the values from an environment variable as explained on the dataflow Cloud Foundry Server docs. +When configuring your binder connections, you can use the values from an environment variable as explained on the dataflow Cloud Foundry Server docs.
diff --git a/font-awesome/font/fontawesome-webfont.svg b/font-awesome/font/fontawesome-webfont.svg index 2edb4ec34..8b349d50e 100755 --- a/font-awesome/font/fontawesome-webfont.svg +++ b/font-awesome/font/fontawesome-webfont.svg @@ -1,5 +1,5 @@ - + diff --git a/spring-cloud-stream.xml b/spring-cloud-stream.xml index b3e7c9921..8165add6d 100644 --- a/spring-cloud-stream.xml +++ b/spring-cloud-stream.xml @@ -120,7 +120,7 @@ Preface A Brief History of Spring’s Data Integration Journey -Spring’s journey on Data Integration started with Spring Integration. With its programming model, it provided a consistent developer experience to build applications that can embrace Enterprise Integration Patterns to connect with external systems such as, databases, message brokers, and among others. +Spring’s journey on Data Integration started with Spring Integration. With its programming model, it provided a consistent developer experience to build applications that can embrace Enterprise Integration Patterns to connect with external systems such as, databases, message brokers, and among others. Fast forward to the cloud-era, where microservices have become prominent in the enterprise setting. Spring Boot transformed the way how developers built Applications. With Spring’s programming model and the runtime responsibilities handled by Spring Boot, it became seamless to develop stand-alone, production-grade Spring-based microservices. To extend this to Data Integration workloads, Spring Integration and Spring Boot were put together into a new project. Spring Cloud Stream was born. With Spring Cloud Stream, developers can: @@ -769,7 +769,7 @@ private MessageChannel output; You can write a Spring Cloud Stream application by using either Spring Integration annotations or Spring Cloud Stream native annotation.
Spring Integration Support -Spring Cloud Stream is built on the concepts and patterns defined by Enterprise Integration Patterns and relies +Spring Cloud Stream is built on the concepts and patterns defined by Enterprise Integration Patterns and relies in its internal implementation on an already established and popular implementation of Enterprise Integration Patterns within the Spring portfolio of projects: Spring Integration framework. So its only natural for it to support the foundation, semantics, and configuration options that are already established by Spring Integration @@ -2345,7 +2345,7 @@ The spring.cloud.stream.schema.server.path property can be us The spring.cloud.stream.schema.server.allowSchemaDeletion boolean property enables the deletion of a schema. By default, this is disabled. The schema registry server uses a relational database to store the schemas. By default, it uses an embedded database. -You can customize the schema storage by using the Spring Boot SQL database and JDBC configuration options. +You can customize the schema storage by using the Spring Boot SQL database and JDBC configuration options.
 The following example shows a Spring Boot application that enables the schema registry: @SpringBootApplication @EnableSchemaRegistryServer @@ -2869,7 +2869,7 @@ a STREAM_CLOUD_STREAM_VERSION header set to 2.x Deploying Stream Applications on CloudFoundry On CloudFoundry, services are usually exposed through a special environment variable called VCAP_SERVICES. -When configuring your binder connections, you can use the values from an environment variable as explained on the dataflow Cloud Foundry Server docs. +When configuring your binder connections, you can use the values from an environment variable as explained on the dataflow Cloud Foundry Server docs.