diff --git a/_posts/01-04-01-Mac-Setup.md b/_posts/01-04-01-Mac-Setup.md
index 0e88359..dc06ddf 100644
--- a/_posts/01-04-01-Mac-Setup.md
+++ b/_posts/01-04-01-Mac-Setup.md
@@ -16,7 +16,7 @@ There are multiple ways to install PHP on OS X.
 [Homebrew PHP] is a repository that contains PHP-related "formulae" for Homebrew, and will let you install PHP.
 
 At this point, you can install `php53`, `php54`, `php55`, `php56`, `php70` or `php71` using the `brew install` command, and switch
-between them by modifying your `PATH` variable. Alternatively you can use [brew-php-switcher][brew-php-switcher] which will switch automatically for you.
+between them by modifying your `PATH` variable. Alternatively, you can use [brew-php-switcher][brew-php-switcher] which will switch automatically for you.
 
 ### Install PHP via Macports
 
diff --git a/_posts/02-01-01-Code-Style-Guide.md b/_posts/02-01-01-Code-Style-Guide.md
index 3365509..65e7bb5 100644
--- a/_posts/02-01-01-Code-Style-Guide.md
+++ b/_posts/02-01-01-Code-Style-Guide.md
@@ -15,7 +15,7 @@ recommendations are merely a set of rules that many projects like Drupal, Zend,
 FuelPHP, Lithium, etc are adopting. You can use them for your own projects, or continue to use your own
 personal style.
 
-Ideally you should write PHP code that adheres to a known standard. This could be any combination of PSRs, or one
+Ideally, you should write PHP code that adheres to a known standard. This could be any combination of PSRs, or one
 of the coding standards made by PEAR or Zend. This means other developers can easily read and work with your code, and
 applications that implement the components can have consistency even when working with lots of third-party code.
 
diff --git a/_posts/05-03-01-Date-and-Time.md b/_posts/05-03-01-Date-and-Time.md
index c56781a..499d074 100644
--- a/_posts/05-03-01-Date-and-Time.md
+++ b/_posts/05-03-01-Date-and-Time.md
@@ -43,7 +43,7 @@ On DateTime objects you can use standard comparison:
 {% highlight php %}
 <?php
 if ($start < $end) {
-    echo "Start is before end!\n";
+    echo "Start is before the end!\n";
 }
 {% endhighlight %}
 
diff --git a/_posts/06-02-01-Basic-Concept.md b/_posts/06-02-01-Basic-Concept.md
index 5469450..965292d 100644
--- a/_posts/06-02-01-Basic-Concept.md
+++ b/_posts/06-02-01-Basic-Concept.md
@@ -47,6 +47,6 @@ class Database
 class MysqlAdapter {}
 {% endhighlight %}
 
-Now we are giving the `Database` class its dependency rather than it creating it itself. We could even create a method
+Now we are giving the `Database` class its dependency rather than creating it itself. We could even create a method
 that would accept an argument of the dependency and set it that way, or if the `$adapter` property was `public` we
 could set it directly.
diff --git a/_posts/06-03-01-Complex-Problem.md b/_posts/06-03-01-Complex-Problem.md
index c64e723..94523d0 100644
--- a/_posts/06-03-01-Complex-Problem.md
+++ b/_posts/06-03-01-Complex-Problem.md
@@ -57,5 +57,5 @@ the adapter based on that contract.
 
 An even bigger benefit to this method is that our code is now much more scalable. If a year down the line we decide
 that we want to migrate to a different type of database, we can write an adapter that implements the original interface
-and inject that instead, no more refactoring would be required as we can ensure that the adapter follows the contract
+and injects that instead, no more refactoring would be required as we can ensure that the adapter follows the contract
 set by the interface.