Updated PR template after visually checking

Author: michalChrobot

.github/pull_request_template.md

@@ -1,6 +1,7 @@
 ## Purpose of this PR
-[//]: # (Describe the purpose of the PR)
-<!-- Replace this block with what this PR does and why. Describe what you'd like reviewers to know, how you applied the engineering principles, and any interesting tradeoffs made. Delete bullet points below that don't apply, and update the changelog section as appropriate. -->
+[//]: # (
+Replace this block with what this PR does and why. Describe what you'd like reviewers to know, how you applied the engineering principles, and any interesting tradeoffs made. 
+)
 
 ### Jira ticket
 _Link to related jira ticket ([Use the smart commits](https://support.atlassian.com/bitbucket-cloud/docs/use-smart-commits/))_
@@ -9,10 +10,10 @@ _Link to related jira ticket ([Use the smart commits](https://support.atlassian.
 [//]: # (updated with all public facing changes  - API changes, UI/UX changes, behaviour changes, bug fixes. Remove if not relevant.)
 
 - Added: The package whose Changelog should be added to should be in the header. Delete the changelog section entirely if it's not needed.
-- Fixed: If you update multiple packages, create a new section with a new header for the other package. 
+- Fixed: If you update multiple packages, create a new section with a new header for the other package.
 - Removed/Deprecated/Changed: Each bullet should be prefixed with Added, Fixed, Removed, Deprecated, or Changed to indicate where the entry should go.
 - Documentation: Contains significant docs changes
-- 
+
 <!--  Uncomment and mark items off with a * if this PR deprecates any API:
 ### Deprecated API
 - [ ] An `[Obsolete]` attribute was added along with a `(RemovedAfter yyyy-mm-dd)` entry.
@@ -22,21 +23,21 @@ _Link to related jira ticket ([Use the smart commits](https://support.atlassian.
 -->
 
 ### Documentation
-<!--  
-    This section is REQUIRED and should mention what documentation changes were following the changes in this PR.
-    We should always evaluate if the changes in this PR require any documentation changes.
--->
+[//]: # (
+This section is REQUIRED and should mention what documentation changes were following the changes in this PR. 
+We should always evaluate if the changes in this PR require any documentation changes.
+)
 
 - No documentation changes or additions were necessary.
 - Includes documentation for previously-undocumented public API entry points.
 - Includes edits to existing public API documentation.
 
 ## Testing & QA
-<!--  
-    This section is REQUIRED and should describe how the changes were tested and how should they be tested when Playtesting for the release.
-    It can range from "edge case covered by unit tests" to "manual testing required and new sample was added".
-    Expectation is that PR creator does some manual testing and provides a summary of it here.
--->
+[//]: #  (
+This section is REQUIRED and should describe how the changes were tested and how should they be tested when Playtesting for the release.
+It can range from "edge case covered by unit tests" to "manual testing required and new sample was added".
+Expectation is that PR creator does some manual testing and provides a summary of it here.)
+
 ### Functional Testing
 [//]: # (If checked, List manual tests that have been performed.)
 _Manual testing :_
@@ -54,15 +55,8 @@ _Does the change require QA team to:_
 If any boxes above are checked, please add QA as a PR reviewer.
 
 ## Backport
-<!--  
-    This section is REQUIRED and should preferably link to the PR that targets other NGO version (develop, develop-2.0.0 branches)
-    If this is not needed (for example feature specific to NGOv2.X) then just mention this fact.
--->
-
-<!-- If this is a backport:
- - Add the following to the PR title: "\[Backport\] ..." .
- - Link to the original PR.
-If this needs a backport - state this here
-If a backport is not needed please provide the reason why.
-If the "Backports" section is not present it will lead to a CI test failure. 
--->
+[//]: # (
+This section is REQUIRED and should link to the PR that targets other NGO version which is either develop or develop-2.0.0 branch
+Add the following to the PR title: "\[Backport\] ..."
+If this is not needed, for example feature specific to NGOv2.X, then just mention this fact.
+)