anchor.diff:  
   [source, java]
   ----
  -@EnableBinding(value={Orders.class, Payment.class}
  +@EnableBinding(value = { Orders.class, Payment.class })
   ----
   
   In Spring Cloud Stream, the bindable `MessageChannel` components are the Spring Messaging `MessageChannel` (for outbound) and its extension, `SubscribableChannel`,
  
positive.code: NOTE: If `group` is not specified anonymous group is used (something like `input.anonymous.2K37rb06Q6m2r51-SPIDDQ`), which is not suitable for error
  handling scenarious, since you don't know what it's going to be until the destination is created.
  
  Also, in the event you are binidng to the existing destination such as:
  
  [source,text]
  ----
  
negative.code: See "`<<spring-cloud-stream-overview-instance-index-instance-count>>`" for more information.
  +
  Default: `-1`.
  useNativeDecoding::
  When set to `true`, the inbound message is deserialized directly by the client library, which must be configured correspondingly (for example, setting an appropriate Kafka producer value deserializer).
  When this configuration is being used, the inbound message unmarshalling is not based on the `contentType` of the binding.
  When native decoding is used, it is the responsibility of the producer to use an appropriate encoder (for example, the Kafka producer value serializer) to serialize the outbound message.
  Also, when native encoding and decoding is used, the `headerMode=embeddedHeaders` property is ignored and headers are not embedded in the message.
  See the producer property `useNativeEncoding`.
  +
  Default: `false`.
  
  
  ==== Producer Properties
  
  