diff --git a/docs/CM_Overview.adoc b/docs/CM_Overview.adoc
index e2b5d7fb1..8b256f514 100755
--- a/docs/CM_Overview.adoc
+++ b/docs/CM_Overview.adoc
@@ -3,7 +3,7 @@
 Chronicle Map is a super-fast, in-memory, key-value
 store, that can overflow seamlessly to disk, and can be distributed across the network.
 
-INSERT DIAGRAM
+image::images\CM_Overview.jpg[]
 
 == Use cases
 Chronicle Map is used in production around the
@@ -25,7 +25,7 @@ low and stable microsecond latencies.
 experience solving real-world problems.
 • open source (standard version), and in use at
 hundreds of sites around the world.
-• in production at banks and hedge funds
+• in production at banks and hedge funds,
 globally.
 • reliable. Chronicle Software have a “chaos
 monkey” test which verifies Chronicle Map
@@ -42,7 +42,7 @@ your own.
 == Replication Environment Example
 The following diagram shows an example of Chronicle Map replication over 3 servers (or sites).
 
-INSERT DIAGRAM
+image::images\Configure_Three_Way_Replication.png[]
 
 Replication is multi-master, lock-free, redundant, deterministic, and eventually consistent.
 
diff --git a/docs/images/CM_Overview.jpg b/docs/images/CM_Overview.jpg
new file mode 100755
index 000000000..a4d200015
Binary files /dev/null and b/docs/images/CM_Overview.jpg differ
diff --git a/docs/images/Configure_Three_Way_Replication.png b/docs/images/Configure_Three_Way_Replication.png
new file mode 100755
index 000000000..3f741a916
Binary files /dev/null and b/docs/images/Configure_Three_Way_Replication.png differ