remove references to datagrid

docs/CM_FAQs.adoc

@@ -24,7 +24,7 @@ Also, is there a reason these `1000` `gets` have be done serially in one thread?
 
 === Answer
 
-The stateless client has been replaced with Chronicle Datagrid. The stateless client is not supported in ChronicleMap 3.x.  For  more information, please refer to Chronicle Datagrid FAQ's.
+The stateless client is not supported in ChronicleMap 3.x. For more information, please contact [email protected].
 
 For `get()s`, parallelizing will reduce costs. For `put()s`, if you have concurrency requirements, that is, multi-key lock before updating all of them, it should be in one thread.
 

docs/CM_Features.adoc

@@ -128,13 +128,6 @@ Please contact us at mailto:[email protected][[email protected]] i
 
 NOTE: For access to commercially available features please contact mailto:[email protected][[email protected]].
 
-== Peer projects
- - Chronicle Datagrid.  Reactive processing framework
- supporting Chronicle Map as a backend.
-
- - http://vanillajava.blogspot.com/2015/09/chronicle-journal-customizable-data.html[Chronicle Journal]. Another
- key-value built by Chronicle Software, with different properties.
-
 == Community support:
  - https://github.com/OpenHFT/Chronicle-Map/issues[Issues]
  - https://groups.google.com/forum/#!forum/chronicle-map[Chronicle Map mailing list]

docs/CM_Updates.adoc

@@ -18,9 +18,9 @@ Changes between Chronicle Map 3 and the previous Chronicle Map version are detai
 
  - "Listeners" mechanism fully reworked; see <<CM_Tutorial_Behaviour.adoc#,Behaviour Customization>>. This has a number of important consequences, most notable is that it is now possible to define "eventual-consistency" replication strategy, different from "last write wins"; any state-based CRDT.
 
- - "Stateless clients" functionality (remote calls) is moved to Chronicle Datagrid.
+ - "Stateless clients" functionality (remote calls) has been removed. Contact [email protected] if you need help with this.
 
- - Replication is performed using Chronicle Datagrid.
+ - Replication is performed using Chronicle Queue Enterprise.
 
  - Earlier versions of Chronicle Map had hard creation-time limits on the number of entries storable in a Chronicle Map. If the size exceeded this limit, an exception was thrown. +
  In Chronicle Map 3, this limitation is removed. The number of entries still has to be configured when the Chronicle Map is created, Exceeding this configured limit is possible, but discouraged. +