README.md in gitscrub-0.0.7 vs README.md in gitscrub-0.0.8

@@ -17,11 +17,12 @@
  * play - This is the default command and it will check your solution for the current level.
  * hint - Gives you a hint (if available) for the current level
  * reset - Reset the current level
 
 
- ##Contributing
+##Contributing
+
  Get yourself on the [contributors list](https://github.com/Gazler/gitscrub/contributors) by doing the following:
 
   * Fork the repository
   * Make a level using the DSL (covered below)
   * Add your level to the LEVELS array inside `lib/gitscrub/level.rb` in a position that makes sense (the "commit" level after the "add" and "init" levels for example)
@@ -64,11 +65,9 @@
     end
 
  By default, `setup` will remove all files from the game folder.  You do not need to include a setup method if you don't want an initial git repository (if you are testing `git init` or only checking an answer.)
  
  You can call `repo.init` to initialize an empty repository with a .gitignore file. It takes a single parameter of false if you want to skip the initial commit of the .gitignore file.
-
- All methods called on `repo` are sent to the grit gem if the method does not existyou want to skip the initial commit of the .gitignore file.
 
  All methods called on `repo` are sent to the [grit gem](https://github.com/mojombo/grit) if the method does not exist, and you can use that for most git related commands (`repo.add`, `repo.commit`, etc.)
 
 
 Another method exists called `init_from_level` and it is used like so: