diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 26edbd95f..60b6d1592 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,16 +1,16 @@
-## Description
-<!-- Thank you so much for your PR!
+# {Insert Description}
+<!-- Thank you so much for your PR to pymc-examples!
 
-To help us review your contribution, please provide the info requested below. Otherwise,
-we may leave reviews that are actually out of the scope of the current PR. -->
+To make the merge process smoother we've provided some links and a checklist below.
 
-Addresses issue #xxx and aims to advance it to <!-- Tracker column: General Updates, ArviZ, Best Practices -->
-
-<!-- We understand that PRs can sometimes be overwhelming, especially as the reviews start coming in.
+We understand that PRs can sometimes be overwhelming, especially as the reviews start coming in.
 Please let us know if the reviews are unclear or the recommended next step seems overly demanding,
 if you would like help in addressing a reviewer's comments,
-or if you have been waiting too long to hear back on your PR.
+or if you have been waiting too long to hear back on your PR. -->
+
++ [ ] Notebook follows style guide https://github.com/pymc-devs/pymc/wiki/PyMC-Jupyter-Notebook-Style-Guide
++ [ ] PR description contains a link to the relevant issue: a tracker one for existing notebooks or a proposal one for new notebooks
+
 
-Also, please consider reading the contributing guidelines and code of conduct carefully before submitting the PR. They are available at
-- https://github.com/arviz-devs/arviz/blob/main/CONTRIBUTING.md
-- https://github.com/arviz-devs/arviz/blob/main/CODE_OF_CONDUCT.md -->
+### Helpful links
+* https://github.com/pymc-devs/pymc-examples/blob/main/CONTRIBUTING.md