doc: Sketchy drawings (#880)

* doc: Sketchy drawings

* guide image is ok

akka-distributed-cluster-docs/src/main/paradox/feature-summary.md

@@ -15,9 +15,9 @@ With Projections over gRPC you could have the same advantages of loosely coupled
 without the burden and cost of operating the broker infrastructure. As a bonus, you would gain low-latency cross
 region delivery of messages.
 
-FIXME graphic that is more overview and less step by step? (this is the same as projection gRPC)
+FIXME make the drawing look nice
 
-![service-to-service-overview.png](images/service-to-service-overview.png)
+![projection-over-grpc.png](images/projection-over-grpc.png)
 
 Projections over gRPC uses the event journal on the producer side and Akka Projections event processing and offset
 tracking on the consumer side. The transparent data transfer between producers and consumers is implemented with
@@ -55,6 +55,10 @@ You would use Replicated Event Sourcing over gRPC for entities that can be updat
 location, such as different cloud regions. This makes it possible to implement patterns such as active-active and
 hot standby.
 
+FIXME make the drawing look nice
+
+![projection-over-grpc.png](images/res-over-grpc.png)
+
 Replicated Event Sourcing gives:
 
 * redundancy to tolerate failures in one location and still be operational

akka-distributed-cluster-docs/src/main/paradox/guide/2-service-to-service.md

@@ -14,8 +14,6 @@ a downstream analytics service.
 
 ## gRPC transport for consuming events
 
-FIXME graphic that is more overview and less step by step? (this is the same as projection gRPC)
-
 ![service-to-service-overview.png](../images/service-to-service-overview.png)
 
 1. An Entity stores events in its journal in service A.
@@ -185,4 +183,4 @@ FIXME running locally instructions here as well
 
 ## What's next?
 
-* Turning the shopping cart highly available through Active-Active
+* Turning the shopping cart highly available through Active-Active

akka-distributed-cluster-docs/src/main/paradox/index.md

@@ -1,5 +1,14 @@
 # Akka Distributed Cluster
 
+Akka Distributed Cluster is a set of features in Akka that will help you with:
+
+* stretching an Akka Cluster over geographically distributed locations for higher availability and lower latency
+* asynchronous communication between different Akka Microservices
+
+FIXME make the drawing look nice
+
+![projection-over-grpc.png](images/combined.png)
+
 .
 
 @@toc { depth=2 }
@@ -11,4 +20,4 @@
 * [Feature Summary](feature-summary.md)
 * [Guide](guide.md)
 
-@@@
+@@@

akka-distributed-cluster-docs/src/main/paradox/overview.md

@@ -20,6 +20,10 @@ many problems that must be overcome:
 Instead, each geographical location can be a separate, fully autonomous, Akka Cluster and be connected to the other
 Akka Clusters with the communication mechanisms provided by Akka Distributed Cluster.
 
+FIXME make the drawing look nice
+
+![projection-over-grpc.png](images/connected-clusters.png)
+
 The communication transport between the Akka Clusters is then using reliable event replication over gRPC, which
 gives characteristics such as: