diff --git a/_posts/04-02-01-Composer-and-Packagist.md b/_posts/04-02-01-Composer-and-Packagist.md
index 4caa9ea..9374866 100644
--- a/_posts/04-02-01-Composer-and-Packagist.md
+++ b/_posts/04-02-01-Composer-and-Packagist.md
@@ -41,13 +41,11 @@ When you come across documentation that states to run Composer as `php composer.
 
 First, create a `composer.json` file in the same directory as `composer.phar`. Here's an example that lists [Twig][2] as a project dependency.
 
-{% highlight json %}
-{
-    "require": {
-        "twig/twig": "1.8.*"
-    }
-}
-{% endhighlight %}
+	{
+	    "require": {
+	        "twig/twig": "1.8.*"
+	    }
+	}
 
 Next, run this command from your project root directory.
 
diff --git a/_posts/07-02-01-Test-Driven-Development.md b/_posts/07-02-01-Test-Driven-Development.md
index 7cbc98a..c663a86 100644
--- a/_posts/07-02-01-Test-Driven-Development.md
+++ b/_posts/07-02-01-Test-Driven-Development.md
@@ -18,7 +18,7 @@ var_dump() in a test.php, which is no way to build an application - large or sma
 
 The other use for unit tests is contributing to open source. If you can write a test that shows broken 
 functionality, then fix it, and show the test working, patches are much more likely to be accepted. If 
-you run a project who accepts pull requests, you should suggest this as a requirement for pull requests.
+you run a project which accepts pull requests then you should suggest this as a requirement.
 
 PHPUnit is the most popular and has become a de facto standard with its popular adoption amongst [PHP 
 frameworks][phpfws] and [Composer][composer] component developers, but there are a few alternatives around.