Corrected documentation formatting for the ease of read/fixing

Author: michalChrobot

.github/pull_request_template.md

@@ -22,7 +22,7 @@ _Link to related jira ticket ([Use the smart commits](https://support.atlassian.
 - [ ] The users can understand why this API was removed and what they should use instead.
 -->
 
-### Documentation
+## 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.

.github/workflows/pr-verification.yml

@@ -40,8 +40,8 @@ jobs:
                 description: 'PR description must include a "## Testing & QA" section. Please add this section and provide information about the testing performed for this PR. It can range from adding unit tests to full samples and is needed from QA side to analyze PRs while Playtesting for the release.'
               },
               {
-                header: '### Documentation',
-                description: 'PR description must include a "### Documentation" section. Please add this section and provide information about the documentation changes made in this PR. It is important to keep the documentation up to date with the code changes.'
+                header: '## Documentation',
+                description: 'PR description must include a "## Documentation" section. Please add this section and provide information about the documentation changes made in this PR. It is important to keep the documentation up to date with the code changes.'
               }
             ];