fix(core users): clarifications to groups, roles

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/groups-roles-capabilities.mdx

@@ -29,8 +29,6 @@ Here's a diagram showing how user type restrictions on what a user can access ov
 ![Diagram - precedence of capability restrictions](./images/capability-restrictions.png "Diagram - precedence of capability restrictions")
 <figcaption>A user's group (and that group's associated role) can restrict their capabilities. The [user type](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type) can also restrict capabilities and that takes precedence over group/role restrictions. For example: a basic user may be assigned to a group that has full New Relic access, but their user type ([basic user](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type)) restrictions override their group permissions.</figcaption>
 
-A basic user's capabilities aren't defined by a specific role. A basic user can best be described as having our [**All product admin** role](#standard-roles) but without access to most of our more curated UI experiences. A core user is similar to a basic user but with a bit more access to some specific UI experiences. [Learn more about user type.](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type)
-
 ## What are groups? [#groups]
 
 For users on our New Relic One user model, a "group" is what allows the grouping together and managing of multiple users at the same time. A New Relic user always requires assignment to at least one group to have access to a New Relic account. Here's an explanation of how groups are tied to specific capabilities: 
@@ -222,6 +220,15 @@ Our standard roles include:
 
 For more about how you'd assign roles to groups and create custom roles, see the [user management tutorial](/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model). 
 
+### How do roles relate to user type? [#role-user-type]
+
+User type doesn't directly relate to roles. Some specifics: 
+
+* A basic user's capabilities aren't defined by a specific role. A basic user can best be described as having our [**All product admin** role](#standard-roles) but without access to most of our more curated UI experiences. 
+* A core user is similar to a basic user; it just has a few more capabilities. 
+
+[Learn more about user type.](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type)
+
 ## Capabilities [#capabilities]
 
 A role, whether one of our [standard roles](#standard-roles) or a custom role, is a set of capabilities. To view roles and their associated capabilities, use the [**Organization and access** UI](/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles/#where).

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-type.mdx

@@ -23,7 +23,8 @@ On the [New Relic One pricing model](/docs/accounts/accounts-billing/new-relic-o
 
 If you're tasked with [adding New Relic users](/docs/accounts/accounts-billing/new-relic-one-user-management/tutorial-add-new-user-groups-roles-new-relic-one-user-model/#add-users), one of the key decisions to make is what user type to make them. If you're not sure at first, you can add them as basic users and later decide which users you want to upgrade. For how to adjust user type, see [Manage user type](/docs/accounts/accounts-billing/new-relic-one-user-management/add-manage-users-groups-roles#edit-user-type).
 
-The user type is meant to be a fairly long-term setting based on a user's expected New Relic responsibilities over the next several weeks or longer. This intention is reflected in our [billing calculations](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#user-count) and [downgrade rules](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#user-downgrade-rules). For more frequent or more granular adjustments to a user's New Relic access, you can use [group and role assignments](/docs/accounts/accounts-billing/new-relic-one-user-management/groups-roles-capabilities). 
+The user type is meant to be a fairly long-term setting based on a user's expected New Relic responsibilities over the next several weeks or longer. This intention is reflected in our [billing calculations](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#user-count) and [downgrade rules](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing#user-downgrade-rules). For more frequent or more granular adjustments to a user's New Relic access, you can [assign them to more restrictive groups](/docs/accounts/accounts-billing/new-relic-one-user-management/groups-roles-capabilities). 
+
 
 ## Capabilities by user type [#user-type-capabilities]
 
@@ -645,5 +646,5 @@ For questions related to lack of access to New Relic, see [Factors affecting acc
 
 ## How does user type relate to roles and groups? [#user-type-groups-roles]
 
-Want to learn how user type relates to roles and groups? See [Groups, roles, and capabilities](?).
+Want to learn how user type relates to the group and role concepts? See [Groups, roles, and capabilities](/docs/accounts/accounts-billing/new-relic-one-user-management/groups-roles-capabilities#role-user-type).