Add space for docs PR in PR template

Signed-off-by: Pedro Pombeiro <pombeirp@users.noreply.github.com>

.github/ISSUE_TEMPLATE/BUG_REPORT_TEMPLATE.md

@@ -18,12 +18,15 @@ As a <user|developer|...>, I want to <task> so that <goal>.
 *Summary*: ...
 
 #### Expected behavior
+
 [comment]: # (Describe what you expected to happen.)
 
 #### Actual behavior
+
 [comment]: # (Describe what actually happened.)
 
 ### Reproduction
+
 [comment]: # (Describe how we can replicate the bug step by step.)
 
 - Open Status
@@ -31,6 +34,7 @@ As a <user|developer|...>, I want to <task> so that <goal>.
 - Step 3, etc.
 
 ### Solution
+
 [comment]: # (Please summarise the solution and provide a task list on what needs to be fixed.)
 *Summary*:
 
@@ -38,14 +42,16 @@ As a <user|developer|...>, I want to <task> so that <goal>.
 - [ ] ...
 
 ### Additional Information
+
 [comment]: # (Please do your best to fill this out.)
-* Status version: ...
+- Status version: ...
 [comment]: # (Android or iOS.)
-* Operating System: <Android|iOS>
+- Operating System: <Android|iOS>
 
 #### Logs
 
 [comment]: # (if on Android please replicate bug whilst running adb logcat)
+
 ```
 ...
 ```

.github/ISSUE_TEMPLATE/SIMPLE_ISSUE.md

@@ -8,19 +8,19 @@ about: Simple issue report.
 An overview of the background required to understand the problem.
 A problem description.
 
-# Implementation
+## Implementation
 
 Known steps towards feature implementation.
 What needs further specifying and investigating.
 
-# Acceptance Criteria
+## Acceptance Criteria
 
 Rules for the future PR to be accepted.
 
-# Notes
+## Notes
 
 Random notes to keep in mind while implementing it. Mostly about related issues and future plans and thoughts.
 
-# Future Steps
+## Future Steps
 
 Steps which should be taken after this issue has been resolved.

.github/PULL_REQUEST_TEMPLATE.md

@@ -7,26 +7,34 @@ If you submit PR for issue with bounty then write here Fixes #NN where NN is iss
 
 fixes #...
 
-### Summary:
+### Summary
 
 [comment]: # (Summarise the problem and how the pull request solves it)
 ...
 
-### Review notes (optional):
+<!-- (Optional, remove if no changes to documentation) -->
-<!-- (Specify if something in particular should be looked at, or ignored, during review) -->
+Documentation change PR (review please): https://github.com/status-im/status.im/pull/xxx
+
+### Review notes
+<!-- (Optional. Specify if something in particular should be looked at, or ignored, during review) -->
+
+### Testing notes
+<!-- (Optional) -->
+
+#### Platforms
+<!-- (Optional. Specify which platforms should be tested) -->
 
-### Testing notes (optional):
-<!-- (Specify which platforms should be tested) -->
-#### Platforms (optional)
 - Android
 - iOS
 - macOS
 - Linux
 - Windows
 
-<!-- (Specify if some specific areas has to be tested, for example 1-1 chats) -->
+#### Areas that maybe impacted
-#### Areas that maybe impacted (optional)
+<!-- (Optional. Specify if some specific areas has to be tested, for example 1-1 chats) -->
-**Functional**
+
+##### Functional
+
 - 1-1 chats
 - public chats
 - group chats
@@ -40,13 +48,15 @@ fixes #...
 - fleet
 - bootnodes
 
-**Non-functional**
+##### Non-functional
+
 - battery performance
 - CPU performance / speed of the app
 - network consumption
 
+### Steps to test
 <!-- (Specify exact steps to test if there are such) -->
-### Steps to test:
+
 - Open Status
 - ...
 - Step 3, etc.