Update PULL_REQUEST_TEMPLATE.md

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,9 +1,9 @@
 # Description
 
-A short summary of what is included in your Pull Request.
+<!-- Give summary of what is included in your Pull Request. -->
 
 Fixes #(issue_no)
-<!-- If you PR as fixing an issue within the issue section, eplace `issue_no` in the above line, with the issue related to this PR.
+<!-- If you PR as fixing an issue within the issue section, replace `issue_no` in the above line with the issue related to this PR.
 
 If not, tick in the not applicable box and move on-->
 
@@ -13,20 +13,20 @@ If not, tick in the not applicable box and move on-->
 
 ## Type of change
 
-Choosing one or more options from the following as per the nature of your Pull request.
+Choose one or more options from the following as per the nature of your Pull request.
 
 - [ ] Bug fix (non-breaking change which fixes an issue)
 - [ ] New feature (non-breaking change which adds functionality)
 - [ ] Documentation Update
 
 # Checklist:
-Please tick all the boxes that are fulfilled by your Pull Request.
+Please tick all the boxes that your Pull Request fulfils.
 
 - [ ] My code beats 50% + of the users, will 💙 to hear this.
-- [ ] I have named my files and folder, according to this project's guidelines.
-- [ ] My code follows the style guidelines of this project and uptodate with the current trends.
+- [ ] I have named my files and folder according to this project's guidelines.
+- [ ] My code follows the style guidelines of this project and is up to date with the current trends.
 - [ ] I have commented on my code, particularly in hard-to-understand areas and included the time complexity O(n).
-- [ ] I have created a helpful and easy to understand `README.md` especialy when you created a new directory.
+- [ ] I have created a helpful and easy to understand `README.md` especially when you created a new directory.
 - [ ] My changes do not produce any warnings.
 
 <!-- provide more info if needed -->