Merge pull request kennyledet#19 from pravsingh/master

kennyledet · kennyledet · commit 20dcf04fd3db · 2013-12-25T01:01:20.000-08:00
fixed types and added the conventions on writing unit test cases
diff --git a/README.md b/README.md
@@ -18,12 +18,13 @@ Conventions
 + Submissions should follow this directory structure
 	
 		Algorithm_Name/Language_Name/username_filename.extension
+		Algorithm_Name/Language_Name/username_filename_unittest.extension
     
 + It is preferred that you prepend or append your files with your Github username or some identifier to avoid overwriting others' implementations. `git blame` is cool, and has many more appropriate applications, but in this context I'd rather pull a flat list of files and be able to check out everyone's contributions that way than have to look through the revisions.
 
-+ Each algorithm should have its corresppnding unit test cases which covers the corner cases, happy/unhappy path.
-	Advantage of doing so is to asset that every thing is covered and algorithm is not broken between code change.
-	It also helps newbie to have a quick look at the unit test cases and understand the basic usecase of the algorithm.
++ Each algorithm should have its corresppnding unit test cases (as directory structure suggested above) which covers the corner cases, happy/unhappy paths.
+	Advantage of doing so is to assert that every thing is covered and algorithm is not broken between code change.
+	It also helps newbies to have a quick look at the unit test cases and understand the basic usecase of the algorithm.
 
 + Documentation inside the code is recommended. This helps others in understanding the code base.
 
