Doc updates

DOC/CLUSTER_MGMT.md

@@ -80,9 +80,9 @@ If a node fails completely and is not coming back, or if you shut down a node be
 You can also make a direct call to the HTTP API to remove a node:
 
 ```
-curl -XDELETE http://localhost:4001/remove -d '{"id": "<node raft ID>"}'
+curl -XDELETE http://host:4001/remove -d '{"id": "<node raft ID>"}'
 ```
-assuming `localhost` is the address of the cluster leader. If you do not do this the leader will continually attempt to communicate with that node. **Note that the cluster must be functional -- there must still be an operational leader -- for this removal to be successful**. If, after a node failure, a given cluster does not have a quorum of nodes still running, you must bring back the failed node. Any attempt to remove it will fail as there will be no Leader to respond to the node-removal request.
+where `host` is any node in the cluster. If you do not remove a failed node the lLader will continually attempt to communicate with that node. **Note that the cluster must be functional -- there must still be an operational Leader -- for this removal to be successful**. If, after a node failure, a given cluster does not have a quorum of nodes still running, you must bring back the failed node. Any attempt to remove it will fail as there will be no Leader to respond to the node-removal request.
 
 If you cannot bring sufficient nodes back online such that the cluster can elect a leader, follow the instructions in the section titled _Dealing with failure_.