From 210df59880df670b70a2b6d3ac10fbcf9fd07676 Mon Sep 17 00:00:00 2001
From: Zearin <zearin@noreply.codeberg.org>
Date: Fri, 17 Jul 2026 19:19:30 +0200
Subject: [PATCH] Minor nitpicky punctuation edits

---
 content/collaborating/repo-permissions.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/content/collaborating/repo-permissions.md b/content/collaborating/repo-permissions.md
index 8fbf745..e9e5f5a 100644
--- a/content/collaborating/repo-permissions.md
+++ b/content/collaborating/repo-permissions.md
@@ -37,7 +37,7 @@ it will seem as if it does not exist at all!
 
 ## Collaborators
 
-There are four permission levels: **Read**, **Write**, **Administrator** and **Owner**.
+There are four permission levels: **Read**, **Write**, **Administrator**, and **Owner**.
 
 By default, the person who creates a repository is an **_Owner_**.
 
@@ -55,7 +55,7 @@ The table below gives an overview of what collaborators are allowed to do when g
  </thead>
  <tbody>
   <tr>
-   <td>View, clone and pull repository</td>
+   <td>View, clone, and pull repository</td>
    <td><span style="color: green">{% fas_icon "check" %}</span></td>
    <td><span style="color: green">{% fas_icon "check" %}</span></td>
    <td><span style="color: green">{% fas_icon "check" %}</span></td>
@@ -83,7 +83,7 @@ The table below gives an overview of what collaborators are allowed to do when g
    <td><span style="color: green">{% fas_icon "check" %}</span></td>
   </tr>
   <tr>
-   <td>Merge pull requests </td>
+   <td>Merge pull requests</td>
    <td><span style="color: red">{% fas_icon "times" %}</span></td>
    <td><span style="color: green">{% fas_icon "check" %}</span></td>
    <td><span style="color: green">{% fas_icon "check" %}</span></td>
@@ -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)).
@@ -151,7 +151,7 @@ Currently, there are six units that can be configured:
 
 - Code: access source code, files, commits, and branches.
 - Issues: organize bug reports, tasks, and milestones.
-- Pull Requests: access pull requests, and code reviews.
+- 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.