fix(user migration): improve intro

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

@@ -43,7 +43,13 @@ We recommend **not** using the user migration wizard in these circumstances:
 
 If you have questions about whether you should use the user migration wizard, talk to your New Relic account representative. 
 
-## Understand user management concepts [#before-beginning]
+## Optional: review your users' user type [#user-type]
+
+For organizations on the [New Relic One pricing model](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/new-relic-one-pricing-billing), your users' [user type](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type) is a billing factor. 
+
+Whether you're currently on the New Relic One pricing model, or plan to soon [switch to that pricing model](/docs/accounts/original-accounts-billing/original-product-based-pricing/switch-new-models), it may make sense to edit your users' user type before doing the user migration. One reason for that is that the original **Users and roles** UI allows you to see when your users' last activity was, and that can be useful for determining what user type to make them. For tips on how to do this, see [Edit user type](/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model/#full-user-count).
+
+## Recommended: Understand user management concepts [#before-beginning]
 
 During the user migration procedure, you'll have a choice to either grant all your users access to all your organization's accounts, or to assign more granular access (set the roles and accounts your user groups have access to). 
 
@@ -55,19 +61,15 @@ The more you need to partition access to accounts or roles, the more it will hel
 
 To learn more, see [User management concepts](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#understand-concepts).
 
-## Recommendations and considerations [#plan-groups]
+You can edit and adjust your access grants after you've done the migration, but if you wanted to plan that out first, here are some tips for that: 
 
-If you're on New Relic One pricing, your users' [user type](/docs/accounts/accounts-billing/new-relic-one-user-management/user-type) is a billing factor. 
-
-If you'll need to do a good amount of partitioning of users' access to accounts or roles, as is common for larger organizations, you'll want to think about how you'll implement groups and roles. Here are some tips:  
-
-* For organizations with a good number of accounts, a common configuration is to have one user group with the [**Organization manager** role](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#standard-roles) (organization-level management capabilities), one group with the [**Authentication domain manager**](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#standard-roles) (user management capabilities), a group with the [**Billing user**](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#standard-roles) (billing-related capabilities) on the primary (first) account, and then configuring various users groups for admins, users, and other roles as needed on your other accounts.  
+* For organizations with a high number of accounts, a common configuration is to have one user group with the [**Organization manager** role](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#standard-roles) (organization-level management capabilities), one group with the [**Authentication domain manager**](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#standard-roles) (user management capabilities), a group with the [**Billing user**](/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts#standard-roles) (billing-related capabilities) on the primary (first) account, and then configuring various users groups for admins, users, and other roles as needed on your other accounts.  
 * Customers with smaller and/oor flatter organizations that are okay with transparency for all teams across all of their data could have as little as one or two groups.
 * For organizations where all data is in a single account, a common configuration might be having five or six groups.
 
-## Migrate your users with the migration wizard [#find]
+## Start the user migration process [#find]
 
-Before you start, be sure you've read [the requirements](#requirements). To start using the wizard: 
+Before you start, be sure you've read [the requirements](#requirements) and the other recommendations above. To start using the wizard: 
 
 1. From [one.newrelic.com](https://one.newrelic.com), click **Apps** in the top navigation. 
 2. In the table of apps, click the **User migration walkthrough** app.
@@ -190,6 +192,8 @@ Once your users are migrated to the new user model, you can find and manage them
 * **User management**: use this to view and add users, change their type (basic versus full), change their group, and approve user upgrade requests. 
 * **Organization and access**: use this to create access grants (granting groups access to roles and accounts), and configure authentication domains (SAML SSO settings and SCIM settings, and more). 
 
-For more about these tools, see the [new user management docs](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-managing-users/).
+For some tips for planning out access grants, see [Tips on access grants](#before-beginning).
+
+For more about these tools and concepts, see the [user management docs](/docs/accounts/accounts-billing/new-relic-one-user-management/introduction-managing-users).