Updated README.md

Using scala markup notation.

Author: manub

README.md

@@ -20,52 +20,56 @@ scalatest-embedded-kafka is available on Bintray and Maven Central, compiled for
 * In your `build.sbt` file add the following dependency: `"net.manub" %% "scalatest-embedded-kafka" % "0.9.0" % "test"`
 * Have your `Spec` extend the `EmbeddedKafka` trait.
 * Enclose the code that needs a running instance of Kafka within the `withRunningKafka` closure.
+```scala
+class MySpec extends WordSpec with EmbeddedKafka {
 
-        class MySpec extends WordSpec with EmbeddedKafka {
-    
-        "runs with embedded kafka" should {
+"runs with embedded kafka" should {
 
-            withRunningKafka {
-                // ... code goes here
-            }
-        
-        }
+    withRunningKafka {
+        // ... code goes here
+    }
 
+}
+```
 * In-memory Zookeeper and Kafka will be instantiated respectively on port 6000 and 6001 and automatically shutdown at the end of the test.
 
 ### Use without the `withRunningKafka` method
 
 A `EmbeddedKafka` companion object is provided for usage without the `EmbeddedKafka` trait. Zookeeper and Kafka can be started an stopped in a programmatic way.
 
-        class MySpec extends WordSpec {
+```scala
+class MySpec extends WordSpec {
 
-        "runs with embedded kafka" should {
-        
-            EmbeddedKafka.start()
-            
-            // ... code goes here
-            
-            EmbeddedKafka.stop() 
-        
-        }
+"runs with embedded kafka" should {
+
+    EmbeddedKafka.start()
+    
+    // ... code goes here
+    
+    EmbeddedKafka.stop() 
+
+}
+```
 
 Please note that in order to avoid Kafka instances not shutting down properly, it's recommended to call `EmbeddedKafka.stop()` in a `after` block or in a similar teardown logic. 
 
 ## Configuration
 
 It's possible to change the ports on which Zookeeper and Kafka are started by providing an implicit `EmbeddedKafkaConfig`
 
-        class MySpec extends WordSpec with EmbeddedKafka {
-    
-        "runs with embedded kafka on a specific port" should {
+```scala
+class MySpec extends WordSpec with EmbeddedKafka {
 
-            implicit val config = EmbeddedKafkaConfig(kafkaPort = 12345)
+"runs with embedded kafka on a specific port" should {
 
-            withRunningKafka {
-                // now a kafka broker is listening on port 12345
-            }
-        
-        }
+    implicit val config = EmbeddedKafkaConfig(kafkaPort = 12345)
+
+    withRunningKafka {
+        // now a kafka broker is listening on port 12345
+    }
+
+}
+```
 
 This works for both `withRunningKafka` and `EmbeddedKafka.start()`
 
@@ -79,12 +83,14 @@ are.
 
 The `EmbeddedKafka` trait provides also some utility methods to interact with the embedded kafka, in order to set preconditions or verifications in your specs:
 
-        def publishToKafka(topic: String, message: String): Unit
-        
-        def consumeFirstMessageFrom(topic: String): String
+```scala
+def publishToKafka(topic: String, message: String): Unit
+
+def consumeFirstMessageFrom(topic: String): String
+
+def createCustomTopic(topic: String, topicConfig: Map[String,String], partitions: Int, replicationFactor: Int): Unit
+```
 
-        def createCustomTopic(topic: String, topicConfig: Map[String,String], partitions: Int, replicationFactor: Int): Unit
-        
 ## Custom producers
 
 It is possible to create producers for custom types in two ways: