diff --git a/astro/src/content/docs/apis/users.mdx b/astro/src/content/docs/apis/users.mdx
index 9158dcd90e..cfb465598e 100644
--- a/astro/src/content/docs/apis/users.mdx
+++ b/astro/src/content/docs/apis/users.mdx
@@ -339,7 +339,7 @@ The response for this API contains the information for the User that was reactiv
 
 ## Import Users
 
-This API is used to bulk import multiple Users into FusionAuth. Each User must have at least an **email** or a **username**. This request is useful for migrating data from an existing database into FusionAuth. Additionally, you can provide an Id for each User inside the JSON User object of the request body. When using this API, you should import with batches of up to 100,000 users per request. After completing an import, you should [reindex the Elasticsearch database](/docs/lifecycle/manage-users/search/search#reindexing-elasticsearch) as well.
+This API is used to bulk import multiple Users into FusionAuth. Each User must have at least an **email** or a **username**. This request is useful for migrating data from an existing database into FusionAuth. Additionally, you can provide an Id for each User inside the JSON User object of the request body. When using this API, you should import with larger batches per request.  Depending on deployment capacity, batches of around 100,000 users per request is possible (more, if the system is scaled up). After completing an import, you should [reindex the Elasticsearch database](/docs/lifecycle/manage-users/search/search#reindexing-elasticsearch) as well.
 
 You should not make multiple calls to this API in parallel. Multiple sequential calls to this API are fine.
 
diff --git a/astro/src/content/docs/lifecycle/migrate-users/index.mdx b/astro/src/content/docs/lifecycle/migrate-users/index.mdx
index 9e4f09e02b..aae98af607 100644
--- a/astro/src/content/docs/lifecycle/migrate-users/index.mdx
+++ b/astro/src/content/docs/lifecycle/migrate-users/index.mdx
@@ -29,7 +29,7 @@ When you are migrating from another provider, you can do a bulk or slow migratio
 
 ### Bulk Migration
 
-Bulk migration lets you import users at one point in time, making for a clean cutover. You can import password hashes, including hashes performed with a custom, non-standard algorithm, making a migration seamless to 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), which helps 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 with batches of up to 100,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 one point in time, making for a clean cutover. You can import password hashes, including hashes performed with a custom, non-standard algorithm, making a migration seamless to 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), which helps 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 with larger batches per request.  Depending on deployment capacity, batches of around 100,000 users per request is possible (more if the system is scaled up). After completing a migration you should [reindex of the Elasticsearch database](/docs/lifecycle/manage-users/search/search#reindexing-elasticsearch) as well.
 
 A bulk migration is a good choice when you: