fix: improving style guide

content/contributing/style-guide-and-content-model/style-guide.md

@@ -1479,8 +1479,8 @@ A **permission** is the ability to perform a specific action. For example, the a
 A **role** is a set of permissions that can be assigned to a user. Roles exist at different levels.
 
 - Accounts (e.g., organization owner, billing manager for an enterprise account)
-- Resources (e.g., "Write" for a repository, "Admin" for a security advisory)
-- Teams (e.g., "team maintainer")
+- Resources (e.g., write for a repository, admin for a security advisory)
+- Teams (e.g., team maintainer)
 
 A person's **access** refers generally to all the abilities the person has in a particular context, regardless of which roles or individual permissions those abilities come from.
 
@@ -1490,6 +1490,7 @@ Only use **permission** or **role** when the distinction between the two is impo
 - **Use:** Managing a team's access to your organization's repository
 - **Use:** If your team membership gives you a different level of access than your role as organization owner…
 - **Use:** People with write access can…
+- **Avoid:** People with the write access can...
 - **Avoid:** People with the write role can…
 - **Avoid:** People with write permissions can…
 - **Avoid:** People with write privileges can…