diff --git a/.github/ISSUE_TEMPLATE/tracker.md b/.github/ISSUE_TEMPLATE/tracker.md
index acabf5519..0c6f6fc78 100644
--- a/.github/ISSUE_TEMPLATE/tracker.md
+++ b/.github/ISSUE_TEMPLATE/tracker.md
@@ -8,7 +8,8 @@ labels: tracker id
 File:
 Reviewers:
 
-## Context
+> The sections below may still be pending. If so, the issue is still available, it simply doesn't
+> have specific guidance yet. Please refer to [this overview of updates](https://github.com/pymc-devs/pymc-examples/wiki/Notebook-updates-overview)
 
 ## Known changes needed
 Changes listed in this section should all be done at some point in order to get this
@@ -35,4 +36,4 @@ the notebook but may not have a clear implementation, or fix some know issue onl
 
 ### Exotic dependencies
 
-### Computing power
+### Computing requirements
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8905ff61f..cf536cf69 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -36,6 +36,14 @@ Before starting a work on a pull request look at the tracker issue of the
 notebook you are planning to edit to make sure it is not being updated by someone
 else.
 
+**Note on labels**: The labels on an issue will apply to the most immediate 1 position update.
+One issue can be labeled "good first issue" for updating from "To Do" to "General updates", but
+that does not mean that updating from "To Do"->"ArviZ" or
+"General Updates"->"Best Practices" won't be challenging.
+The same could be true the other way around.
+In case of doubt, don't hesitate to ask and read over the notebook to
+see what changes are expected.
+
 If there are no comments and nobody is working on this notebook,
 comment on the ticket to make it evident to others, we will assign
 the issue to you as soon as possible.