diff --git a/voxxed-microservices-2018/module-02.adoc b/voxxed-microservices-2018/module-02.adoc
index 887ebf5..07bb972 100644
--- a/voxxed-microservices-2018/module-02.adoc
+++ b/voxxed-microservices-2018/module-02.adoc
@@ -90,7 +90,7 @@ which can be used for building and running Java applications on OpenShift.
 
 [source,sh]
 ----
-$ oc new-app --name=order-msa debezium/msa-lab-s2i:latest~https://github.com/debezium/microservices-lab \
+$ oc new-app --name=order-msa debezium/msa-lab-s2i:latest~https://github.com/<your fork>/microservices-lab#module2 \
     --context-dir=ticket-msa/order \
     -e MYSQL_DATABASE=inventory \
     -e AB_PROMETHEUS_OFF=true \
diff --git a/voxxed-microservices-2018/module-03.adoc b/voxxed-microservices-2018/module-03.adoc
index e5e7033..b7c1969 100644
--- a/voxxed-microservices-2018/module-03.adoc
+++ b/voxxed-microservices-2018/module-03.adoc
@@ -252,8 +252,6 @@ $ oc exec -c zookeeper -it my-cluster-zookeeper-0 -- /opt/kafka/bin/kafka-consol
    --topic EventrOrder
 ----
 
-Note: if you didn't scale down the cluster to a single node in module 1, please use `my-cluster-kafka-bootstrap:9092` as bootstrap server instead.
-
 Note that by default topic names follow the pattern "<db server name>.<db name>.<table name>".
 By means of the `RegexRouter` in the connector configuration we've changed that so that the topic name is just the unqualified table name.
 You should see messages comprising of a key and a value like the following (formatted for the sake readability),
@@ -807,8 +805,6 @@ $ oc exec -c zookeeper -it my-cluster-zookeeper-0 -- /opt/kafka/bin/kafka-consol
    --topic orders_with_event
 ----
 
-Note: if you didn't scale down the cluster to a single node in module 1, please use `my-cluster-kafka-bootstrap:9092` as bootstrap server instead.
-
 Let's deploy another instance of the Elasticsearch sink connector for streaming the aggregate events into Elasticsearch:
 
 [source,sh]