anchor.diff:  
   ==== Using custom state stores in functional applications
   
  -You can define custom state stores as beans in your application and those will be detected and added to the Streams builder by the binder.
  +You can define custom state stores as beans in your application and those will be detected and added to the Kafka Streams builder by the binder.
   Note that, for regular StreamListener based processors, you still need to use the `KafkaStreamsStateStore` annotation for custom state stores.
  -Here is an example of using custom state stores with functional style.
  +Here is an example of using custom state stores with functional style described in this section.
   
   [source]
   ----
  
positive.code: ----
  
  The input will be received from the input binding defined in the `KafkaStreamsProcessor` interface and the output will be sent to the output binding.
  
  If the processor does not send any data on the outbound, then this becomes a plain Consumer bean as below.
  
  [source]
  ----
  
negative.code:     }
  ----
  
  In the above function bean, there are two inputs and one output.
  The function that returns from the method takes a `KStream` as input, but if you look at the output of this function,, that is another function
  which takes a `KTable` as its input. The output of this second function is a `KStream` which becomes the output of the processor.
  Another way to look at this is like the following:
  
  Function 1: Function<KStream<String, Long> - KStream input; returns the output of "Function 2"
  Function 2: Function<KTable<String, String>, KStream<String, Long>> - KTable input; returns KStream<String, Long> which becomes the output of the processor.
  
  Both inputs are available as references in the method body and the applications can perform various operations on them.
  In this example we use function currying on two partial functions.
  One thing to keep in mind is that the input bindings must follow a natural order of sorting when you have multiple input bindings, otherwise the binder won't know which binding to bind for the various function inputs.
  