anchor.diff:  
   ==== Binding and Binding names
   
  -Binding is an abstraction that represents a bridge between remote destinations exposed by the binder and user code,
  +Binding is an abstraction that represents a bridge between sources and targets exposed by the binder and user code,
   This abstraction has a name and while we try to do our best to limit configuration required to run spring-cloud-stream applications,
  -being aware of such name(s) is necessary for most cases, since binding names are part of the configuration property name for a specific binding.
  +being aware of such name(s) is necessary for cases where additional per-binding configuration is required.
   
   Throughout this manual you will see examples of configuration properties such as `spring.cloud.stream.bindings.input.destination=myQueue`.
  -The `input` segment in this property name example is what we refer to as _binding name_ and it could derive via several mechanisms.
  +The `input` segment in this property name is what we refer to as _binding name_ and it could derive via several mechanisms.
   The following sub-sections will describe the naming conventions and configuration elements used by spring-cloud-stream to control binding names.
   
   ===== Functional binding names
   
  -Unlike the explicit annotation-based support (legacy) used in the previous versions of spring-cloud-stream, the functional
  +Unlike the explicit annotation-based support (legacy) used in the previous versions of spring-cloud-stream via annotations, the functional
   programming model follows a simple convention when it comes to binding names thus greatly simplifying application configuration.
   Let's look at the first example:
   
  
positive.code: }
  ----
  
  In the above example we have an application with a single function which acts as message listener. As a `Function` it has an
  input and output which happened to also be the default names used for binding names - `input` and `output`. So if for example you would want to map
  the input of this function to a remote destination (e.g., topic, queue etc) called "my-topic" you would do so with the following property:
  ----
  spring.cloud.stream.bindings.input.destination=my-topic
  ----
  Note how `input` is used as a segment in property name. The same goes for `output`.
  
  But what if you have multiple functions as in <<Multiple functions in a single application>> section?
  
  [source, java]
  ----
  @SpringBootApplication
  public class SampleApplication {
  
  	@Bean
  	public Function<String, String> uppercase() {
  	    return value -> value.toUpperCase();
  	}
  
  	@Bean
  	public Function<String, String> lowercase() {
  	    return value -> value.toLowerCase();
  	}
  }
  ----
  
  We certainly can't use `input` and `output` as names given that we actually have multiple inputs and outputs.
  For those cases the following naming convention applies:
  
  * input - `<functionName> + -in- + <index>`
  * output - `<functionName> + -out- + <index>`
  
  So if for example you would want to map the input of 'uppercase()' function to a remote destination (e.g., topic, queue etc) called "my-topic"
  you would do so with the following property:
  ----
  spring.cloud.stream.bindings.uppercase-in-0.destination=my-topic
  ----
  
  And if you want to change the content-type of the output of the 'lowercase()' function you would do so with the following property.
  ----
  spring.cloud.stream.bindings.lowercase-out-0.content-type=text/plain
  ----
  
  For more on properties and other configuration options please see <<Configuration Options>> section.
  
  
negative.code: @SpringBootApplication
  public static class SupplierConfiguration {
  
  	@PollableBean
  	public Supplier<Flux<String>> stringSupplier() {
  		return () -> Flux.just("hello", "bye");
  	}
  }
  ----
  
  The bean itself is annotated with `PollableBean` annotation (sub-set of `@Bean`), thus signaling to the framework that although the implementation
  of such a supplier is reactive, it still needs to be polled.
  
  ====== Polling Configuration Properties
  