anchor.diff:  In this application, there is a single input binding that is of type `KStream`.
   The binder creates this binding for the application with a name `process-in-0`, i.e. the name of the function bean name followed by a dash character (`-`) and the literal `in` followed by another dash and then the ordinal position of the parameter.
   You use this binding name to set other properties such as destination.
  -For example, `spring.cloud.stream.bindings.process-in-0.destinaion=my-topic`.
  +For example, `spring.cloud.stream.bindings.process-in-0.destination=my-topic`.
   
   NOTE: If the destination property is not set on the binding, a topic is created with the same name as the binding (if there are sufficient privileges for the application) or that topic is expected to be already available.
   
  
positive.code: Please note that this is a major change on default behavior from previous versions of Kafka Streams binder where the deserialization was done by the framework.
  
  Kafka Streams binder will try to infer matching `Serde` types by looking at the type signature of `java.util.function.Function|Consumer` or `StreamListener`.
  Here is the order that it matches Serdes.
  
  * If the application provides a bean of type `Serde` and if the return type is parameterized with the actual type of the incoming key or value type, then it will use that `Serde` for inbound deserialization.
  For e.g. if you have the following in the application, the binder detects that the incoming value type for the `KStream` matches with a type that is parameterized on a `Serde` bean.
  
negative.code: 
  === Usage
  
  For using the Kafka Streams binder, you just need to add it to your Spring Cloud Stream application, using the following maven coordinates:
  
  [source,xml]
  ----
  