[feat/fix]: Improve the contributing guidelines (TheAlgorithms#1503)

* [feat/fix]: Improve the contributing guidelines

Mostly fix grammar, spelling errors, typos, and improves wording.

* [docs]: Apply suggestions from code review

* [feat/fix]: Minor improvements/fixes

Co-authored-by: Ayaan Khan <ayaankhan98@gmail.com>

Author: Panquesito7

CONTRIBUTING.md

@@ -2,54 +2,54 @@
 
 ## Before contributing
 
-Welcome to [TheAlgorithms/C-Plus-Plus](https://github.com/TheAlgorithms/C-Plus-Plus)! Before submitting pull requests, please make sure that you have **read the whole guidelines**. If you have any doubts about this contribution guide, please open [an issue](https://github.com/TheAlgorithms/C-Plus-Plus/issues/new/choose) and clearly state your concerns.
+Welcome to [TheAlgorithms/C-Plus-Plus](https://github.com/TheAlgorithms/C-Plus-Plus)! Before submitting pull requests, please make sure that you have **read the whole guidelines**. If you have any doubts about this contribution guide, please open [an issue](https://github.com/TheAlgorithms/C-Plus-Plus/issues/new/choose) or ask in our [Discord server](https://discord.gg/c7MnfGFGa6), and clearly state your concerns.
 
 ## Contributing
 
 ### Contributor
 
-We are very happy that you consider implementing algorithms and data structures for others! This repository is referred to and used by learners from around the globe. Being one of our contributors, you agree and confirm that:
+Being a contributor at The Algorithms, we request you to follow the points mentioned below:
 
 - You did your own work.
   - No plagiarism allowed. Any plagiarized work will not be merged.
-- Your work will be distributed under [MIT License](License) once your pull request has been merged.
-- You submitted work fulfils or mostly fulfils our styles and standards.
+- Your work will be distributed under the [MIT License](https://github.com/TheAlgoritms/C-Plus-Plus/blob/master/LICENSE) once your pull request has been merged.
+- Please follow the repository guidelines and standards mentioned below.
 
-**New implementation** New implementation are welcome!
+**New implementation** New implementations are welcome!
 
-**Improving comments** and **adding tests** to existing algorithms are much appreciated.
+You can add new algorithms or data structures which are **not present in the repository** or that can **improve** the old implementations (**documentation**, **improving test cases**, removing bugs or in any other resonable sense)
 
-**Issues** Please avoid opening issues asking to be "assigned” to a particular algorithm.  This merely creates unnecessary noise for maintainers.  Instead, please submit your implementation in a pull request and it will be evaluated by project maintainers.
+**Issues** Please avoid opening issues asking to be "assigned” to a particular algorithm. This merely creates unnecessary noise for maintainers. Instead, please submit your implementation in a pull request, and it will be evaluated by project maintainers.
 
 ### Making Changes
 
 #### Code
 
 - Please use the directory structure of the repository.
-- File extension for code should be `*.hpp`, `*.h` or `*.cpp`.
-- Don't use **bits/stdc++.h** because this is quite Linux specific and slows down the compilation process.
-- Organize your code using **`struct`**, **`class`** and/or **`namespace`** keywords
+- Make sure the file extensions should be `*.hpp`, `*.h` or `*.cpp`.
+- Don't use **`bits/stdc++.h`** because this is quite Linux-specific and slows down the compilation process.
+- Organize your code using **`struct`**, **`class`**, and/or **`namespace`** keywords
 - If an implementation of the algorithm already exists, please refer to the [file-name section below](#new-file-name-guidelines).
 - You can suggest reasonable changes to existing algorithms.
 - Strictly use snake_case (underscore_separated) in filenames.
 - If you have added or modified code, please make sure the code compiles before submitting.
-- Our automated testing runs [__CMake__](https://cmake.org/) on all pull requests so please be sure that your code passes before submitting.
-- Please conform to [doxygen](https://www.doxygen.nl/manual/docblocks.html) standard and document the code as much as possible. This not only facilitates the readers but also generates the correct info on website.
-- **Be consistent in use of these guidelines.**
+- Our automated testing runs [__CMake__](https://cmake.org/) on all the pull requests, so please be sure that your code passes before submitting.
+- Please conform to [Doxygen](https://www.doxygen.nl/manual/docblocks.html) standard and document the code as much as possible. This not only facilitates the readers but also generates the correct info on the website.
+- **Be consistent in the use of these guidelines.**
 
 #### Documentation
 
-- Make sure you put useful comments in your code.  Do not comment things that are obvious.
+- Make sure you put useful comments in your code. Do not comment on obvious things.
 - Please avoid creating new directories if at all possible. Try to fit your work into the existing directory structure. If you want to create a new directory, then please check if a similar category has been recently suggested or created by other pull requests.
-- If you have modified/added documentation, please ensure that your language is concise and contains no grammar errors.
-- Do not update [`README.md`](https://github.com/TheAlgorithms/C-Plus-Plus/blob/master/README.md) along with other changes. First create an issue and then link to that issue in your pull request to suggest specific changes required to [`README.md`](https://github.com/TheAlgorithms/C-Plus-Plus/blob/master/README.md).
-- The repository follows [Doxygen](https://www.doxygen.nl/manual/docblocks.html) standards and auto-generates the [repository website](https://thealgorithms.github.io/C-Plus-Plus). Please ensure the code is documented in this structure. Sample implementation is given below.
+- If you have modified/added documentation, please ensure that your language is concise and must not contain grammatical errors.
+- Do not update [`README.md`](https://github.com/TheAlgorithms/C-Plus-Plus/blob/master/README.md) along with other changes. First, create an issue and then link to that issue in your pull request to suggest specific changes required to [`README.md`](https://github.com/TheAlgorithms/C-Plus-Plus/blob/master/README.md).
+- The repository follows [Doxygen](https://www.doxygen.nl/manual/docblocks.html) standards and auto-generates the [repository website](https://thealgorithms.github.io/C-Plus-Plus). Please ensure the code is documented in this structure. A sample implementation is given below.
 
 #### Test
 
-- Make sure to add examples and test cases in your main() function.
-- If you find any algorithm or document without tests, please feel free to create a pull request or issue describing suggested changes.
-- Please try to add one or more `test()` functions that will invoke the algorithm implementation on random test data with expected output. Use `assert()` function to confirm that the tests will pass. Requires including the `cassert` header.
+- Make sure to add examples and test cases in your `main()` function.
+- If you find an algorithm or document without tests, please feel free to create a pull request or issue describing suggested changes.
+- Please try to add one or more `test()` functions that will invoke the algorithm implementation on random test data with the expected output. Use the `assert()` function to confirm that the tests will pass. Requires including the `cassert` header.
 
 #### Typical structure of a program
 
@@ -130,7 +130,7 @@ int main(int argc, char *argv[]) {
 
 #### New File Name guidelines
 
-- Use lowercase words with ``"_"`` as separator
+- Use lowercase words with ``"_"`` as a separator
 - For instance
 
 ```markdown
@@ -139,8 +139,8 @@ my_new_cpp_class.cpp    is correct format
 ```
 
 - It will be used to dynamically create a directory of files and implementation.
-- File name validation will run on docker to ensure the validity.
-- If an implementation of the algorithm already exists and your version is different from that implemented, please use incremental numeric digit as a suffix. For example, if `median_search.cpp` already exists in the `search` folder and you are contributing a new implementation, the filename should be `median_search2.cpp` and for a third implementation, `median_search3.cpp`.
+- File name validation will run on docker to ensure validity.
+- If an implementation of the algorithm already exists and your version is different from that implemented, please use incremental numeric digit as a suffix. For example: if `median_search.cpp` already exists in the `search` folder, and you are contributing a new implementation, the filename should be `median_search2.cpp` and for a third implementation, `median_search3.cpp`.
 
 #### New Directory guidelines
 
@@ -158,7 +158,7 @@ some_new_fancy_category         is correct
 
 #### Commit Guidelines
 
-- It is recommended to keep your changes grouped logically within individual commits. Maintainers find it easier to understand changes that are logically spilt across multiple commits.  Try to modify just one or two files in the same directory.  Pull requests that span multiple directories are often rejected.
+- It is recommended to keep your changes grouped logically within individual commits. Maintainers find it easier to understand changes that are logically spilled across multiple commits. Try to modify just one or two files in the same directory. Pull requests that span multiple directories are often rejected.
 
 ```bash
 git add file_xyz.cpp
@@ -216,14 +216,14 @@ clang-tidy --fix --quiet -p build subfolder/file_to_check.cpp --
 #### GitHub Actions
 
 - Enable GitHub Actions on your fork of the repository.
-After enabling it will execute `clang-tidy` and `clang-format` after every push (not a commit).
+After enabling, it will execute `clang-tidy` and `clang-format` after every push (not a commit).
   - Click on the tab "Actions", then click on the big green button to enable it.
 
 ![GitHub Actions](https://user-images.githubusercontent.com/51391473/94609466-6e925100-0264-11eb-9d6f-3706190eab2b.png)
 
 - The result can create another commit if the actions made any changes on your behalf.
 - Hence, it is better to wait and check the results of GitHub Actions after every push.
-- Run `git pull` in your local clone if these actions made many changes in order to avoid merge conflicts.
+- Run `git pull` in your local clone if these actions made many changes to avoid merge conflicts.
 
 Most importantly,