fix(docs): use consistent spelling for ‘adapter’ (cloudflare#23301)

Author: yeskunall

src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/known-limitations.mdx

@@ -44,7 +44,7 @@ Resolve-DnsName -Name google.com
 
 ## 4G/5G embedded modules
 
-Because of how the WARP client instantiates the local DNS Proxy, it is incompatible with 4G/5G cellular adaptors which have IPv6 enabled. To run WARP on these devices, you will need to disable IPv6 on the system.
+Because of how the WARP client instantiates the local DNS Proxy, it is incompatible with 4G/5G cellular adapters which have IPv6 enabled. To run WARP on these devices, you will need to disable IPv6 on the system.
 
 :::note
 

src/content/docs/workers/framework-guides/web-apps/astro.mdx

@@ -160,7 +160,7 @@ If your Astro project uses [on demand rendering (also known as SSR)](https://doc
         </WranglerConfig>
         <Details header="What's this configuration doing?">
         	The key parts of this config are:
-        	- `main` points to the entry point of your Worker script. This is generated by the Astro adaptor, and is what powers your server-rendered pages.
+        	- `main` points to the entry point of your Worker script. This is generated by the Astro adapter, and is what powers your server-rendered pages.
         	- `assets.directory` tells Wrangler where to find your static assets. In this case, we're telling Wrangler to look in the `./dist` directory. If your assets are in a different directory, update the `directory` value accordingly.
 
         	Read more about [Wrangler configuration options](/workers/wrangler/configuration/) and [asset configuration options](/workers/wrangler/configuration/#assets).

src/content/docs/workers/framework-guides/web-apps/nextjs.mdx

@@ -32,7 +32,7 @@ This is a simple getting started guide. For detailed documentation on how the to
 
 Next.js supports Server-side and Client-side rendering, as well as Partial Prerendering which lets you combine static and dynamic components in the same route.
 
-You can deploy your Next.js app to Cloudflare Workers using the OpenNext adaptor.
+You can deploy your Next.js app to Cloudflare Workers using the OpenNext adapter.
 
 ## Next.js supported features
 

src/content/docs/workers/static-assets/migration-guides/migrate-from-pages.mdx

@@ -32,7 +32,7 @@ Migrating from Cloudflare Pages to Cloudflare Workers is often a straightforward
 
 ### Frameworks
 
-If your Pages project uses [a popular framework](/workers/framework-guides/), most frameworks already have adaptors available for Cloudflare Workers. Switch out any Pages-specific adaptors for the Workers equivalent and follow any guidance that they provide.
+If your Pages project uses [a popular framework](/workers/framework-guides/), most frameworks already have adapters available for Cloudflare Workers. Switch out any Pages-specific adapters for the Workers equivalent and follow any guidance that they provide.
 
 ### Project configuration