Update CONTRIBUTING.md

Signed-off-by: Lilis Iskandar <[email protected]>

CONTRIBUTING.md

@@ -1,15 +1,15 @@
 # Contribution Guide
 
 ## Checklist
-These are loose checklist that contributors can follow.
+These are loose checklist for contributors to follow when submitting patches.
 
 1. Small commits
 
    You can contribute by a lot of ways from improving README, fixing typos, coding style, specific bugs, performance optimizations. However, it is preferred that you break up your commits to single logical change using `git add -p` so it is easier to review the patch. The larger the change, the more necessary it is for the commit to be broken up to tiny little pieces. If your change is large but consistent throughout (e.g. fixing a specific coding style that happens on almost every file), that can be counted as single logical change.
 
 2. File and directory-based commit message
 
-   We're starting to use commit messages that looks like this: `sdl: fixed some typos in render.go` or `examples: render_goroutine: fixed a dereferenced nil pointer` where it starts with folder hierarchy. It's not something strictly required but we would prefer it to be followed.
+   We're starting to use commit messages that looks like this: `sdl: fixed some typos in render.go` or `examples/render_goroutine: fixed a dereferenced nil pointer` where it starts with folder hierarchy. It's not something strictly required but we would prefer it to be followed.
 
 3. Compatibility with SDL 2.0.0