fix: Update org members can edit project ownership rules (#11400)

Add that org members can edit project ownership rules

Co-authored-by: Liza Mock <[email protected]>

Author: jangjodi

docs/organization/membership/index.mdx

@@ -36,8 +36,8 @@ Organization-level roles enable broad access to the entire organization, as desc
 | Can join and leave existing teams                                               |             | ✓          | ✓         | ✓           | ✓         |
 | Can add repositories (through GitHub integrations)                              |             | ✓          | ✓         | ✓           | ✓         |
 | Can create and remove teams from the organization                               |             |            | ✓         | ✓           | ✓         |
-| Can change project settings                                                     |             |            | ✓         | ✓           | ✓         |
-| Can create and remove projects for the organization                             |             | ✓\*        | ✓         | ✓           | ✓         |
+| Can change project settings                                                     |             | ✓\*        | ✓         | ✓           | ✓         |
+| Can create and remove projects for the organization                             |             | ✓\*\*      | ✓         | ✓           | ✓         |
 | Can edit Global Integrations                                                    |             |            | ✓         | ✓           | ✓         |
 | Can remove repositories                                                         |             |            | ✓         | ✓           | ✓         |
 | Can add, remove, and change Org Members                                         |             |            |           | ✓           | ✓         |
@@ -49,7 +49,9 @@ Organization-level roles enable broad access to the entire organization, as desc
 | Can transfer projects to another organization                                   |             |            |           |             | ✓         |
 | Can remove an organization                                                      |             |            |           |             | ✓         |
 
-\*For Business and Enterprise plans, even Org Members who are not a Team Admin for any team can create a new personal project. When creating this project, the member will get assigned a new personal team that they will become a Team Admin for. [Team Admin permissions](#permissions-1) will then apply for this team.
+\*Org Members will only be able to edit [ownership rules](https://sentry.io/orgredirect/organizations/:orgslug/settings/projects/action-release/ownership/) for the project.
+
+\*\*If your organization is on a Business or Enterprise plan, anyone who's part of the org will be able to create a project without having to be a Team Admin. When org members create a project, they'll become the Team Admin for that project by default and have all the permissions of the [Team Admin](#permissions-1) for that project.
 
 ## Team-level Roles
 
@@ -113,9 +115,9 @@ Let's say a user is a Team Admin for Team 1 and a Contributor for Team 2, and bo
 
 Projects can only be accessed by that project's team(s). Team Admins, Org Managers, and Org Owners can add or remove project teams in **Project Settings > Project Teams**. Alternatively, these roles can also add projects to a team in **Team Settings > Projects**.
 
-All Org Members can get access to a project by joining a team associated with that project.
+Any Org Member can get access to a project by joining the team that's associated with that project. Once you've joined a project you'll also be able to edit [ownership rules](/product/issues/ownership-rules/) for that project.
 
-### Adding New Members 
+### Adding New Members
 <Note>
 This feature is currently only available for [Early Adopters](/organization/early-adopter-features/).
 </Note>