11# Description
22
3- A short summary of what is included in your Pull Request.
3+ <!-- Give summary of what is included in your Pull Request. -->
44
55Fixes #(issue_no)
6- <!-- 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.
6+ <!-- 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.
77
88If not, tick in the not applicable box and move on-->
99
@@ -13,20 +13,20 @@ If not, tick in the not applicable box and move on-->
1313
1414## Type of change
1515
16- Choosing one or more options from the following as per the nature of your Pull request.
16+ Choose one or more options from the following as per the nature of your Pull request.
1717
1818- [ ] Bug fix (non-breaking change which fixes an issue)
1919- [ ] New feature (non-breaking change which adds functionality)
2020- [ ] Documentation Update
2121
2222# Checklist:
23- Please tick all the boxes that are fulfilled by your Pull Request.
23+ Please tick all the boxes that your Pull Request fulfils .
2424
2525- [ ] My code beats 50% + of the users, will 💙 to hear this.
26- - [ ] I have named my files and folder, according to this project's guidelines.
27- - [ ] My code follows the style guidelines of this project and uptodate with the current trends.
26+ - [ ] I have named my files and folder according to this project's guidelines.
27+ - [ ] My code follows the style guidelines of this project and is up to date with the current trends.
2828- [ ] I have commented on my code, particularly in hard-to-understand areas and included the time complexity O(n).
29- - [ ] I have created a helpful and easy to understand ` README.md ` especialy when you created a new directory.
29+ - [ ] I have created a helpful and easy to understand ` README.md ` especially when you created a new directory.
3030- [ ] My changes do not produce any warnings.
3131
3232<!-- provide more info if needed -->
0 commit comments