inverted pyramid

Author: akristen

content/manuals/admin/_index.md

@@ -42,47 +42,42 @@ Administrators start with the [Docker Admin Console](https://app.docker.com/admi
 Administrators get started with Docker by accessing the Admin Console to create a company and organizations. 
 
 - If you're a Docker Business subscriber, you have access to both company and organization features.
-- If you're Docker Team subscriber, you have access to organization features in Admin Console.
-
-As an administrator, you're an owner who can invite users with their email addresses, then assign them member roles to particular teams.
+- If you're Docker Team subscriber, you have access to organization features.
 
 ## Company and organization hierarchy
 
-Admin Console gives administrators a bird's eye overview of a company  and its downstream organizations. Company and organizations have a hierarchical relationship:
+Admin Console gives administrators a bird's eye view of who has access to Docker. There are two levels of visibility, company and organizations, and they have a hierarchical relationship:
 
 ![Diagram showing Docker’s administration hierarchy with Company at the top, followed by Organizations, Teams, and Members](./images/docker-admin-structure.webp)
 
-Administrators can occupy company owner or organization owner roles (or both), where each role has its own permissions and seat rules. 
-
-- Company owners can view and bulk edit settings and configurations for all organizations beneath them.
-- Organization owners have full admin permissions to manage settings, members, roles, and teams within their organization, but not organizations they're not part of.
-
-When an administrator creates the first company from Admin Console, they assume owner roles pursuant to their subscription type. For example:
+### Company
 
-- A Docker Business subscriber assumes owner permissions for both the first company and first organization.
-- A Docker Team subscriber assumes owner permissions for the first created organization. 
+The highest level of visibility an administrator can have is at the company level. A company owner views and manages all organizations within the company and has full access to company-wide settings.
 
-### Company
+### Organization
 
-The highest level of visibility an administrator can have is at the company level. A company owner views and manages all organizations within the company and has full access to company-wide settings. 
+An organization contains teams and repositories. Organization owners manage organization settings, users, and access controls. 
 
-Company owners won't occupy a seat unless one of the following is true:
+- All Docker Team and Business
+subscribers must create one organization before inviting new members to Docker.
+- All organizations owners occupy one seat, but can occupy more than one seat if they're members or owners of multiple, separate organizations.
+- Unlike a company, an organization is discrete from other organizations and cannot inherit permissions in bulk from other organizations. 
 
-- They are added as a member of an organization under your company.
-- SSO is enabled.
+If you're a Docker team subscriber who wants access to company-level permissions, you can [upgrade to Docker Business](/subscription/change/#upgrade-your-subscription).
 
-If you're a Docker team subscribe who wants access to company-level permissions, you can [upgrade to Docker Business](/subscription/change/#upgrade-your-subscription).
+## Seats and user management
 
-### Organization
+The number of seats an administrator can provision depends on their [subscription type](https://www.docker.com/pricing/). Administrators can act as company or organization owners who can invite users with their email addresses, then assign them member roles to particular teams.
 
-An organization contains teams and repositories. All Docker Team and Business
-subscribers must create one organization before inviting new members to Docker.
+### Company and organization owners 
 
-Organization owners manage organization settings, users, and access controls. All organizations owners occupy at least one seat, but can occupy more than one seat if they're members or owners of multiple, separate organizations. 
+Administrators can occupy company owner or organization owner roles (or both), where each role has its own permissions and seat rules. 
 
-## Seats and user management
+- Company owners can view and bulk edit settings and configurations for all organizations beneath them.
+- Company owners won't occupy a seat unless SSO is enabled, or they're a member of an organization within the company. 
+- Organization owners have full admin permissions to manage settings, members, roles, and teams within their organization, but not organizations they're not part of.
 
-The number of seats an administrator can provision depends on their [subscription type](https://www.docker.com/pricing/). Once you've decided on a plan and created your first company or organization, you can send invitations to future members. 
+When an administrator creates the first company or organization from Admin Console, they assume owner roles for the company and/or the organization by default.
 
 ### Seats 
 
@@ -91,18 +86,18 @@ A seat is a unit purchased with a subscription plan that extends access to users
   - They give administrators granular permissions around who can contribute to a repository.
   - They prevent unauthorized users from pushing to a repos they're not members of. 
 
-For example, an organization owner takes up one seat. They can invite Docker users to an organization. Once invitees become members, organization owners can set permissions in bulk or on an individual basis to repositories affiliated with an organization.  
+For example, an organization owner takes up one seat. They can invite Docker users to an organization. Once invitees become members, organization owners can set permissions to members of their company or organization. 
 
 ### Users and members 
 
-Docker uses specific terminology to define the kind of access a Docker user has: 
+Docker uses specific terminology to define user access: 
 
 - A user is someone with a Docker ID.
-  - They are not necessarily affiliated with an organization.
-  - They do not take up seats by default.
+  - They're not necessarily affiliated with an organization.
+  - They do not occupy a seat by default.
 - An invitee is a user invited to an organization.
   - Invitees occupy one seat. 
-  - This is a user state before accepting and joining an organization. 
+  - It behaves as a user state before accepting and joining an organization. 
 - A member is a user who accepted an invitation to an organization.
 - Teams let you group members together.
   - They are optional.