diff --git a/articles/Two_years_with_clojure.md b/articles/Two_years_with_clojure.md
index 39a3b47..7ece68a 100644
--- a/articles/Two_years_with_clojure.md
+++ b/articles/Two_years_with_clojure.md
@@ -177,7 +177,7 @@ Further more, dealing with realtime processing at that time was all about java e
 There was Storm, Kafka, Zookeeper, etc...
 
 So using a language which could use all the java libraries seemed very important to us.
-With that in mind we simply had t choose between Scala and Clojure.
+With that in mind we simply had to choose between Scala and Clojure.
 Looking at scala, it was clear that it will be to Java what C++ is to C.
 While Clojure being a descendant from the LISP family, we found that everything was simple, easier to read and understand.
 Clojure community sounded great.
@@ -185,7 +185,7 @@ Clojure community sounded great.
 Furthermore Storm was first written in Clojure.
 So go go go!
 
-t was during summer that most technical choices were made.
+It was during summer that most technical choices were made.
 
 1. We wanted to deploy using Mesos / Marathon,
 2. Use Kafka and Storm,
@@ -199,7 +199,7 @@ Each choice was balanced.
 In the end some of those choices were changed throught practice.
 
 For instance, we discarded Storm.
-The power of core.async was more than enough efficiently exploit all the juice of our machines,
+The power of `core.async` was more than enough efficiently exploit all the juice of our machines,
 Storm added some unnecessary latency and complexity.
 
 Today you can see a result here: