diff --git a/en/05_Contributing/00_Issues_and_Bugs.md b/en/05_Contributing/00_Issues_and_Bugs.md
index b4e2ef2c6..a49a2dcc5 100644
--- a/en/05_Contributing/00_Issues_and_Bugs.md
+++ b/en/05_Contributing/00_Issues_and_Bugs.md
@@ -91,7 +91,7 @@ The current GitHub labels are grouped into five sections:
 1. *Impact* - What impact does this issue have, does it break a feature completely, is it just a side effect or is it trivial and not a big problem (but a bit annoying), etc. Impact is evaluated in the context of the CMS as a whole, rather than against the individual module the issue is raised on.
 1. *Complexity* - What level of technical proficiency is required to address this issue?
 1. *Type* - The type of solution required to address this issue
-1. *Affects* - The release line this issue is relevant to
+1. *Affects* - The major release line this issue is relevant to - for instance `silverstripe/admin 2.0.0` is on the CMS 5 major release line, so use `affects/v5`. Do not add this label for unreleased major release lines, instead use `type/api-break`.
 1. *RFC* - The issue is a request-for-comment
 
 | Label | Purpose |
@@ -109,6 +109,7 @@ The current GitHub labels are grouped into five sections:
 | type/ux | Impact on the CMS user interface |
 | type/docs | A docs change |
 | type/userhelp | A userhelp documentation change |
+| type/other | Any issue that does not is not covered by another type label e.g. general maintainence |
 | affects/* | Issue has been observed on a specific CMS release line |
 | rfc/draft | [RFC](/project_governance/request_for_comment) under discussion |
 | rfc/accepted | [RFC](/project_governance/request_for_comment) where agreement has been reached |