Update README.md (elsewhencode#168)

Github -> GitHub
github -> GitHub

Author: eltociear

README.md

@@ -95,7 +95,7 @@ There are a set of rules to keep in mind:
 
   _Why:_
 
-  > It protects your production-ready branches from receiving unexpected and irreversible changes. read more... [Github](https://help.github.com/articles/about-protected-branches/), [Bitbucket](https://confluence.atlassian.com/bitbucketserver/using-branch-permissions-776639807.html) and [GitLab](https://docs.gitlab.com/ee/user/project/protected_branches.html)
+  > It protects your production-ready branches from receiving unexpected and irreversible changes. read more... [GitHub](https://help.github.com/articles/about-protected-branches/), [Bitbucket](https://confluence.atlassian.com/bitbucketserver/using-branch-permissions-776639807.html) and [GitLab](https://docs.gitlab.com/ee/user/project/protected_branches.html)
 
 <a name="git-workflow"></a>
 
@@ -210,7 +210,7 @@ Having a good guideline for creating commits and sticking to it makes working wi
 - For projects with more than one repository, provide links to them in their respective `README.md` files.
 - Keep `README.md` updated as a project evolves.
 - Comment your code. Try to make it as clear as possible what you are intending with each major section.
-- If there is an open discussion on github or stackoverflow about the code or approach you're using, include the link in your comment.
+- If there is an open discussion on GitHub or stackoverflow about the code or approach you're using, include the link in your comment.
 - Don't use comments as an excuse for a bad code. Keep your code clean.
 - Don't use clean code as an excuse to not comment at all.
 - Keep comments relevant as your code evolves.