diff --git a/src/content/docs/workers/static-assets/migrate-from-pages.mdx b/src/content/docs/workers/static-assets/migrate-from-pages.mdx
index 1e8cb0b1e3e5eee..ae4c2dbe23fb7bd 100644
--- a/src/content/docs/workers/static-assets/migrate-from-pages.mdx
+++ b/src/content/docs/workers/static-assets/migrate-from-pages.mdx
@@ -172,7 +172,7 @@ If you use **Pages Functions with a [folder of `functions/`](/pages/functions/)*
 
 Although this command will remain available to you to run at any time, we do recommend considering using another framework if you wish to continue to use file-based routing. [HonoX](https://github.com/honojs/honox) is one popular option.
 
-Once the Worker script has been compiled, you can update your configuration file's `main` field to point to the location of its location:
+Once the Worker script has been compiled, you can update your configuration file's `main` field to point to the location it was built to:
 
 <WranglerConfig>
 
@@ -332,7 +332,7 @@ Optionally, you can also [protect these preview URLs with Cloudflare Access](/wo
 
 :::note
 
-Unlike Pages, Workers does not natively support defining different bindings in production vs. non-production builds. This is something we are actively exploring, but in the meantime, you may wish to explore using [Wrangler Environments](/workers/wrangler/environments/) and an [appropriate Workers Build configuration](/workers/ci-cd/builds/advanced-setups/#wrangler-environments) to achieve this.
+Unlike Pages, Workers does not natively support defining different bindings in production vs. non-production builds. This is something we are actively exploring, but in the meantime, you may wish to consider using [Wrangler Environments](/workers/wrangler/environments/) and an [appropriate Workers Build configuration](/workers/ci-cd/builds/advanced-setups/#wrangler-environments) to achieve this.
 
 :::