anchor.diff:  The above describes just a few use cases where you may need to use a single function to accept and/or produce
   multiple _streams_ of data. And that is the type of use cases we are targeting here.
   
  -Also, note a slightly different emphasis on the concept of _sreams_ here. The assumption is that such functions are only valuable
  +Also, note a slightly different emphasis on the concept of _streams_ here. The assumption is that such functions are only valuable
   if they are given access to the actual streams of data (not the individual elements). So for that we are relying on
   abstractions provided by https://projectreactor.io/[Project Reactor] (i.e., `Flux` and `Mono`) which is already available on the
   classpath as part of the dependencies brought in by spring-cloud-functions.
  
positive.code: 
  The Binder SPI consists of a number of interfaces, out-of-the box utility classes, and discovery strategies that provide a pluggable mechanism for connecting to external middleware.
  
  The key point of the SPI is the `Binder` interface, which is a strategy for connecting inputs and outputs to external middleware. The following listing shows the definnition of the `Binder` interface:
  
  [source,java]
  ----
  
negative.code: ----
  
  For cases where you have multiple bindings and/or multiple inputs and outputs, the `send()` and `receive()`
  methods of `InputDestination` and `OutputDestination` are overridden to allow you to provide index of the input and output destination.
  
  Consider the following sample:
  [source,java]
  