anchor.diff:  = Frequently Asked Questions about Chronicle
   
  -=== SingleChronicleQueue
  +=== What is SingleChronicleQueue?
   
   Single Chronicle Queue is designed to be easier to work with compared with
   the previous Vanilla and Indexed Chronicles.
   
  -It supports;
  +It supports:
   
   - concurrent readers in different JVMs.
   - concurrent writers in different JVMs.
  
positive.code: they need and perform queries without needed to touch the critical system as they can record anything they might need later.
  
  Chronicle works best in SEDA style event driven systems, where latency is critical and you need a record of exactly what was performed when. (Without expensive network sniffing/recording systems)
  
  === What was the library originally designed for?
  
  
negative.code: - the header stores key information so there is no longer the requirement that the writers and reads be configured the same.
  - you don't need to know how big the message is.
  
  === What is Chronicle designed for?
  
  Chronicle is design to be a record everything of interest logger and persisted IPC.
  