diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 1b28d3d79..19e8a9fbe 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -8,23 +8,23 @@ assignees: ''
 ---
 
 <!--
-Oh no, a bug. It happens. Thanks for reporting an issue with NewPipe
+Oh no, a bug! It happens. Thanks for reporting an issue with NewPipe.
 
 Use this template to notify us if you found a bug.
 
 To make it easier for us to help you please enter detailed information below.
 
-Please note, we only support the latest version of NewPipe and master branch. Please make sure to upgrade & recreate the issue on the latest version prior to opening an issue. The release page (https://github.com/TeamNewPipe/NewPipe/releases/latest) is a good start, make sure its version is the same as in your app (to check your version, open the left drawer and click on "About").
+Please note, we only support the latest version of NewPipe and the master branch. Please make sure to upgrade & recreate the issue on the latest version prior to opening an issue. The release page (https://github.com/TeamNewPipe/NewPipe/releases/latest) is a good start. Make sure its version is the same as in your app (to check your version, open the left drawer and click on "About").
 
 P.S.: Our [contribution guidelines](https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md) might be a nice document to read before you fill out the report :)
 -->
 ### Version
-<!--Which version are you using?-->
+<!-- Which version are you using? -->
 - 
 
 
-### Steps to reproduce
-<!--If you cant reproduce it, please try and give as many details as possible how you think you got to the bug-->
+### Steps to reproduce the bug
+<!-- If you can't reproduce it, please try and give as many details as possible how you think you got to the bug. -->
 Steps to reproduce the behavior:
 1. Go to '...'
 2. Press on '....'
@@ -36,10 +36,10 @@ Tell us what you expected to happen.
 ### Actual behaviour
 Tell us what happens instead.
 
-### Screenshots/-recording
-If applicable, add screenshots or a screen recording to help explain your problem. Github should support uploading them directly in the issue field. If your file is too big, feel free to paste a link from a image/video hoster here instead.
+### Screenshots/Screen records
+If applicable, add screenshots or a screen recording to help explain your problem. Github should support uploading them directly in the issue field. If your file is too big, feel free to paste a link from an image/video hoster here instead.
 
 ### Logs
 If your bug includes a crash, please head over to the [incredible bugreport to markdown converter](https://teamnewpipe.github.io/CrashReportToMarkdown/). Copy the result. Paste it here:
 
-<!--That's right, here-->
+<!-- That's right, here! -->
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index a6262ad7b..b461675bd 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -8,13 +8,13 @@ assignees: ''
 ---
 <!-- Hey. Our [contribution guidelines](https://github.com/TeamNewPipe/NewPipe/blob/HEAD/.github/CONTRIBUTING.md) might be a nice
  document to read before you fill out the request :) -->
-#### Is your feature request related to a problem? Please describe.
+#### Is your feature request related to a problem? Please describe it
 A clear and concise description of what the problem is.
 Example: *I want to do X, but there is no way to do it.*
 
 #### Describe the solution you'd like
 A clear and concise description of what you want to happen.
-Example: *I think it would be nice if you would add feature Y so it will make it easier.*
+Example: *I think it would be nice if you add feature Y which makes X possible.*
 
 #### Describe alternatives you've considered
 A clear and concise description of any alternative solutions or features you've considered.
@@ -24,7 +24,7 @@ Example: *I considered Z, but that didn't turn out to be a good idea because...*
 Add any other context or screenshots about the feature request here.
 Example: *Here's a photo of my cat!*
 
-#### Why do you/everyone wants this feature
+#### How will you/everyone benefit from this feature?
 Convince us! How does it change your NewPipe experience and/or your life?
-The better this paragraph is, the more likely a developer will think about developing it.
+The better this paragraph is, the more likely a developer will think about working on it.
 
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 978adc100..40dd5d616 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,14 +1,17 @@
-<!-- Hey there. Thank you so much for improving NewPipe. Please take a moment to fill out the following suggestion on how to structure this PR description. Having roughly the same layout drastically helps everybody :)-->
+<!-- Hey there. Thank you so much for improving NewPipe. Please take a moment to fill out the following suggestion on how to structure this PR description. Having roughly the same layout helps everyone considerably :)-->
 
 #### What is it?
 - [ ] Bug fix
 - [ ] Feature
 
 #### Long description of the changes in your PR
-*Now you can make videos*
+<!-- While bullet points are the norm in this section, feel free to write a text instead if you can't fit it in a list -->
+- record videos
+- create clones
+- take over the world
 
 #### Fixes the following issue(s)
-<!--Also add reddit or other links where you change is related-->
+<!-- Also add reddit or other links which are relevant to your change. -->
 - 
 
 #### Relies on the following changes
@@ -16,7 +19,7 @@
 - 
 
 #### Testing apk
-<!--Ensure to have your changes on a new branch which has a meaningful name. This name will be used as suffix of the app id to allow installing and testing multiple versions of NewPipe. Do NOT name your branches like "patch-0" and "feature-1".-->
+<!-- Ensure that you have your changes on a new branch which has a meaningful name. This name will be used as a suffix for the app ID to allow installing and testing multiple versions of NewPipe. Do NOT name your branches like "patch-0" and "feature-1". For example, if your PR implements a bug fix for comments, an appropriate branch name would be "commentfix" -->
 debug.zip
 
 #### Agreement