diff --git a/ReadMe.adoc b/ReadMe.adoc
index 166c15c7e..349c1e841 100755
--- a/ReadMe.adoc
+++ b/ReadMe.adoc
@@ -81,7 +81,9 @@ Replication is multi-master, lock-free, redundant, deterministic, and eventually
 
 The writer can optionally wait for replication to occur across nodes or regions.
 
-NOTE: See <<docs/CM_Replication.adoc#,Chronicle Map Replication>> for more information.
+NOTE: Chronicle Map Replication is a Chronicle Map (Enterprise Edition) feature. +
+For more information on Chronicle Map (Enterprise Edition), please contact mailto:sales@chronicle.software[sales@chronicle.software]. +
+See <<docs/CM_Replication.adoc#,Chronicle Map Replication>> for more information.
 
 '''
 == Documentation
diff --git a/docs/CM_Features.adoc b/docs/CM_Features.adoc
index a1d1bb9e8..9b461998e 100755
--- a/docs/CM_Features.adoc
+++ b/docs/CM_Features.adoc
@@ -34,6 +34,9 @@ applications, such as trading and financial market applications.
  doesn't sustain write rates.
 
 
+NOTE: Chronicle Map Replication is a Chronicle Map (Enterprise Edition) feature. +
+For more information on Chronicle Map (Enterprise Edition), please contact mailto:sales@chronicle.software[sales@chronicle.software].
+
 NOTE: See <<CM_Replication.adoc#,Chronicle Map Replication>> for more information.
 
 **Chronicle Map** has two meanings:
diff --git a/docs/CM_Replication.adoc b/docs/CM_Replication.adoc
index 949f7e511..ad3fbb18d 100755
--- a/docs/CM_Replication.adoc
+++ b/docs/CM_Replication.adoc
@@ -24,7 +24,10 @@ For more information on the stress test see <<CM_Replication_Stress_Test.adoc#,C
 
 = Replication
 
-Chronicle Map Replication is a multi-master replicated data store. Chronicle Map supports both TCP and UDP replication
+Chronicle Map Replication is a multi-master replicated data store. Chronicle Map supports both TCP and UDP replication.
+
+NOTE: Chronicle Map Replication is a Chronicle Map (Enterprise Edition) feature. +
+For more information on Chronicle Map (Enterprise Edition), please contact mailto:sales@chronicle.software[sales@chronicle.software].
 
 image::http://openhft.net/wp-content/uploads/2014/07/Chronicle-Map-TCP-Replication_simple_02.jpg[TCP/IP Replication]
 
@@ -44,6 +47,9 @@ We are careful not to swamp your network with too much TCP/IP traffic. We do thi
 == How Chronicle Map Replication works
 Chronicle Map provides multi-master hash-map replication. This means that each remote map mirrors its changes over to another remote map. Neither map is considered to be the master store of data. Each map uses timestamps to reconcile changes.
 
+NOTE: Chronicle Map Replication is a Chronicle Map (Enterprise Edition) feature. +
+For more information on Chronicle Map (Enterprise Edition), please contact mailto:sales@chronicle.software[sales@chronicle.software].
+
 We refer to an instance of a remote map as a **node**. Each node can be connected to up to 128 other nodes.
 
 The data that is stored locally in each node becomes eventually consistent. So changes made to one node, for example by calling `put()`, will be replicated over to the other node.