Fix spelling and capitalization errors in documentation (#212)

Author: 314systems

next.config.js

@@ -4,9 +4,9 @@
 // let assetPrefix = undefined;
 
 ///** Deploys as a directory through GitHub Actions **/
-//const isGithubActions = process.env.GITHUB_ACTIONS || false
+//const isGitHubActions = process.env.GITHUB_ACTIONS || false
 //
-//if (isGithubActions) {
+//if (isGitHubActions) {
 //  // trim off `<owner>/`
 //  const repo = process.env.GITHUB_REPOSITORY.replace(/.*?\//, '')
 //

pages/aws/config.mdx

@@ -7,7 +7,7 @@ There is two build arguments that you can pass to the `open-next build` command:
 
 ### Configuration File
 
-For personalisation you need to create a file `open-next.config.ts` at the same place as your `next.config.js`, and export a default object that satisfies the `OpenNextConfig` interface. It is possible to not have an `open-next.config.ts` file, the default configuration will then be applied automatically.
+For personalization you need to create a file `open-next.config.ts` at the same place as your `next.config.js`, and export a default object that satisfies the `OpenNextConfig` interface. It is possible to not have an `open-next.config.ts` file, the default configuration will then be applied automatically.
 
 This file needs to be placed at the same level as your `next.config.js` file.
 

pages/aws/config/nx.mdx

@@ -159,7 +159,7 @@ export default $config({
 $ cd apps/next-site && sst install
 ```
 
-this will resolve the type issues and initialise SST.
+this will resolve the type issues and initialize SST.
 
 - next we need to add `sst.config.ts` to our `tsconfig.json`'s excludes array
 

pages/aws/contribute/plugin.mdx

@@ -16,7 +16,7 @@ openNextPlugin({
     deletes: ["id1"],
   })
 
-  //To inject arbritary code by using (import at top of file):
+  //To inject arbitrary code by using (import at top of file):
 
   //#import
 
@@ -63,7 +63,7 @@ openNextEdgePlugin({
   nextDir: "next",
   // The path to the edgeFunctionHandler.js file that we'll use to bundle the routing
   edgeFunctionHandlerPath: "./edgeFunctionHandler.js",
-  // The middlewareInfo from the middlware manifest file
+  // The middlewareInfo from the middleware manifest file
   middlewareInfo: middlewareInfo
   // If the app should be bundled for cloudflare workers
   isInCloudflare: true

pages/aws/inner_workings/components/overview.mdx

@@ -24,7 +24,7 @@ Every backend is a separate module. The following backends are available:
 - Warmer
 - Initializer
 
-All these backends can be overrided to fit your needs. They share some common ground for the configuration and the way they are used.
+All these backends can be overridden to fit your needs. They share some common ground for the configuration and the way they are used.
 
 ### Common Overrides
 

pages/aws/v2/inner_workings/plugin.mdx

@@ -1,6 +1,6 @@
 import { Callout } from "nextra/components";
 
-Open-next use esbuild to build the project. Given that we aim to support multiple version of Next and multiple runtime, we developped a plugin to override some parts of our code at build time with an esbuild plugin.
+Open-next use esbuild to build the project. Given that we aim to support multiple version of Next and multiple runtime, we developed a plugin to override some parts of our code at build time with an esbuild plugin.
 
 <Callout type="warning" emoji="⚠️">
   As of now, the plugin is internal and not exposed to the user. We might expose it in the future, but for

pages/cloudflare/caching.mdx

@@ -5,7 +5,7 @@ import { Tabs } from "nextra/components";
 
 Next.js offers multiple ways to improve an application's performance by [caching](https://nextjs.org/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating#caching-data) routes and network requests. An application will try to pre-render and cache as much data as possible during build-time to reduce the amount of work required when serving a response to a user.
 
-The cache data are updated using revalidation, either peridiocally or on-demand:
+The cache data are updated using revalidation, either periodically or on-demand:
 
 - "[Time-based revalidation](https://nextjs.org/docs/app/building-your-application/data-fetching/incremental-static-regeneration#time-based-revalidation)" updates the cache data after the revalidation delay specified by the applications expires
 - "[On-demand revalidation](https://nextjs.org/docs/app/building-your-application/data-fetching/incremental-static-regeneration#on-demand-revalidation-with-revalidatetag)" allows to invalid cache entries with a specific tag (via `revalidateTag`) or at a given path (via `revalidatePath`). You can also use `res.revalidate` in Pages router API route.
@@ -585,9 +585,9 @@ export default defineCloudflareConfig({
 });
 ```
 
-##### 4. Initialise the cache during deployments
+##### 4. Initialize the cache during deployments
 
-In order for the cache to be properly initialised with the build-time revalidation data, you need to run a command as part of your deploy step. This should be run as part of each deployment to ensure that the cache is being populated with each build's data.
+In order for the cache to be properly initialized with the build-time revalidation data, you need to run a command as part of your deploy step. This should be run as part of each deployment to ensure that the cache is being populated with each build's data.
 
 To populate remote bindings and create a new [version](https://developers.cloudflare.com/workers/configuration/versions-and-deployments/#versions) of your application at the same time, you can use either the [`deploy`](/cloudflare/cli#deploy-command) command or the [`upload`](/cloudflare/cli#upload-command) command. Similarly, the [`preview`](/cloudflare/cli#preview-command) command will populate your local bindings and start a Wrangler dev server.
 

pages/cloudflare/community.mdx

@@ -17,7 +17,7 @@ Here is a list of some of the features it includes:
   - Rate Limiting with Cloudflare KV to prevent abuse
   - Validation for all user actions with react-zsa and zod
 - Database: Drizzle ORM and Cloudflare D1
-- UI: Shadcn, Tailwind CSS and Hero UI (formely NextUI)
+- UI: `shadcn/ui`, Tailwind CSS and HeroUI (formerly NextUI)
 - Transactional email templates with react-email and integration with Resend and Brevo
 - Dev Experience
   - Completely type safe
@@ -26,5 +26,5 @@ Here is a list of some of the features it includes:
     - .cursorrules
     - A markdown project documentation that Cursor can refer to for more context and better responses
   - Detailed documentation for local development and production deployment
-  - Automatic deployment using Github Actions and the Wrangler CLI
+  - Automatic deployment using GitHub Actions and the Wrangler CLI
 - And more...

pages/cloudflare/former-releases/0.2/get-started.mdx

@@ -137,4 +137,4 @@ Either deploy via the command line:
 npm run deploy:worker
 ```
 
-Or [connect a Github or Gitlab repository](https://developers.cloudflare.com/workers/ci-cd/), and Cloudflare will automatically build and deploy each pull request you merge to your production branch.
+Or [connect a GitHub or GitLab repository](https://developers.cloudflare.com/workers/ci-cd/), and Cloudflare will automatically build and deploy each pull request you merge to your production branch.

pages/cloudflare/former-releases/0.3/caching.mdx

@@ -10,7 +10,7 @@ By default, all `fetch()` subrequests made in your Next.js app are cached. Refer
 
 Note that [Revalidating](https://nextjs.org/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating#revalidating-data) is not yet supported.
 
-Next.js primes the cache at build time. The build time values are serverd by the [Workers Assets](https://developers.cloudflare.com/workers/static-assets/).
+Next.js primes the cache at build time. The build time values are served by the [Workers Assets](https://developers.cloudflare.com/workers/static-assets/).
 
 <Callout>
   Workers KV is eventually consistent, which means that it can take up to 60 seconds for updates to be