diff --git a/exercises/11-aem-cloud-integration-adapter/README.md b/exercises/11-aem-cloud-integration-adapter/README.md
index c221d50..daa05b2 100644
--- a/exercises/11-aem-cloud-integration-adapter/README.md
+++ b/exercises/11-aem-cloud-integration-adapter/README.md
@@ -6,9 +6,12 @@ In previous exercises, we've communicated with SAP Integration Suite, advanced e
- REST protocol, from the Node.js application in exercise 08.
- AMQP protocol, from the CAP project in exercise 10.
-Now, in this exercise, we will consume the events from AEM using the Cloud Integration service. We will leverage the [AEM adapter](https://hub.sap.com/integrationadapter/AdvancedEventMesh) available and use it in an integration flow to consume the purchased tickets events from a queue in AEM (the AEM adapter uses the Solace Messaging protocol). We will then enrich the message and publish it to a topic. As explained in the previous exercise, there is a separate service that simulates the ticket purchased events from the ticket website. We will extend the consumption of those events in this exercise.
+Now, in this exercise, we will consume the events from AEM using the Cloud Integration service. We will leverage the [AEM adapter](https://hub.sap.com/integrationadapter/AdvancedEventMesh) available and use it in an integration flow to consume the purchased tickets events from a queue in AEM (the AEM adapter uses the Solace Messaging protocol). We will then enrich the message and publish it to a topic. As explained in the previous exercise, there is a separate service that simulates the ticket purchased events from the ticket website. We will extend the consumption of those events in this exercise. By the end of this exercise, we will achieve a communication scenario like the one below.
-
+
+ 
+ Consuming and publishing messages from a Cloud Integration iFlow
+
> The goal of this exercise is not to create an integration flow from scratch but to get familiar with the AEM integration adapter and understand the connectivity mechanism between AEM and Cloud Integration.
@@ -16,13 +19,6 @@ Before we get started, make a note of the connection details for the Solace Mess
-By the end of this exercise, we will achieve a communication scenario like the one below.
-
-
-
- Consuming and publishing messages from a Cloud Integration iFlow
-
-
## Queue for Cloud Integration
👉 Access the `EU-North-Broker` and clone the queue created in the previous exercise and name it: `codejam/edi/[your-sap-community-username]/Tickets/Purchased_CloudIntegration`. Make sure to also clone the subscriptions.