clarifies difference between triage and write levels

Signed-off-by: Nell Shamrell <nellshamrell@gmail.com>

Author: nellshamrell

text/0000-github-access-policy.md

@@ -37,10 +37,11 @@ GitHub provides several permission levels for access to a repository. Please ref
 Repositories in the Rust-Lang organization should follow these permission guidelines:
 
 * **Admin** - only Rust team or working group leads should have this permission level
-* **Write** - contributors within GitHub teams may have this permission level at the discretion of the team leads
-* **Triage** - contributors within GitHub teams involved in issue and pull request management (i.e. closing, re-opening, and assigning issues and pull requests) should be granted this access
+* **Write** - contributors within GitHub teams may have this permission level at the discretion of the team leads. Members of the triage team should also ge given this level of access so they have the ability edit issue descriptions.
 * **Read** - by default, everyone should have access to read repositories
 
+GitHub does provide another permission level - Triage - which is geared toward contributors involved in issue and pull request management. This permission level unfortunately does not allow contributors to edit issue descriptions, which is something Rust's triage teams do frequently. Therefore, contributors in triage roles should be assigned "Write" permissions, rather than "Triage" permissions.
+
 By default, repositories should be public and allow read access to all. When needed, some repositories can have limited read access (i.e. repositories related to security). 
 
 Bot accounts controlled by the Infrastructure Team (such as the [Rust High Five Bot](https://github.com/rust-highfive)) can be granted any level of access required for them to work at the discretion of the Infrastructure Team.