Fix up contributor list links

Created by: eliedrian

Some links are broken, I've fixed them.

.github/CONTRIBUTING.md

+# Contribution guide
+
+Welcome to your first contribution. :heart:
+
+#### Before Contributing:
+You need to run it locally on your desktop.
+
+In order to do that:
+
+Move to the desired location where package.json file is located
+
+- Install npm(latest version) -
+    npm is distributed with Node.js - which means that when you download Node.js,
+    you automatically get npm installed on your computer.
+    https://www.npmjs.com/get-npm
+- Install all the dependencies used by this project.
+   Use this command:  `install npm`
+
+- Run these final commands to run it locally:
+
+  `npm run build`
+  
+  `npm start`
+
+#### Table Of Contents
+- [Code of Conduct](#code-of-conduct)
+- [Translation Guide](#translation-guide)
+
+## Code of Conduct
+If you want to contribute, you need to know a few things.
+
+[Code of conduct](../CODE_OF_CONDUCT.md)
+
+## Translation Guide
+We have some rules for translation. If you make the first translation for your language, you must add your language list on `Translations.md`.
+
+#### Example
+
+`Translations.md`
+```markdown
+|Country | Translated Link |
+| --- | --- |
+| English | [English](../README.md) |
+| 🇮🇳 India | [Hindi](../translations/README.hi.md) |
+| 🇲🇲 Myanmar | [Myanmar Unicode](../translations/README.mm_unicode.md), Myanmar ZawGyi |
+```
+
+## TODO
+- [ ] Fix the grammar for the contribution guide.
+- [ ] Add more examples and more guides.
+
+
+Thanks! :heart:

.github/ISSUE_TEMPLATE.md

+<!--- Provide a general summary of the issue in the Title above -->
+
+🐞 **Problem**
+<!--- Provide a detailed description of the change or addition you are proposing -->
+<!--- If it is a feature or a bug, what problem is it solving-->
+
+🎯 **Goal**
+<!--- Why is this change important to you? How would you use it? -->
+<!--- How can it benefit other users? -->
+
+💡 **Possible solutions**
+<!--- Not obligatory, but suggest an idea for implementing addition or change -->
+
+📋  **Steps to solve the problem**
+
+*   Comment below about what you've started working on.
+*   Add, commit, push your changes.
+*   Submit a pull request and add this in comments - `Addresses #<put issue number here>`
+*   Ask for a review in comments section of pull request.
+*   Celebrate your contribution to this project. 🎉

additional-material/git_workflow_scenarios/Useful-links-for-further-learning.md

+# Useful Links
+
+This document is dedicated to all the blog posts, helpful sites, tips and tricks websites that makes our lives easier. That we refer to for all our needs, be it a beginner or an expert. This page should act as an index of all those useful links that would help everybody who is new in the open-source domain or someone who wants to learn more.
+
+## The List
+1.  [Interactive tutorial to git](https://try.github.io)
+2.  [git - the simple guide](http://rogerdudler.github.io/git-guide/)
+3.  [On undoing, fixing, or removing commits in git](http://sethrobertson.github.io/GitFixUm/fixup.html)
+4.  [Git and GitHub tutorial translated to many languages](https://github.com/Roshanjossey/first-contributions)
+5.  [Merge Conflicts](https://www.git-tower.com/learn/git/ebook/en/command-line/advanced-topics/merge-conflicts)
+6.  [Resolving Merge Conflicts](https://githowto.com/resolving_conflicts)
+7.  [Official Git cheat sheet in many languages](https://services.github.com/on-demand/resources/cheatsheets)
+8.  [Git cheat sheet from Tower](https://www.git-tower.com/learn/cheat-sheets/git)
+9.  [Common Git Problems](https://www.codementor.io/citizen428/git-tutorial-10-common-git-problems-and-how-to-fix-them-aajv0katd)
+10. [Git Rebase](https://blog.gitprime.com/git-rebase-an-illustrated-guide/)
+11. [Beginner's Guide to Rebasing and Squashing](https://github.com/servo/servo/wiki/Beginner%27s-guide-to-rebasing-and-squashing)
+12. [Git Cheatsheet that shows correlations between commands and files](http://ndpsoftware.com/git-cheatsheet.html)
+13. [How to contribute](https://opensource.guide/how-to-contribute/)
+14. [Getting started with Open Source](https://github.com/OpenSourceHelpCommunity/Getting-Started-With-Contributing-to-Open-Sources)
+15. [How to contribute](https://github.com/freeCodeCamp/how-to-contribute-to-open-source)
+16. [Atlassians Git Tutorials](https://www.atlassian.com/git)
+17. [Pull request reviews](https://help.github.com/articles/about-pull-request-reviews/)
+18. [Another Interactive tutorial for git](https://learngitbranching.js.org/)
+19. [Git commandline cheat-sheet](https://gist.github.com/davfre/8313299)
+20. [Programming Books](https://github.com/EbookFoundation/free-programming-books)
+
+Keep adding more links, that you find helpful.
+20. [tutorial about simple rules of become git professional](https://medium.freecodecamp.org/follow-these-simple-rules-and-youll-become-a-git-and-github-master-e1045057468f)

additional-material/git_workflow_scenarios/additional-material.md

+# Additional information
+
+We assume that you have already finished with the basic tutorial before coming here. The additional information will give you some information about advanced Git techniques.
+
+### [Amending a commit](amending-a-commit.md)
+This document provides information about how to amend a commit on the remote repository.
+> Use this when you need to adjust a commit you made.
+
+### [Configuring git](configuring-git.md)
+This document provides information about how to configure user details and other options in git.
+> Use this to better control your git configurations.
+
+### [Keeping your fork synced with the repository](keeping-your-fork-synced-with-this-repository.md)
+This document provides information about how to keep your forked repository up-to-date with the base repository. This is important, as hopefully you and many others will contribute to the project.
+> Follow these steps if your fork doesn't have any changes in parent repository.
+
+### [Moving a Commit to a different Branch](moving-a-commit-to-a-different-branch.md)
+This document provides information about how to move a Commit to another Branch.
+> Take these steps to move a commit to another branch.
+
+### [Removing a File](removing-a-file.md)
+This document provides information about how to remove a file from your local repository.
+> Follow these steps to learn how to remove a file prior to a commit
+
+### [Removing a branch from your repository](removing-branch-from-your-repository.md)
+This document provides information about how to delete a branch from your repository.
+> Only do these steps after your pull request get's merged.
+
+### [Resolving Merge Conflicts](resolving-merge-conflicts.md)
+This document provides information about how to resolve merge conflicts.
+> Take these steps to resolve the annoying merge conflicts.
+
+### [Reverting a commit](reverting-a-commit.md)
+This document provides information about how to revert a commit on the remote repository. It comes in handy in case for when you need to undo a commit that has already been pushed to Github.
+> Take these steps if you want to reverse a commit.
+
+### [Squashing Commits](squashing-commits.md)
+This document provides information about how to squash commits with an interactive rebase.
+> Use this if you want to open a PR in an open source project and the reviewer asks you to squash every commit into one, with an informative commit message.
+
+### [Undo-ing a local commit](undoing-a-commit.md)
+This document provides information about how to undo a commit on your local repository. This is what you need to do when you feel you've messed up your local repository and wish to reset the local repository.
+> Take these steps if you want to undo/reset a local commit.
+
+### [Useful Links](Useful-links-for-further-learning.md)
+This document is dedicated to all the blog posts, helpful sites, tips and tricks websites that makes our lives easier. That we refer to for all our needs, be it a beginner or an expert. This page should act as an index of all those useful links that would help everybody who is new in the open-source domain or someone who wants to learn more.

additional-material/git_workflow_scenarios/amending-a-commit.md

+# Amending a Commit
+
+What if you commit a change to your remote repository only to realize later that you have a typo in the commit message or you forgot to add a line in your most recent commit.
+How do you edit that? This is what this tutorial covers.
+
+## Changing a recent commit message after you have pushed to Github.
+To do this without opening a file:
+*   Type in the ```git commit --amend -m "followed by your new commit message"```
+*   Run ```git push origin <branch-name>``` to commit the changes to the repository.
+
+Note: If you type in just ```git commit --amend```, your text editor would open up prompting you to edit the commit message.
+Adding the ``-m`` flags prevents it.
+
+## Modifying on a single commit
+
+So, what if we forgot to make a minor change to a file like changing a single word and we have already pushed the commit to our remote repository?
+
+To illustrate here is a log of my commits:
+```
+g56123f create file bot file
+a2235d updated contributor.md
+a5da0d modified bot file
+```
+Let's say I forgot to add a single word to the bot file
+
+There are 2 ways to go about this. The first is to have an entirely new commit that contains the change like so:
+```
+g56123f create file botfile
+a2235d updated contributor.md
+a5da0d modified botfile
+b0ca8f added single word to botfile
+```
+The second way is to amend the a5da0d commit, add this new word and  push it to Github as one commit.
+The second sounds better since it is just a minor change.
+
+To achieve this, we would do the following:
+*   Modify the file. In this case, I will modify the botfile to include the word I omitted previously.
+*   Next, add the file to the staging area with ```git add <filename>```
+
+Usually after adding files to the staging area, the next thing we do is git commit -m "our commit message" right?
+But since what we want to achieve here is to amend the previous commit, we would instead run:
+
+* ```git commit --amend```
+ This would then bring up the text editor and prompt you to edit the message. You can decide to leave the message as it was before or change it.
+* Exit the editor
+* Push your changes with `` `git push origin <branch-name>` ``
+
+That way, both changes would be in one single commit.