anchor.diff:  (_where, `reactor.ipc.netty` is the global package for everything `reactor-netty` related_)
   
   NOTE: Similar to the `local-deployer` and `cloudfoundry-deployer` options as discussed above, there
  -are equivalent settings available for Apache YARN, Apache Mesos and Kubernetes varaints, too. Check out the 
  +are equivalent settings available for Apache YARN, Apache Mesos and Kubernetes variants, too. Check out the
   respective link:https://github.com/spring-cloud?utf8=%E2%9C%93&query=deployer[SPI implementations] to 
   find out more details about the packages to configure for logging.
   
  
positive.code: The streaming applications in Spring Cloud Data Flow are Spring Boot applications and they can be 
  independently setup with logging configurations. 
  
  For instance, if you'd have to troubleshoot the `header` and `payload` specifics that's being passed 
  around between source, processor and sink channels, you'd be deploying the stream with the following
  options.
  
  
  
negative.code: == Logging
  
  Spring Cloud Data Flow is built upon several Spring projects, but ultimately the dataflow-server is a 
  Spring Boot app, so the logging techniques that apply to any link:http://docs.spring.io/spring-boot/docs/current/reference/html/howto-logging.html#howto-logging[Spring Boot]
  application are applicable here as well.
  
  
  While troubleshooting, following are the two primary areas where enabling the DEBUG logs could be 
  