anchor.diff:  [NOTE]
   ====
   The `HQuorumPeer` process is a ZooKeeper instance which is controlled and started by HBase.
  -If you use ZooKeeper this way, it is limited to one instance per cluster node, , and is appropriate for testing only.
  +If you use ZooKeeper this way, it is limited to one instance per cluster node and is appropriate for testing only.
   If ZooKeeper is run outside of HBase, the process is called `QuorumPeer`.
  -For more about ZooKeeper configuration, including using an external ZooKeeper instance with HBase, see <<zookeeper,zookeeper>>.
  +For more about ZooKeeper configuration, including using an external ZooKeeper instance with HBase, see <<zookeeper,zookeeper>> section.
   ====
   
   . Browse to the Web UI.
  
positive.code: If you get an error indicating that Java is not installed,
  but it is on your system, perhaps in a non-standard location,
  edit the _conf/hbase-env.sh_ file and modify the `JAVA_HOME`
  setting to point to the directory that contains _bin/java_ your system.
  
  
  [[shell_exercises]]
  
negative.code: +
  If everything is set up correctly, you should be able to connect to the UI for the Master
  `http://node-a.example.com:16010/` or the secondary master at `http://node-b.example.com:16010/`
   using a web browser.
  If you can connect via `localhost` but not from another host, check your firewall rules.
  You can see the web UI for each of the RegionServers at port 16030 of their IP addresses, or by
  clicking their links in the web UI for the Master.
  
  . Test what happens when nodes or services disappear.
  +
  With a three-node cluster you have configured, things will not be very resilient.
  You can still test the behavior of the primary Master or a RegionServer by killing the associated processes and watching the logs.
  
  
  === Where to go next
  