Proofread changes to index.mdx

astro/src/content/docs/lifecycle/migrate-users/index.mdx

@@ -101,7 +101,7 @@ With a bulk migration, you are moving all your users at once. The exact duration
 * Run the migration scripts or programs.
 * Perform the cutover and flip the system of record for all your users from the old system to the new.
 
-Bulk migration lets you import users at a single point in time, making for a clean cutover. You can import password hashes, including hashes performed with a custom, non-standard algorithm, making migration seamless for your users. You use the [User Import API](/docs/apis/users#import-users) to perform this. You can also [import refresh tokens](/docs/apis/users#import-refresh-tokens) if you want your users to be able to refresh access tokens transparently. When using the [User Import API](/docs/apis/users#import-users), you should import in batches of less than 10,000 users per request. After completing a migration you should [reindex of the Elasticsearch database](/docs/lifecycle/manage-users/search/search#reindexing-elasticsearch) as well.
+Bulk migration lets you import users at a single point in time, making for a clean cutover. You can import password hashes, including hashes performed with a custom, non-standard algorithm, making migration seamless for your users. You use the [User Import API](/docs/apis/users#import-users) to perform this. You can also [import refresh tokens](/docs/apis/users#import-refresh-tokens) if you want your users to be able to refresh access tokens transparently. When using the [User Import API](/docs/apis/users#import-users), you should only import batches of fewer than 10,000 users per request. After completing a migration you should [reindex of the Elasticsearch database](/docs/lifecycle/manage-users/search/search#reindexing-elasticsearch) as well.
 
 This approach has strengths:
 
@@ -310,7 +310,7 @@ Consider your change management strategy. How will you capture your FusionAuth s
 
 Prepare FusionAuth for your users and applications; while the exact configuration depends on your application needs, the following items should be considered.
 
-Create one or more tenants. Multiple tenants are useful for allowing someone to have the same email but different passwords or to have different settings, such as the theme or password rules. Add these via the API or navigate to <strong>Tenants</strong> and click the green plus sign.
+Create one or more tenants. Multiple tenants are useful for allowing someone to have the same email but different passwords or to have different settings, such as the theme or password rules. Add these via the API or navigate to <strong>Tenants</strong> and click the <strong>green plus sign</strong>.
 
 <img src="/img/docs/lifecycle/migrate-users/provider-specific/add-tenant.png" alt="Adding a tenant." width="1200" role="bottom-cropped" />