fix(nerdpack permission): updating for core launch

src/markdown-pages/build-apps/permission-manage-apps.mdx

@@ -21,19 +21,19 @@ Understand the requirements for managing and using Nerdpacks in New Relic One.
 
 ## Capabilities at a glance
 
-Your ability to manage and use Nerdpacks depends on your user's:
+Your ability to manage and use Nerdpacks is affected by a New Relic user's:
 
-- Model (original or New Relic One model)
-- Type
-- Role
+- User model (original or New Relic One model)
+- User type
+- Assigned roles
 
 Whether you're on the [original user model](https://docs.newrelic.com/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/) or the [New Relic One user model](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure/), review the tables below for a summary of your Nerdpack capabilities.
 
 ### Original user model
 
-If your organization was created before July 30, 2020 and you haven't transitioned to our New Relic One pricing model, you're on the [original pricing plan](https://docs.newrelic.com/docs/accounts/original-accounts-billing/product-pricing/product-based-pricing/). Capabilities for our [original user model](https://docs.newrelic.com/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/) differ from those of our [new user model](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure/):
+If your users are on our [original user model](https://docs.newrelic.com/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models), here are details about your New Relic One app capabilities:  
 
-| | Basic user | Full user without the Nerdpack Manager add-on role | Full user with the Nerdpack Manager add-on role | Owner/Admin user |
+| | Basic user | Core or full platform user without Nerdpack Manager add-on role | Core or full platform user with Nerdpack Manager add-on role | Owner/Admin user |
 |:--|:-:|:-:|:-:|:-:|
 | Serve Nerdpacks | yes | yes | yes | yes |
 | Publish Nerdpacks | no | no | yes | yes |
@@ -47,9 +47,9 @@ _* There are a few Nerdlets that basic users are allowed to use. See [Basic user
 
 ### New Relic One user model
 
-If your organization is part of the [New Relic One pricing model](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing/), the user types, privileges, and capabilities are different than those of our original user model:
+If your users are on our [New Relic One user model](https://docs.newrelic.com/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models), here are details about your New Relic One app capabilities:  
 
-| | Basic user | Full platform user/Core user |
+| | Basic user | Core or full platform user |
 |---|---|---|
 | Serve Nerdpacks | yes | yes |
 | Publish Nerdpacks | no | yes |
@@ -63,72 +63,72 @@ _* There are a few Nerdlets that basic users are allowed to use. See [Basic user
 
 ## Nerdpack permissions: Original user model
 
-Learn the differences between how basic users, full users, and admins can use and manage Nerdpacks in the [original user model](https://docs.newrelic.com/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/).
+In this section, we'll explain the differences between how basic users, full users, and admins on our [original user model](https://docs.newrelic.com/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/) can use and manage Nerdpacks. 
 
 ### Basic users
 
-If you're a basic user in the original user model, you're limited in your Nerdpack capabilities. You can only create and serve Nerdpacks locally. To publish, tag, subscribe to, and use your Nerdpacks, an admin must upgrade you to a full user.
+If you're a basic user on our original user model, you're limited in your Nerdpack capabilities. You can only create and serve Nerdpacks locally. To publish, tag, subscribe to, and use your Nerdpacks, an admin must upgrade you to a full user.
 
 <Callout variant="tip">
 
-If you're a basic user, you generally can't use any Nerdpacks. However, there are some Nerdlets that New Relic maintains that you can use. These are rare and there is currently no way for you to distinguish them in our web interface. And even if you can use a Nerdlet in a Nerdpack, you're never able to use custom visualizations. For this, you must be upgraded to a full user.
+If you're a basic user, you generally can't use any Nerdpacks. However, there are some Nerdlets that New Relic maintains that you can use. These are rare and there is currently no way for you to distinguish them in our web interface. And even if you can use a Nerdlet in a Nerdpack, you're never able to use custom visualizations. For this, you must be upgraded to a core or full platform user.
 
 </Callout>
 
-### Full users
+### Core users and full platform users
 
-If you're a full user in the original user model, you either:
+If you're a core or full platform user on our original user model, you either:
 
-- Have the **Nerdpack Manager** add-on role
+- Have the **Nerdpack Manager** add-on role, or
 - Don't have the **Nerdpack Manager** add-on role
 
 The **Nerdpack Manager** role is required to publish, subscribe to, and tag Nerdpacks. So if you don't have the **Nerdpack Manager** role, you can only create and serve Nerdpacks locally and use Nerdpacks that your accounts have already been subscribed to.
 
-To publish, tag, or subscribe to a Nerdpack, an admin must upgrade you to a full user or grant you the **Nerdpack Manager** add-on role.
+To publish, tag, or subscribe to a Nerdpack, an admin must upgrade you to a core user or full platform user, or grant you the **Nerdpack Manager** add-on role.
 
 ### Owner/Admin users
 
 If you're an owner or admin user, you can perform any of the Nerdpack capabilities. You can create, serve, publish, tag, subscribe to, and use any and all Nerdpack items, both Nerdlets and visualizations. This includes Nerdpacks built by New Relic or by one of your accounts.
 
 ## Nerdpack permissions: New Relic One user model
 
-Learn the differences between how basic users, full platform users, and core users can use and manage Nerdpacks in the [New Relic One user model](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-user-management/new-relic-one-user-model-understand-user-structure/).
+In this section, we'll explain the differences between how basic users, full platform users, and core users on our [New Relic One user model](https://docs.newrelic.com/docs/accounts/original-accounts-billing/original-users-roles/overview-user-models) can use and manage Nerdpacks. 
 
 ### Basic users
 
-If you're a basic user in the New Relic One user model, you're limited in your Nerdpack capabilities. You can only create and serve Nerdpacks locally. To publish, tag, subscribe to, and use your Nerdpacks, an admin must upgrade you to a full platform user or core user.
+If you're a basic user on our New Relic One user model, you're limited in your Nerdpack capabilities. You can only create and serve Nerdpacks locally. To publish, tag, subscribe to, and use your Nerdpacks, an admin must upgrade you to a full platform user or core user.
 
 <Callout variant="tip">
 
 If you're a basic user, you generally can't use any Nerdpacks. However, there are some Nerdlets that New Relic maintains that you can use. These are rare and there is currently no way for you to distinguish them in our web interface. And even if you can use a Nerdlet in a Nerdpack, you're never able to use custom visualizations. For this, you must be upgraded to a full platform user or a core user.
 
 </Callout>
 
-### Full platform users/Core users
+### Core users and full platform users
 
-If you're a full platform user or a core user in the New Relic One user model, you either:
+If you're a core user or a full platform user on the New Relic One user model, you either:
 
-- Have the **Nerdpacks "modify"** privilege
+- Have the **Nerdpacks "modify"** privilege, or
 - Don't have the **Nerdpacks "modify"** privilege
 
 The **Nerdpacks "modify"** privilege is required to publish, subscribe to, and tag Nerdpacks. So if you don't have the **Nerdpacks "modify"** privilege, you can only create and serve Nerdpacks locally and use Nerdpacks that your accounts have already been subscribed to.
 
-To publish, tag, or subscribe to your Nerdpack, an admin must grant you the **Nerdpacks "modify"** privilege.
+To publish, tag, or subscribe to your Nerdpack, an admin must grant you the **Nerdpacks "modify"** capability.
 
 <Callout variant="tip">
 
-The **Nerdpacks "modify"** privilege is included in both the **User** and **Admin** groups, the only groups available by default. So in most cases, you'll have the ability to manage Nerdpacks as a full platform user or a core user. However, if you're a full platform user or a core user assigned to a custom group that doesn't include the **Nerdpacks "modify"** privilege, you won't be able to manage Nerdpacks.
+The **Nerdpacks "modify"** capability is included in both the **User** and **Admin** groups, the only groups available by default. So in most cases, you'll have the ability to manage Nerdpacks as a full platform user or a core user. However, if you're a full platform user or a core user assigned to a custom group that doesn't include the **Nerdpacks "modify"** privilege, you won't be able to manage Nerdpacks.
 
 </Callout>
 
-## Master/Sub-account Capabilities
+## Parent/child account capabilities
 
-Some accounts, called master accounts, have sub-accounts that report data back up to them. This organizational hierarchy affects Nerdpack capabilities.
+Some New Relic organizations have [parent/child account structures](https://docs.newrelic.com/docs/accounts/original-accounts-billing/original-users-roles/parent-child-account-structure). For these organizations, child accounts (sometimes referred to as sub-accounts) report data back up to the parent accounts (sometimes referred to as master accounts). This organizational hierarchy affects Nerdpack capabilities.
 
 In general, the flow of control moves downstream:
 
 ![Master/Sub-account example](../../images/build-an-app/master-sub-accounts-nerdpacks.png)
 
 In this example scenario **A**, the master account publishes a Nerdpack. This means that all three accounts, **Master**, **Account 1**, and **Account 2**, can subscribe to it. If you subscribe the master account to the Nerdpack, then users of all three accounts can use it. If you subscribe **Account 1** to it, only **Account 1** users can use it, because neither **Master** nor **Account 2** is downstream in the hierarchy.
 
-In scenario **B**, the sub-account, **Account 1**, publishes a Nerdpack, so you can't use or subscribe to the Nerdpack from **Master** or **Account 2**.
+In scenario **B**, the child account, **Account 1**, publishes a Nerdpack, so you can't use or subscribe to the Nerdpack from **Master** or **Account 2**.