diff --git a/GSoC-2015-Ideas.md b/GSoC-2015-Ideas.md
index f4df651..736e489 100644
--- a/GSoC-2015-Ideas.md
+++ b/GSoC-2015-Ideas.md
@@ -132,7 +132,7 @@ yet documented: It's done in a pretty adhoc fashion that mostly uses
 the transitivity of inequality relations and some simple control flow analysis.
 
 However, in the context of *optimization* and code generation there has been
-lots of progress in commercial comilers in the form of auto vectorization.
+lots of progress in commercial compilers in the form of auto vectorization.
 One such framework that enables auto vectorization is the polyhedral model.
 The polyhedral model deals with iteration spaces and serves to parallelize loop
 programs automatically by applying algebraic transformations. As it is a
@@ -190,7 +190,10 @@ documentation should be installed on the system as well.
   * Add cross-linking capabilities in nim doc
   * Make nimble build and install the documentation locally so you have
     docs of all your installed libraries
-  * Automatically create an online documentation of each nimble package
+  * Automatically create online documentation of each nimble package
+
+**Bonus Points:**
+  * Implement testing of the examples in the documentation into the ``testament`` test suite.
 
 **Difficulty:** Easy to Medium
 
@@ -214,7 +217,7 @@ ___
 #### MPI support
 
 Message Passing Interface (MPI) is a portable system for writing highly
-parallel programs. Nim with its excellent performance/productivity ratio would
+parallel programs. Nim, with its excellent performance/productivity ratio, would
 make a great language for this use.
 
 **Tasks**:
@@ -231,10 +234,10 @@ make a great language for this use.
 #### nimfmt: Automatically format Nim code
 
 Gofmt is often cited as one of the major points for the Go programming
-language. It completely elimantes the need to manually adhere to style
-formatting, by automatically converting go code into a consistent style.
+language. It completely eliminates the need to manually adhere to style
+formatting, by automatically converting Go code into a consistent style.
 Something similar would be nice to have in Nim, where we have additional
-freedoms, like case insensitivity, that should be handled in a onsistent way
+freedoms, like case insensitivity, that should be handled in a consistent way
 for big projects.
 
 **Tasks**: