PR Feedback.

docs/Governance.md

@@ -117,14 +117,14 @@ Responsibilities:
 
 ## Prioritizing Issues
 
-In the weekly triage meetings, new issues are assigned to contributors and are set to a monthly milestone by which the issue is expected to be completed. It may not be possible for the assignees to address all the issues assigned to them by their target milestone. As a result issues may pile up in a given milestone. In such cases project admins can request contributors to use *special labels* to prioritize issues as follows:
+In the weekly triage meetings, new issues are assigned to collaborators and are set to a monthly milestone by which the issue is expected to be completed. It may not be possible for the assignees to address all the issues assigned to them by their target milestone. As a result issues may pile up in a given milestone. In such cases project admins can request that triage drivers and maintainers use *special labels* to prioritize issues as follows:
 ### P1:
-This label represents highest priority. This label should be used for bugs impacting users, new feature or enhancements that are urgently requested by users. Contributors should try to resolve these issues in the **current milestone**.
+This label represents highest priority. This label should be used for bugs impacting users, new feature or enhancements that are urgently requested by users. Collaborators  should try to resolve these issues in the **current milestone**.
 ### P2:
 This label is used for the next level of priority. Issues marked as P2 for the current milestone may be moved to the *next milestone* after discussing in the weekly triage meeting.
 ### P3:
 This label is used for low priority issues. Issues marked with this label may be moved to the *backlog* milestone.
-Note that contributors and admins can change the priority of issues as deemed necessary.
+Note that triage drivers, maintainers, and project admins can change the priority of issues as deemed necessary.
 
 ## Reviewing Pull Requests