diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 32579078..8a4ea6b2 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,58 +1,37 @@
 ## Description
 
 <!--
-
 A clear and concise description of what you changed and why.
-
-Bullet points can be enough.
-
-You can use the following PRs as inspiration:
-  - https://github.com/stackernews/stacker.news/pull/227 (feature)
-  - https://github.com/stackernews/stacker.news/pull/915 (feature)
-  - https://github.com/stackernews/stacker.news/pull/871 (fix)
-  - <your PR could be here>
-
 Don't forget to mention which tickets this closes (if any).
-Use following syntax to close them automatically on merge: closes #<NUMBER>
-
+Use following syntax to close them automatically on merge: closes #<number>
 -->
 
 ## Screenshots
 
 <!--
-
 If your changes are user facing, please add screenshots of the new UI.
-
 You can also create a video to showcase your changes (useful to show UX).
-
 -->
 
 ## Additional Context
 
 <!--
-
 You can mention here anything that you think is relevant for this PR. Some examples:
-
 * You encountered something that you didn't understand while working on this PR
 * You were not sure about something you did but did not find a better way
 * You initially had a different approach but went with a different approach for some reason
-
 -->
 
 ## Checklist
 
-<!-- Examples for backwards incompatible changes:
-- dropping database columns
-- changing GraphQL type definitions to make a field mandatory -->
 - [ ] Are your changes backwards compatible?
 
-<!-- If your PR is not ready for review yet, please mark your PR as a draft.
-If changes were requested, request a new review when you incorporated the feedback. -->
+<!--
+If your PR is not ready for review yet, please mark your PR as a draft.
+If changes were requested, request a new review when you incorporated the feedback.
+-->
 - [ ] Did you QA this? Could we deploy this straight to production?
 
-<!-- You should be able to use the mobile browser emulator in your browser to test this. -->
 - [ ] For frontend changes: Tested on mobile?
 
-<!-- New env vars need to be called out
-so they can be properly configured for prod. -->
 - [ ] Did you introduce any new environment variables? If so, call them out explicitly in the PR description.