chore: Use second person POV

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

@@ -27,7 +27,7 @@ Your ability to manage and use Nerdpacks depends on your user's:
 - Type
 - Role
 
-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 user Nerdpack capabilities.
+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
 
@@ -39,7 +39,7 @@ If your organization was created before July 30, 2020 and you haven't transition
 | Publish Nerdpacks | no | no | yes | yes |
 | Subscribe to Nerdpacks | no | no | yes | yes |
 | Tag Nerdpacks | no | no | yes | yes |
-| Use Nerdlets or visualizations created by the user's accounts | no | yes | yes | yes |
+| Use Nerdlets or visualizations created by your accounts | no | yes | yes | yes |
 | Use Nerdlets created by New Relic | no* | yes | yes | yes |
 | Use visualizations created by New Relic | no | yes | yes | yes |
 
@@ -55,7 +55,7 @@ If your organization is part of the [New Relic One pricing model](https://docs.n
 | Publish Nerdpacks | no | yes |
 | Subscribe to Nerdpacks | no | yes |
 | Tag Nerdpacks | no | yes |
-| Use Nerdlets or visualizations created by the user's accounts | no | yes |
+| Use Nerdlets or visualizations created by your accounts | no | yes |
 | Use Nerdlets created by New Relic | no* | yes |
 | Use visualizations created by New Relic | no | yes |
 
@@ -67,7 +67,7 @@ Learn the differences between how basic users, full users, and admins can use an
 
 ### Basic users
 
-Basic users in the original user model are limited in their Nerdpack capabilities. They can only create and serve Nerdpacks locally. To publish, tag, subscribe to, and use their Nerdpacks, a basic user must be upgraded to a full user. An admin user on their account can do this for them.
+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.
 
 <Callout variant="tip">
 
@@ -77,28 +77,26 @@ If you're a basic user, you generally can't use any Nerdpacks. However, there ar
 
 ### Full users
 
-Full users in the original user model fit into two categories:
+If you're a full user in the original user model, you either:
 
-- Those who have been granted the **Nerdpack Manager** add-on role
-- Those who have not been granted the **Nerdpack Manager** add-on role
+- Have the **Nerdpack Manager** add-on role
+- Don't have the **Nerdpack Manager** add-on role
 
-The **Nerdpack Manager** role is required to publish, subscribe to, and tag Nerdpacks. So a full user who doesn't have the **Nerdpack Manager** role is only allowed to create and serve Nerdpacks locally and use Nerdpacks that their accounts have already been subscribed to.
+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, a full user must be either upgraded to an admin user or granted the **Nerdpack Manager** add-on role by an admin.
-
-A full user with the **Nerdpack Manager** role can perform any of the Nerdpack capabilities and is, therefore, equivalent to an owner or admin within the context of Nerdpacks.
+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.
 
 ### Owner/Admin users
 
-An owner or admin user can perform any of the Nerdpack capabilities, including creating, serving, publishing, tagging, subscribing to, and using any and all Nerdpack artifacts, both Nerdlets and visualizations, either built by New Relic or by their own accounts.
+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 artifacts, 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 and full 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/).
 
 ### Basic users
 
-Like in the original user model, basic users in the New Relic One user model are limited in their Nerdpack capabilities. They can only create and serve Nerdpacks locally. To publish, tag, subscribe to, and use their Nerdpacks, a basic user must be upgraded to a full user by an admin.
+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 user.
 
 <Callout variant="tip">
 
@@ -108,18 +106,18 @@ If you're a basic user, you generally can't use any Nerdpacks. However, there ar
 
 ### Full users
 
-Full users in the New Relic One user model fit into two categories:
+If you're a full user in the New Relic One user model, you either:
 
-- Those who have been granted the **Nerdpacks "modify"** privilege
-- Those who have not been granted the **Nerdpacks "modify"** privilege
+- Have the **Nerdpacks "modify"** privilege
+- Don't have the **Nerdpacks "modify"** privilege
 
-The **Nerdpacks "modify"** privilege is required to publish, subscribe to, and tag Nerdpacks. So a full user who doesn't have the **Nerdpacks "modify"** privilege is only allowed to create and serve Nerdpacks locally and use Nerdpacks that their accounts have already been subscribed to.
+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.
 
-So 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"** privilege.
 
 <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, a full user has the ability to manage Nerdpacks. However, if an admin creates a custom group that does not include this privilege, full users assigned to that custom group won't be able to manage Nerdpacks.
+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 user. However, if you're a full user assigned to a custom group that doesn't include the **Nerdpacks "modify"** privilege, you won't be able to manage Nerdpacks.
 
 </Callout>
 
@@ -131,6 +129,6 @@ 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 the master account subscribes to the Nerdpack, then all three accounts can use it. If **Account 1** subscribes to it, only **Account 1** can use it, because neither **Master** nor **Account 2** is downstream in the hierarchy.
+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 neither **Master** nor **Account 2** can subscribe to it or use it.
+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**.