Spell fixes in text documents

examples/cms-sitefinity/README.md

@@ -76,7 +76,7 @@ In order to install it:
 
 ### Step 3. Enable the web service
 
-By default the web services are not allowed for anonymous users, so the yhave to be enabled.
+By default the web services are not allowed for anonymous users, so they have to be enabled.
 
 Go to /sitefinity/Administration/WebServices and edit the 'Default' web service to allow it to be accessible by 'Everyone'
 

examples/cms-storyblok/README.md

@@ -144,7 +144,7 @@ Then set each variable on `.env.local`:
 
 ### Step 9. Configure Image Optimization
 
-To safely allow optimizing images, define a list of supported URL patterns in `next.config.js`. Use the following configuration to allow Storyblok assets and Unspash image URL's
+To safely allow optimizing images, define a list of supported URL patterns in `next.config.js`. Use the following configuration to allow Storyblok assets and Unsplash image URL's
 
 ```
 module.exports = {

examples/cms-tina/README.md

@@ -56,7 +56,7 @@ yarn create next-app --example cms-tina cms-tina-app
 pnpm create next-app --example cms-tina cms-tina-app
 ```
 
-### Setp 1. Run Next.js in development mode
+### Step 1. Run Next.js in development mode
 
 To get started, no configuration is needed for local development and editing.
 

examples/cms-umbraco/README.md

@@ -102,7 +102,7 @@ Once completed you'll be redirected to the Umbraco backoffice where the blog sam
 All the sample content is unpublished to begin with. You need to publish all of it to show the blog posts on the blog.
 
 1. Click the _Posts_ item in the Content tree. This item contains all the individual blog posts.
-2. In the lower right hand corner of the browser you'll find a green button labelled "Save and publish".
+2. In the lower right hand corner of the browser you'll find a green button labeled "Save and publish".
 3. Click the little up-arrow next to this button and select "Publish with descendants...".
 4. In the dialog, tick "Include unpublished content items" to publish the _Posts_ item and all the blog posts in one go.
 

examples/cms-wordpress/README.md

@@ -8,7 +8,7 @@ This is an example on how you can build a Next.js 14 project (with App Router),
 - `sitemap.ts`: This automatically gets all paths from the API and generates a sitemap to serve on the `/sitemap.xml` route.
 - `middleware.ts`: This contains a middleware function that checks the users path for stored redirects, and redirects the user if a match is found.
 - `[[...slug]]`: This is the catch-all route that is used to render all pages. It is important that this route is not removed, as it is used to render all pages. It fetches the ContentType and renders the corresponding
-- `not-found.tsx`: This page is used for dynamic 404 handling - adjust the database id to match your decired WordPress page, and make sure the WordPress slug is "not-found", your 404 page will then be editable from your CMS.
+- `not-found.tsx`: This page is used for dynamic 404 handling - adjust the database id to match your desired WordPress page, and make sure the WordPress slug is "not-found", your 404 page will then be editable from your CMS.
 - `codegen.ts`: Automatic type generation for your WordPress installation
 - `Draft Mode`: Seamless Preview / Draft Preview support, using authentication through WPGraphQL JWT Authentication and Next.js Draft Mode
 - `On Demand Cache Revalidation`: Including a bare minimum WordPress theme that implements cache revalidation, WordPress link rewrites and other utils for integrating with Next.js
@@ -119,7 +119,7 @@ Deploy it to the cloud with [Vercel](https://vercel.com/new?utm_source=github&ut
 | `NEXT_PUBLIC_BASE_URL`               | Insert base url of frontend                                             | http://localhost:3000    | Used for generating sitemap, redirects etc.                                                                                                                         |
 | `NEXT_PUBLIC_WORDPRESS_API_URL`      | Insert base url of your WordPress installation                          | http://wp-domain.com     | Used when requesting wordpress for data                                                                                                                             |
 | `NEXT_PUBLIC_WORDPRESS_API_HOSTNAME` | The hostname without protocol for your WordPress installation           | wp-domain.com            | Used for dynamically populating the next.config images remotePatterns                                                                                               |
-| `HEADLESS_SECRET`                    | Insert the same random key, that you generated for your `wp-config.php` | INSERT_RANDOM_SECRET_KEY | Used for public exhanges between frontend and backend                                                                                                               |
+| `HEADLESS_SECRET`                    | Insert the same random key, that you generated for your `wp-config.php` | INSERT_RANDOM_SECRET_KEY | Used for public exchanges between frontend and backend                                                                                                               |
 | `WP_USER`                            | Insert a valid WordPress username                                       | username                 | Username for a system user created specifically for interacting with your WordPress installation                                                                    |
 | `WP_APP_PASS`                        | Insert application password                                             | 1234 5678 abcd efgh      | [Generate an application password](https://make.wordpress.org/core/2020/11/05/application-passwords-integration-guide/) for the WordPress user defined in `WP_USER` |
 
@@ -153,7 +153,7 @@ module.exports = {
 ## Advanced Custom Fields PRO (optional, but recommended)
 
 I will recommend building your page content by using the [Flexible Content](https://www.advancedcustomfields.com/resources/flexible-content/) data type in ACF Pro.
-This will make you able to create a "Block Builder" editor experience, but still having everything automatically type generated, and recieving the data in a structured way.
+This will make you able to create a "Block Builder" editor experience, but still having everything automatically type generated, and receiving the data in a structured way.
 The default "Gutenberg" editor returns a lot of HTML, which makes you loose a lot of the advantages of using GraphQL with type generation.
 
 ## Redirection setup

examples/with-babel-macros/README.md

@@ -31,5 +31,5 @@ plugin, then we can use the `preval.macro` in `app/page.tsx` to pre-evaluate
 code at build-time. `preval.macro` is effectively transforming our code, but
 we didn't have to configure it to make that happen!
 
-Specifically what we're doing is we're prevaling the username of the user who
+Specifically what we're doing is we're prevailing the username of the user who
 ran the build.

examples/with-turbopack/README.md

@@ -1,6 +1,6 @@
 # Next.js + Turbopack
 
-This example allows you to get started with `next dev --turbo` quicky.
+This example allows you to get started with `next dev --turbo` quickly.
 
 ## Deploy your own
 

packages/next-swc/README.md

@@ -64,7 +64,7 @@ flowchart TD
     D(next-core) --> E(next-build)
 ```
 
-- `next-custom-transforms`: provides next-swc specific SWC transform visitors. Turbopack, and the plain next-swc bidnings (`transform`) use these transforms. Since this is a bottom package can be imported in any place (turbopack / next-swc / wasm), it is important package do not contain specific dependencies. For example, using Turbopack's VC in this package will cause build failures to wasm bindings.
+- `next-custom-transforms`: provides next-swc specific SWC transform visitors. Turbopack, and the plain next-swc bindings (`transform`) use these transforms. Since this is a bottom package can be imported in any place (turbopack / next-swc / wasm), it is important package do not contain specific dependencies. For example, using Turbopack's VC in this package will cause build failures to wasm bindings.
 - `next-core`: Implements Turbopack features for the next.js core functionality. This is also the place where Turbopack-specific transform providers (implementing `CustomTransformer`) lives, which wraps swc's transformer in the `next-custom-transforms`.
 - `next-api`: Binding interface to the next.js provides a proper next.js functionality using `next-core`.
 - `napi` / `wasm`: The actual binding interfaces, napi for the node.js and wasm for the wasm. Note wasm bindings cannot import packages using turbopack's feature.

packages/next/src/client/components/react-dev-overlay/README.md

@@ -6,7 +6,7 @@
 - `font/` - Includes Geist fonts that will be served to the client via the internal `/__nextjs_font/...` route.
 - `pages/` - Main entrypoint and related files for Pages Router dev overlay.
 - `server/` - Source files related to the dev overlay that are to run on the server and not sent to the client.
-- `ui/` - Main source files that build the UI of the dev overlay. It is recommended to keep this directory isolated from the rest of the codebase to make it easier to be excluded from compiliation and be bundled in the future.
+- `ui/` - Main source files that build the UI of the dev overlay. It is recommended to keep this directory isolated from the rest of the codebase to make it easier to be excluded from compilation and be bundled in the future.
 - `utils/` - Utils that can also be used outside of this project unlike the ones inside the `ui/` directory.
 
 ## Development
@@ -27,7 +27,7 @@ This will start the Storybook server at `http://localhost:6006`.
 
 ### Styling
 
-Next.js direcly injects CSS into the DOM via `<style>` tag. The styles will not affect the user's application as the [styles are encapsulated](https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_shadow_DOM#encapsulation_from_css) from the rest of the application.
+Next.js directly injects CSS into the DOM via `<style>` tag. The styles will not affect the user's application as the [styles are encapsulated](https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_shadow_DOM#encapsulation_from_css) from the rest of the application.
 
 > [!TIP]
 > While Shadow DOM provides style encapsulation, the root element (i.e., `<nextjs-portal>`) can still inherit styles from parent elements like `<body>` or `<html>`. Direct styling on these parent elements (e.g., `body { contain: layout; }`) will affect the dev overlay.

turbopack/crates/turbo-persistence/README.md

@@ -57,7 +57,7 @@ Therefore there are there value types:
   - 8 bytes hash
   - 2 bytes block index
 
-An Index block contains `n` 8 bytes hashes, which specify `n - 1` hash ranges (eq hash goes into the prev range, except for the first key). Between these `n` hashes there are `n - 1` 2 byte block indicies that point to the block that contains the hash range.
+An Index block contains `n` 8 bytes hashes, which specify `n - 1` hash ranges (eq hash goes into the prev range, except for the first key). Between these `n` hashes there are `n - 1` 2 byte block indices that point to the block that contains the hash range.
 
 The hashes are sorted.
 
@@ -122,7 +122,7 @@ Reading start from the current sequence number and goes downwards.
 
 - We have all SST files memory mapped
 - for i = CURRENT sequence number .. 0
-  - Check AQMF from SST file for key existance -> if not continue
+  - Check AQMF from SST file for key existence -> if not continue
   - let block = 0
   - loop
     - Index Block: find key range that contains the key by binary search
@@ -150,7 +150,7 @@ For compaction we compute the "coverage" of the SST files. The coverage is the a
 
 For a single SST file we can compute `(max_hash - min_hash) / u64::MAX` as the coverage of the SST file. We sum up all these coverages to get the total coverage.
 
-Compaction chooses a few SST files and runs the merge step of merge sort on tham to create a few new SST files with sorted ranges.
+Compaction chooses a few SST files and runs the merge step of merge sort on them to create a few new SST files with sorted ranges.
 
 Example:
 
@@ -172,7 +172,7 @@ SST 3':                          |-----|
 
 The merge operation decreases the total coverage since the new SST files will have a coverage of < 1.
 
-But we need to be careful to insert the SST files in the correct location again, since items in these SST files might be overriden in later SST file and we don't want to change that.
+But we need to be careful to insert the SST files in the correct location again, since items in these SST files might be overridden in later SST file and we don't want to change that.
 
 Since SST files that are smaller than the current sequence number are immutable we can't change the files and we can't insert new files at this sequence numbers.
 Instead we need to insert the new SST after the current sequence number and copy all SST files after the original SST files after them. (Actually we only need to copy SST files with overlapping key hash ranges. And we can hardlink them instead). Later we will write the current sequence number and delete them original and all copied SST files.

turbopack/crates/turbo-static/readme.md

@@ -5,7 +5,7 @@ graph for your turbo tasks project.
 
 ## How it works
 
-- find all occurences of #[turbo_tasks::function] across all the packages you
+- find all occurrences of #[turbo_tasks::function] across all the packages you
   want to query
 - for each of the tasks we find, query rust analyzer to see which tasks call
   them

turbopack/crates/turbopack-swc-ast-explorer/README.md

@@ -1,6 +1,6 @@
 # swc-ast-explorer
 
-A small binary to print out SWC Abtract Syntax Trees.
+A small binary to print out SWC Abstract Syntax Trees.
 
 ```shell
 echo "console.log('hello')" | cargo run -p swc-ast-explorer

turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/node-default-import/issues/Specified module format (CommonJs) is not matching-63a9f9.txt

@@ -1,4 +1,4 @@
 error - [analysis] [project]/turbopack/crates/turbopack-tests/tests/execution/turbopack/basic/node-default-import/input/node_modules/esm-package/invalid-exports.cjs  Specified module format (CommonJs) is not matching the module format of the source code (EcmaScript Modules)
   The CommonJs module format was specified in the package.json that is affecting this source file or by using an special extension, but Ecmascript import/export syntax is used in the source code.
-  The module was automatically converted to an EcmaScript module, but that is in conflict with the specified module format. Either change the "type" field in the package.json or replace EcmaScript import/export syntax with CommonJs syntas in the source file.
+  The module was automatically converted to an EcmaScript module, but that is in conflict with the specified module format. Either change the "type" field in the package.json or replace EcmaScript import/export syntax with CommonJs syntax in the source file.
   In some cases EcmaScript import/export syntax is added by an transform and isn't actually part of the source code. In these cases revisit transformation options to inject the correct syntax.