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: Spring Cloud Data Flow builds upon link:https://github.com/spring-cloud/spring-cloud-deployer[Spring Cloud Deployer] SPI 
  and the platform specific dataflow-server uses the respective link:https://github.com/spring-cloud?utf8=%E2%9C%93&query=deployer[SPI implementations]. 
  Specifically, if we were to troubleshoot deployment specific issues; such as the network errors, it'd 
  be useful to enable the DEBUG logs at the deployers and the libraries used by it. 
  
  . For instance, if you'd like to enable DEBUG logs for the link:https://github.com/spring-cloud/spring-cloud-deployer/tree/master/spring-cloud-deployer-local[local-deployer], 
  you'd be starting the server with following.
  
negative.code: ----
  
  (_where, `org.springframework.integration` is the global package for everything Spring Integration related, 
  which is responsible for messaging channels_)
  
  These properties can also be specified via `deployment` properties when deploying the stream.
  
  [source,bash]
  ----
  dataflow:>stream deploy foo --properties "app.*.logging.level.org.springframework.integration=DEBUG"
  ----