diff --git a/docs/Governance.md b/docs/Governance.md
index cb5e3f7ea7..c977a1bbad 100644
--- a/docs/Governance.md
+++ b/docs/Governance.md
@@ -131,12 +131,11 @@ In the weekly triage meetings, new issues should be added to a milestone followi
 
 To help prioritize issues, the triage drivers and maintainers MUST use *special labels* to prioritize issues as follows:
 ### P1:
-This label represents highest priority. This label should be used for bugs impacting users, new features, or enhancements that are urgently
-requested by users. `P1` issues MUST be set to the *current milestone*.
+This label represents highest priority. This label should ONLY be applied to bugs or features with quantifiable business impact. Quantifiable business impact may include number of users, business blocked, or deployment blocked. Bugs with only qualitative impact (descriptions without numbers) will be ranked lower than quantifiable P1 bugs. `P1` issues MUST be set to the *current milestone*.
 ### P2:
-This label is used for the next level of priority. Issues marked as `P2` can be set to the current milestone or to a future milestones (preferred).
+This label is used for the next level of priority. Issues marked as `P2` will be set future milestones (preferred).
 ### P3:
-This label is used for low priority issues. Issues marked as `P3` can be set to any future milestone or the `Backlog` milestone.
+This label is used for low priority issues. Issues marked as `P3` can be set to future milestones beyond 3 month or the `Backlog` milestone.
 
 ## Milestone Issues Limit
 Triage managers need to ensure that the number of issues in a milestone does not exceed the capacity of the contributors