anchor.diff:          For any component based system one problem that can quickly occur is dependency nightmares.  NiFi addresses this by providing a custom class loader model
           ensuring that each extension bundle is exposed to a very limited set of dependencies.  As a result extensions can be built with little concern for whether 
           they might conflict with another extension.  The concept of these extension bundles is called 'NiFi Archives' and will be discussed in greater detail 
  -        in the developers guide.
  +        in the developer's guide.
   Clustering (scale-out)::
       NiFi is designed to scale-out through the use of clustering many nodes together as described above.  If a single node is provisioned and configured
       to handle hundreds of MB/s then a modest cluster could be configured to handle GB/s.  This then brings about interesting challenges of load balancing
  -    and fail-over between NiFi and the systems from which it gets data.  Use of asynchronous queuing based protocols like messaging services, Kafka, etc.. can
  -    help.  Use of NiFi's 'site-to-site' feature is also very effective as it is a protocol that allows NiFi and a client (could be another NiFi cluster) to talk to eachother, share information
  +    and fail-over between NiFi and the systems from which it gets data.  Use of asynchronous queuing based protocols like messaging services, Kafka, etc., can
  +    help.  Use of NiFi's 'site-to-site' feature is also very effective as it is a protocol that allows NiFi and a client (could be another NiFi cluster) to talk to each other, share information
       about loading, and to exchange data on specific authorized ports.
   
   # References
  
positive.code:         either side of the sender/recipient equation.
      User to system;;
          NiFi enables 2-Way SSL authentication and provides pluggable authorization so that it can properly control
          a users access and at particular levels (read-only, dataflow manager, admin).  If a user enters a 
          sensitive property like a password into the flow it is immediately encrypted server side and never again exposed
          on the client side even in its encrypted form.
  
  Designed for Extension::
  
negative.code: Architecture <<soa>>, the rise of the API <<api>><<api2>>, Internet of Things <<iot>>,
  and Big Data <<bigdata>>.  In addition, the level of rigor necessary for 
  compliance, privacy, and security is constantly on the rise.  Even still with 
  all of these new concepts coming about, the patterns and needs of dataflow are 
  still largely the same.  The primary differences then are the scope of
  complexity, the rate of change necessary to adapt, and that at scale  
  the edge case becomes common occurrence.  NiFi is built to help tackle these 
  