From 6434d15d7f9b119bd519a17f4fb2a6dd53731670 Mon Sep 17 00:00:00 2001 From: Zearin Date: Fri, 17 Jul 2026 19:22:19 +0200 Subject: [PATCH] (more) Minor nitpicky punctuation edits --- content/collaborating/repo-permissions.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/collaborating/repo-permissions.md b/content/collaborating/repo-permissions.md index e9e5f5a..39ae8db 100644 --- a/content/collaborating/repo-permissions.md +++ b/content/collaborating/repo-permissions.md @@ -141,8 +141,8 @@ you can specify for each unit (Code Access, Issues, Releases) a different permis Each unit is configured to have one of these 3 permission levels: - No Access: Members cannot view or take any other action on this unit. -- Read: Members can view the unit, and do standard actions for that unit. (See the Read column under [Collaborators](#collaborators).) -- Write: Members can view the unit, and execute write actions that unit. (See the Write column under [Collaborators](#collaborators).) +- Read: Members can view the unit and do standard actions for that unit. (See the Read column under [Collaborators](#collaborators).) +- Write: Members can view the unit and execute write actions that unit. (See the Write column under [Collaborators](#collaborators).) When a team is configured to have administrator access, when this is specified, you cannot change units. The team will have admin permissions (See the Admin column under [Collaborators](#collaborators)). @@ -154,7 +154,7 @@ Currently, there are six units that can be configured: - Pull Requests: access pull requests and code reviews. - Releases: track the project versions and downloads. - Wiki: access and write documentation. -- Projects: access and manage issues and pull requests in project boards. +- Projects: access/manage issues and pull requests in project boards. There are also two units which can be toggled: