diff --git a/CHANGELOG.md b/CHANGELOG.md
index d9e9739..4b86215 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,12 @@
 # Changelog
 
+## Mocked Streams 1.4.0
+
+* Build against Apache Kafka 0.11.0.1
+* Added record order and multiple emissions by Svend Vanderveken
+* Updated SBT to 1.0.2
+* Added Svend Vanderveken to CONTRIBUTORS.md
+
 ## Mocked Streams 1.2.2
 
 * Build against Apache Kafka 0.11.0.0
diff --git a/README.md b/README.md
index 14a980d..c36203d 100644
--- a/README.md
+++ b/README.md
@@ -50,13 +50,13 @@ It also allows you to have multiple input and output streams. If your topology u
     mstreams.output("out-a", strings, ints, expA.size) shouldEqual(expectedA)
     mstreams.output("out-b", strings, ints, expB.size) shouldEqual(expectedB)
 
-## Event order and multiple emissions
+## Record order and multiple emissions
 
-The events provided to the mock stream will be submitted to the topology during the test in the order in which they appear in the fixture. You can also submit events multiple times to the same topics, at various moments in your scenario. 
+The records provided to the mocked stream will be submitted to the topology during the test in the order in which they appear in the fixture. You can also submit records multiple times to the same topics, at various moments in your scenario. 
 
-This can be handy to validate that your topology behaviour is or is not dependent on the order in which the events are received and processed. 
+This can be handy to validate that your topology behaviour is or is not dependent on the order in which the records are received and processed. 
 
-In the example below, 2 events are first submitted to topic A, then 3 to topic B, then 1 more to topic A again. 
+In the example below, 2 records are first submitted to topic A, then 3 to topic B, then 1 more to topic A again. 
 
     val firstInputForTopicA = Seq(("x", int(1)), ("y", int(2)))
     val firstInputForTopicB = Seq(("x", int(4)), ("y", int(3)), ("y", int(5)))