fix(v1 users): various wording improvements

src/content/docs/accounts/accounts/saml-single-sign/saml-service-providers.mdx

@@ -43,9 +43,9 @@ Single Sign On (SSO) allows a computer user to log in to multiple systems via a
 
 Requirements include:
 
-* These docs apply for managing users on our [original user model](/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models). For SSO for users on New Relic One user model, see [Authentication domains](/docs/accounts/accounts-billing/new-relic-one-user-management/configure-authentication-domains-sso).
+* These docs apply for managing users on our [original user model](/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models). For enabling SSO for users on our New Relic One user model, see [Authentication domains](/docs/accounts/accounts-billing/new-relic-one-user-management/configure-authentication-domains-sso).
 * Access to this feature requires Pro or Enterprise edition. 
-* Owner role required
+* You must have the [Owner role](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model#roles).
 
 ## SSO settings UI page [#ui]
 
@@ -260,9 +260,9 @@ The **Session configuration** feature also includes the option to select an [aut
   >
 For an overview of our SAML SSO and SCIM docs, first read [Introduction to SAML SSO and SCIM](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-saml-scim). 
 
-As an additional security measure for SAML single sign-on (SSO) accounts, users are not added until they complete the email confirmation that New Relic sends automatically. Users in the pending state (not yet confirmed) won't receive notifications, such as alerts.
+As an additional security measure for SAML single sign-on (SSO) accounts, users are not added until they complete the email confirmation that we send automatically upon SAML SSO enablement. Users in the pending state (not yet confirmed) won't receive notifications, such as alerts. 
 
-For accounts **without** SAML SSO integration, the account Owner and Admins can add new users without requiring confirmation.
+For accounts **without** SAML SSO enabled, the account Owner and Admins can add new users without requiring confirmation.
 
 ### Requirements
 
@@ -273,17 +273,17 @@ For requirements, including which New Relic users this feature applies to, see [
 Follow this process to add and confirm users on our [original user model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-user-models) that are authenticating via SAML SSO:
 
 1. The account's Owner or an Administrator adds new users: Go to: **[account dropdown](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#account-dropdown) > Account settings > Account > Summary**.
-2. On SAML-enabled accounts, New Relic flags the users as **Pending** and sends an email confirmation. (Pending users will not receive notifications associated with their user role, such as alert notifications.)
+2. On SAML-enabled accounts, New Relic flags the users as **Pending** and sends an email confirmation. (Pending users won't receive New Relic product notifications, such as alert notifications.)
 3. Users select the link in the email to confirm their account, which directs them to the SAML provider's login URL.
 4. When users successfully sign into their SAML SSO end point (Auth0, Okta, OneLogin, Ping Identity, Salesforce, etc.), New Relic flags the users as **Active**.
 
 <Callout variant="caution">
-  If you disable SAML SSO, New Relic automatically flags all of your **Pending** users as **Active**. If you decide to re-enable SAML SSO later, New Relic automatically flags all users except the Owner as **Pending**, and they will need to confirm their account access by email.
+  If you disable SAML SSO, New Relic automatically flags all of your **Pending** users as **Active**. If you decide to re-enable SAML SSO later, New Relic automatically flags all users except the Owner as **Pending**, and they'll need to confirm their account access by email.
 </Callout>
 
-### Bypass email confirmation
+### Bypass email confirmation by claiming your domain
 
-Depending on your [subscription level](https://newrelic.com/application-monitoring/pricing), you may have the option to claim the domain names that you own and bypass the SAML SSO confirmation process. When the account Owner or Administrators add new users and their email address has a domain that matches the account's domains, New Relic automatically adds them as **Active** users.
+Depending on your [subscription level](https://newrelic.com/application-monitoring/pricing), you may have the option to claim the domain names that you own and bypass the SAML SSO confirmation process. When your Owner or Administrators add new users and their email address has a domain that matches the account's domains, New Relic automatically adds them as **Active** users.
 
 Benefits of identifying domain ownership include:
 
@@ -380,8 +380,6 @@ For users on our [original user model](/docs/accounts/original-accounts-billing/
 
 </Collapser>
 
-
-
   <Collapser
     id="partners-saml"
     title="Partners and SAML SSO"

src/content/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model.mdx

@@ -91,15 +91,15 @@ Here are instructions and considerations for some common user management tasks a
 
    <Collapser
     id="full-user-count"
-    title="Managing billable users"
+    title="Manage billable users"
   >
-If you're on the [New Relic One pricing model](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/), your billable user count is a factor in your billing. 
+If you're on the [New Relic One pricing model](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/), the user types of your users are a factor in your billing. 
 
 If you have multiple accounts in your organization, here are some important considerations when managing billable users on the original user model: 
 
-* You can be charged for billable users in all accounts in your organization, regardless of whether those accounts are marked as "active" or "inactive" (not reporting data) in the **Account settings** UI.  
-* You aren't able to see all your organization's users in a single UI. If your goal is to review and edit all your users (for example, editing their [user type](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type) for billing purposes), you must go to the **Users and roles** UI for each individual account.
+* You aren't able to see all your organization's users in a single UI. If your goal is to review and edit all your users (for example, editing their [user type](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type) for billing purposes), you must go to the **Users and roles** UI for each individual account. (Note that the ability to more easily manage your users is one benefit of our [newer user model](/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models).)
 * Because of the above point, the count of billable users you see in the **View your usage** UI may not match the number of users you see when you go to a specific account's **Users and roles** UI. 
+* You can be charged for billable users in all accounts in your organization, regardless of whether those accounts are marked as "active" or "inactive" (not reporting data) in the **Account settings** UI.  
 
 For tips on editing user type, see [Manage user type](#update-user-type).
 
@@ -138,7 +138,8 @@ For an introduction to using SAML SSO and/or SCIM provisioning, see [Get started
     id="view-pending"
     title="View pending SAML SSO users"
   >
-    New Relic accounts with [SAML Single Sign On (SSO)](/docs/accounts-partnerships/accounts/saml-single-sign/saml-service-providers) may have a list of **Pending users**. These are individuals who have been [added to the SAML-enabled account](/docs/accounts-partnerships/accounts/saml-single-sign/adding-users-saml-accounts) but have not yet confirmed.
+    If your organization has implemented [SAML Single Sign On](/docs/accounts-partnerships/accounts/saml-single-sign/saml-service-providers), you may have a list of **Pending users**. These are users who have been [added to the SAML-enabled account](/docs/accounts-partnerships/accounts/saml-single-sign/adding-users-saml-accounts) but have not yet confirmed. 
+
   </Collapser>
 
   <Collapser
@@ -182,6 +183,8 @@ For an introduction to using SAML SSO and/or SCIM provisioning, see [Get started
     id="owner"
     title="Update the account Owner"
   >
+    The Owner role concept exists only for users on our original user model. 
+
     A New Relic account can have only one Owner [role](/docs/accounts-partnerships/accounts/account-billing-usage/users-roles#roles) at any time. You must be the current account Owner to change your role to someone who currently has an Admin role for the account. If the [current Owner is unavailable](#no-owner), contact your account representative at New Relic, or get support at [support.newrelic.com](https://support.newrelic.com).
 
     You cannot delete or remove your assigned Owner role. However, if the account has one or more Admin role, you can change an Owner to an Admin.
@@ -367,7 +370,9 @@ Below are options for managing both managed add-on roles and custom add-on roles
 
 ## Account permissions [#account-rights]
 
-Here is a summary of user permissions. Individuals on a [parent account](/docs/accounts/original-accounts-billing/original-users-roles/mastersub-account-structure) automatically have the same level of access for all the child accounts of that parent account. However, they won't receive [email notifications for alerts or weekly reports](#alert-rights) for child accounts unless they are explicitly granted permission on those accounts.
+The table below gives a summary of roles and their permissions. Note that these are roles applicable only for our [original user model](/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models). 
+
+Users in a [parent account](/docs/accounts/original-accounts-billing/original-users-roles/mastersub-account-structure) have the same level of access for all the child accounts of that parent account. However, those users won't receive [email notifications for alerts or weekly reports](#alert-rights) for child accounts unless they are explicitly granted permission on those accounts.
 
 <table>
   <thead>
@@ -669,6 +674,8 @@ Here is a summary of user permissions. Individuals on a [parent account](/docs/a
   </tbody>
 </table>
 
+Have more questions about access to New Relic? See [Factors affecting access](/docs/accounts/accounts-billing/account-structure/factors-affecting-access-features-data). 
+
 ## Alert permissions [#alert-rights]
 
 Here is a summary of Admin and Add-on manager capabilities with [alerts](/docs/alerts/new-relic-alerts/getting-started/introduction-new-relic-alerts). To allow a User or Restricted User to execute any of these functions in alerts, assign an alerts add-on manager role.