anchor.diff:  
   |=======
   |`Excerpt`| In Chronicle we refer to messages as excerpts.
  -|`PRIMARY`   | The master of the messages aka `source`; messages are replicated from the PRIMARY to the SECONDARY.
  -|`SECONDARY`    | The receiver of the messages aka `sink`; holds an real-time up-to-date copy of the PRIMARY's data.
  +|`PRIMARY`   | The master of the messages; this is also known as `source`. Messages are replicated from the PRIMARY to the SECONDARY.
  +|`SECONDARY`    | The receiver of the messages; this is also known as `sink`. Holds a real-time, up-to-date copy of the PRIMARY's data.
   |=======
   
   '''
  
positive.code: 
  == Configuration File
  
  The host in a cluster are defined in a YAML configuration file. This configuration file below, has just two hosts, but there is no fixed limit to the number of hosts you could include, ultimately it is limited by your hardware resources.
  
  Each host is a running an instance of Chronicle. When using Chronicle Queue Enterprise Edition, these engines are likely to each contain a Chronicle queue. In this example below there are two hosts, one running on `localhost:8080`, and the other on `localhost:8081`. The hosts are on the same machine; in a real life example, these hosts would usually be on different machines.
  
  NOTE: The examples given below perform queue replication using established interfaces that are based on the open source Chronicle Engine API.
  
  [source, yaml]
  ----
  
negative.code: 
  The code above:
  
  - sets up Chronicle Queue on port `localhost:8080`.
  - uses the specified configuration file. This configuration file should be stored at `config/etc/clusters.yaml`.
  - configures an asset on the Chronicle Engine asset tree at `/the/uri` with a `leafRule`. This `leafRule` is setup to provide a `ChronicleQueueView` when asked for a `ChronicleQueue`. The `ChronicleQueueView` is an implementation of the `ChronicleQueue` interface.
  
  Assuming that both the `host1` and `host2` instances of Chronicle Engine were run with the same java code above, then messages added to the Chronicle queue on `host1` would be replicated to `host2`.
  
  The interface of `ChronicleQueueView`, is as follows:
  
  [source, java]
  ----
  