anchor.diff:  |`nifi.security.keystoreType` | The type of Keystore. Must be either `PKCS12` or `JKS`.
   |`nifi.security.keystorePasswd` | The password for the Keystore.
   |`nifi.security.keyPasswd` | The password for the certificate in the Keystore. If not set, the value of `nifi.security.keystorePasswd` will be used.
  -|`nifi.security.truststore` | Filename of the Truststore that will be used to authorize those connecting to NiFi. If not set, all who 
  +|`nifi.security.truststore` | Filename of the Truststore that will be used to authorize those connecting to NiFi. If not set, all who
                               attempt to connect will be provided access as the 'Anonymous' user.
   |`nifi.security.truststoreType` | The type of the Truststore. Must be either `PKCS12` or `JKS`.
   |`nifi.security.truststorePasswd` | The password for the Truststore.
   |`nifi.security.needClientAuth` | Specifies whether or not connecting clients must authenticate themselves. Specifically this property is used
                                   by the NiFi cluster protocol. If the Truststore properties are not set, this must be `false`. Otherwise, a value
  -                                of `true` indicates that nodes in the cluster will be authenticated and must have certificates that are trusted 
  +                                of `true` indicates that nodes in the cluster will be authenticated and must have certificates that are trusted
                                   by the Truststores.
  -|`nifi.security.anonymous.authorities` | Specifies the roles that should be granted to users that connect over HTTPS anonymously. All users can make 
  +|`nifi.security.anonymous.authorities` | Specifies the roles that should be granted to users that connect over HTTPS anonymously. All users can make
                                   use of anonymous access, however if they have been granted a particular level of access by an administrator
  -                                it will take precedence if they access NiFi using a client certificate or once they have logged in. 
  +                                it will take precedence if they access NiFi using a client certificate or once they have logged in.
   |==================================================================================================================================================
   
   Once the above properties have been configured, we can enable the User Interface to be accessed over HTTPS instead of HTTP. This is accomplished
  
positive.code: ----
  
  Increase the number of TCP socket ports available::
  This is particularly important if your flow will be setting up and tearing 
  down a large number of sockets in small period of time.
  ----
  sudo sysctl -w net.ipv4.ip_local_port_range="10000 65000"
  ----
  
  Set how long sockets stay in a TIMED_WAIT state when closed::
  You don't want your sockets to sit and linger too long given that you want to be 
  able to quickly setup and teardown new sockets.  It is a good idea to read more about
  it but to adjust do something like
  ----
  
negative.code: *Dealing with Disconnected Nodes* +
  
  A DFM may manually disconnect a node from the cluster. But if a node becomes disconnected for any other reason (such as due to lack of heartbeat), the NCM will show a bulletin on the User Interface, and the DFM will not be able to make any changes to the dataflow until the issue of the disconnected node is resolved. The DFM or the Administrator will need to troubleshoot the issue with the node and resolve it before any new changes may be made to the dataflow. However, it is worth noting that just because a node is disconnected does not mean that it is not working; it just means that the NCM cannot communicate with the node.
  
  
  *Basic Cluster Setup* +
  
  This section describes the setup for a simple two-node, non-secure, unicast cluster comprised of three instances of NiFi:
  
  * The NCM
  * Node 1
  