diff --git a/Running-Unit-Tests.md b/Running Unit Tests.md
similarity index 81%
rename from Running-Unit-Tests.md
rename to Running Unit Tests.md
index ab88aae..dc3cc8e 100644
--- a/Running-Unit-Tests.md
+++ b/Running Unit Tests.md	
@@ -10,8 +10,7 @@ The tests are located in the `Source/UnitTests` directory and use the [Google Te
 The UnitTests project is compiled as part of the normal build on Windows.  
 There are a few ways to run the tests:
 
-1. Using the [GoogleTest Runner](http://visualstudiogallery.msdn.microsoft.com/9dd47c21-97a6-4369-b326-c562678066f0) extension for Visual Studio in order to integrate tests into the Test Explorer.  
-Requires a version of Visual Studio supporting extensions.
+1. Using the [GoogleTest Runner](http://visualstudiogallery.msdn.microsoft.com/9dd47c21-97a6-4369-b326-c562678066f0) extension for Visual Studio in order to integrate tests into the Test Explorer. This requires a version of Visual Studio that supports the use of extensions.
 
 2. Invoking execution via msbuild with the `RunUnitTests` property, for example:  
   ```
@@ -19,7 +18,7 @@ Requires a version of Visual Studio supporting extensions.
   msbuild /v:m /m /p:Platform=x64 /p:Configuration=Release /p:RunUnitTests=true dolphin-emu.sln
   ```
 
-3. You can of course also go to the UnitTests build output directory and directly run the binary:
+3. You can, of course, also go to the UnitTests build output directory and directly run the binary:
   ```
   pushd Build\x64\Release\UnitTests\bin
   UnitTests