update readme

README.md

@@ -192,7 +192,12 @@ In Terms of Contract Testing you should always proceed according to the followin
 	* define your contract
 	* verify your contract against a mock
 	* publish your contract
-* End up implementing 
+* End up verifying the contract on Producer side
+
+> **_A few words in advance:_ Don't get confused by the Consumer / Producer wording - it is not related to the data flow!** 
+> **Producer in the context of Pact describes who is providing the API.**
+> **That means for instance if you make a POST-request to an API - the API providing application is the _Producer_, where the application that is doing the request is the _Consumer_ on the other hand.**
+
 
 Regarding the example implementations we will focus on the **[HTTP based integration](#rest-example-server-to-server-communication) first** and _later on_ we having a look at [**messaging queues**](#messaging-example).
 
@@ -209,10 +214,6 @@ Defining a Pact should be splitted into 3 steps:
 
 > If you are looking for an example on how to define a contract by using Javascript go [here](#javascript-consumer).  
 
-> **_A few words in advance:_ Don't get confused by the Consumer / Producer wording - it is not related to the data flow!** 
-> **Producer in the context of Pact describes who is providing the API.**
-> **That means for instance if you make a POST-request to an API - the API providing application is the _Producer_, where the application that is doing the request is the _Consumer_ on the other hand.**
-
 ### Define
 We'll start defining our Pact at the **Consumer** Application. 
 I mean hey, we want to work Consumer Driven and who could know its