Edited for clarity and concision (#108)

To help readers understand better and improve readability.

Author: Git-Good

CONTRIBUTING.md

@@ -1,21 +1,21 @@
 ## Contributing
 
-When contributing to this repository, if it is a non-trivial change, please first discuss the change you wish to make via creating an issue in this repository.
+When contributing non-trivial changes to this repository, please first discuss the change you wish to make by creating a pull request in this repository.
 
 ### Submitting New Questions
 
-We typically do not accept submissions for new questions. This is because the [original questions repository](https://github.com/h5bp/Front-end-Developer-Interview-Questions) has been curated by a team of industry professionals and we use it as ground truth and keep our answers in sync with the questions/answers as much as possible. If you are keen to add a question/answer, firstly try to submit an issue/pull request to that repository, once your question is merged, you can then make a pull request with your answers to this repository.
+The [original questions repository](https://github.com/h5bp/Front-end-Developer-Interview-Questions) has been curated by a team of industry professionals. We use it as ground truth and keep our answers in sync with their questions/answers as much as possible. If you are keen to add a question/answer, submit an issue/pull request to the [original questions repository](https://github.com/h5bp/Front-end-Developer-Interview-Questions). Once your question is merged, make a pull request with your answers to this repository.
 
 ### Answering Questions
 
-You are welcome to make improvements to existing answers and/or answer unanswered questions. Try to add a list of references you used when arriving at the answers or any supplementary material that might be useful. This would be helpful for readers who would like to go further in-depth into the answer.
+You are welcome to make improvements to existing answers and answer unanswered questions. Whenever possible, add a list of references and supplementary material. This would be helpful for readers who would like to go further in-depth into the answer.
 
-As much as possible, try to follow the existing format of markdown and code. Any JavaScript code added should adopt [Standard style](https://standardjs.com/).
+Follow the existing format of markdown and code. JavaScript code added should adopt [Standard style](https://standardjs.com/).
 
 ### Translations
 
-Feel free to add translations for the questions and answers only. You might want to retrieve a translated copy of the questions from [the original repository](https://github.com/h5bp/Front-end-Developer-Interview-Questions) and start from there. Simply create an issue expressing interest in being a translator and you can fork the repository and start translating. Translators have the responsibility of keeping the translated content up to date with the master copy. Translated work has to go through the Pull Request and review process before it can be merged into the repository. This is more for organizational purposes as different translators tend to have individual collaboration approach (some prefer merging, some prefer rebasing). Going through a Pull Request process will make the commit history more organized and clean.
+Feel free to add translations for the questions and answers only. You can retrieve a translated copy of the questions from [the original repository](https://github.com/h5bp/Front-end-Developer-Interview-Questions) and start from there. Simply create an issue expressing interest in being a translator and you can fork the repository and start translating. Translators have the responsibility of keeping the translated content up to date with the master copy. Translated work has to go through the Pull Request and review process before it can be merged into the repository. This is more for organizational purposes as different translators tend to have individual collaboration approach (some prefer merging, some prefer rebasing). Going through a Pull Request process will make the commit history more organized and clean.
 
 ### Code of Conduct
 
-Please note we have a Code of Conduct, please follow it in all your interactions with the project.
+Please note our Code of Conduct and follow it in all your interactions with the project.