Update pull_request_template.md

.github/pull_request_template.md

@@ -2,33 +2,33 @@ Closes #
 
 Implemented solution: ... 
 
-How to test: ...
+How to test this PR: ...
 
 ### Sanity checks:
 - [ ] The pull request is explicitly linked to the relevant issue(s)
 - [ ] The issue is well described: clearly states the problem and the general proposed solution(s)
-- [ ] From the issue and the current pr it is explicitly stated how to test the current change
+- [ ] From the issue and the current PR it is explicitly stated how to test the current change
 - [ ] The labels in the issue set the scope and the type of issue (bug, feature, etc.)
-- [ ] All the automatic test checks are passing
+- [ ] All the automated test checks are passing
 - [ ] All the linked issues are included in one milestone
 - [ ] All the linked issues are in the Review/QA column of the [board](https://app.zenhub.com/workspaces/cloud-harness-5fdb203b7e195b0015a273d7/board)
 - [ ] All the linked issues are assigned
 
 ### Breaking changes (select one):
 - [ ] The present changes do not change the preexisting api in any way
-- [ ] This pr and the issue are tagged as a `breaking-change`
+- [ ] This PR and the issue are tagged as a `breaking-change`
 
 ### Possible deployment updates issues (select one):
 - [ ] There is no reason why deployments based on CloudHarness may break after the current update
-- [ ] This pr and the issue are tagged as `alert:deployment`
+- [ ] This PR and the issue are tagged as `alert:deployment`
 
 ### Test coverage (select one):
 - [ ] Tests for the relevant cases are included in this pr
 - [ ] The changes included in this pr are out of the current test coverage scope
 
 ### Documentation (select one):
 - [ ] The documentation has been updated to match the current changes
-- [ ] The changes included in this pr are out of the current documentation scope
+- [ ] The changes included in this PR are out of the current documentation scope
 
 ### Nice to have (if relevant):
 - [ ] Screenshots of the changes