From 6c69c77622e4e61e07ab23a342cd18fd82616afb Mon Sep 17 00:00:00 2001 From: Surav Shrestha Date: Fri, 13 Oct 2023 17:18:37 +0545 Subject: [PATCH 1/6] docs: fix typo in examples/with-temporal/README.md --- examples/with-temporal/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/with-temporal/README.md b/examples/with-temporal/README.md index 06593b5ea886..dc5cab1c5d0c 100644 --- a/examples/with-temporal/README.md +++ b/examples/with-temporal/README.md @@ -28,7 +28,7 @@ Charging user 123 for 2 of item B102 Here is the Temporal code: - The Workflow: `temporal/src/workflows/order.ts` -- The Activites: `temporal/src/activities/{payment|inventory}.ts` +- The Activities: `temporal/src/activities/{payment|inventory}.ts` There are three parts of this starter project that are left unimplemented: From e7463a754f4fe5170b29773aa6ed32eec1baecfe Mon Sep 17 00:00:00 2001 From: Surav Shrestha Date: Fri, 13 Oct 2023 17:19:29 +0545 Subject: [PATCH 2/6] docs: fix typo in examples/with-supabase/README.md --- examples/with-supabase/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/with-supabase/README.md b/examples/with-supabase/README.md index 8a4b42d302f8..bcc2fc6cfdcd 100644 --- a/examples/with-supabase/README.md +++ b/examples/with-supabase/README.md @@ -29,7 +29,7 @@ - [Supabase Auth](https://supabase.com/auth) using cookies, making the user's session available throughout the entire Next.js app, for both client and server. - Styling with [Tailwind CSS](https://tailwindcss.com) - Optional deployment with [Supabase Vercel Integration and Vercel deploy](#deploy-your-own) - - Enviroment variables automatically assigned to Vercel project + - Environment variables automatically assigned to Vercel project ## Demo From 7d67a5d706134c4bb3d364585530920bb79dde0d Mon Sep 17 00:00:00 2001 From: Surav Shrestha Date: Fri, 13 Oct 2023 17:21:04 +0545 Subject: [PATCH 3/6] docs: fix typo in examples/with-quill-js/README.md --- examples/with-quill-js/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/with-quill-js/README.md b/examples/with-quill-js/README.md index 503d63bb454e..734fd9597c06 100644 --- a/examples/with-quill-js/README.md +++ b/examples/with-quill-js/README.md @@ -2,7 +2,7 @@ [Quill](https://quilljs.com/) is powerful rich text editor. This example uses [react-quill](https://github.com/zenoamaro/react-quill) to integrate Quill with Next.js. -Quill does not suppport SSR, so it's only loaded and rendered in the browser. +Quill does not support SSR, so it's only loaded and rendered in the browser. ## Deploy your own From 708b9987c551a29bf0ab0a8531dc47babb78af28 Mon Sep 17 00:00:00 2001 From: Surav Shrestha Date: Fri, 13 Oct 2023 17:22:06 +0545 Subject: [PATCH 4/6] docs: fix typo in examples/with-mqtt-js/README.md --- examples/with-mqtt-js/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/with-mqtt-js/README.md b/examples/with-mqtt-js/README.md index 347259c05e1a..95a8dd2cc81d 100644 --- a/examples/with-mqtt-js/README.md +++ b/examples/with-mqtt-js/README.md @@ -33,7 +33,7 @@ cp .env.local.example .env.local Then set each variable on `.env.local`: - `NEXT_MQTT_URI`: The URI of the broker. For example `wss://test.mosquitto.org:8081/mqtt` -- `NEXT_MQTT_CLIENTID`: An arbritrary string of max. 23 characters. +- `NEXT_MQTT_CLIENTID`: An arbitrary string of max. 23 characters. - `NEXT_MQTT_USERNAME`: The username for the connection to the broker. - `NEXT_MQTT_PASSWORD`: The password for the connection to the broker. From 89a0201d0112b84ddb4b73500e4f3adaf0c17f91 Mon Sep 17 00:00:00 2001 From: Surav Shrestha Date: Fri, 13 Oct 2023 17:23:02 +0545 Subject: [PATCH 5/6] docs: fix typo in errors/api-routes-static-export.mdx --- errors/api-routes-static-export.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/errors/api-routes-static-export.mdx b/errors/api-routes-static-export.mdx index 5351cbe7653b..c2906f88d87f 100644 --- a/errors/api-routes-static-export.mdx +++ b/errors/api-routes-static-export.mdx @@ -15,7 +15,7 @@ To resolve this issue, you have two main options: 1. Use the `next build` command instead of `next export` if you're deploying your application on platforms that don't require `next export`. For example, [Vercel](https://vercel.com) is a popular hosting platform for Next.js applications that supports this feature. 2. If you still need to use `next export`, make sure to remove any paths that use API routes from your `exportPathMap` in your `next.config.js` file. -3. Consider [incrementally adopting the App Router](/docs/app/building-your-application/upgrading/app-router-migration), which supportes [Route Handlers](/docs/app/building-your-application/routing/route-handlers). These "API Routes" can be used to create endpoints that can be statically exported in your application. +3. Consider [incrementally adopting the App Router](/docs/app/building-your-application/upgrading/app-router-migration), which supports [Route Handlers](/docs/app/building-your-application/routing/route-handlers). These "API Routes" can be used to create endpoints that can be statically exported in your application. ## Useful Links From 17db8a07e8d8c0b05e64939b7761961d109b3e63 Mon Sep 17 00:00:00 2001 From: Surav Shrestha Date: Fri, 13 Oct 2023 17:24:11 +0545 Subject: [PATCH 6/6] docs: fix typo in errors/404-get-initial-props.mdx --- errors/404-get-initial-props.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/errors/404-get-initial-props.mdx b/errors/404-get-initial-props.mdx index b47aee94f7e2..5629fd3224f0 100644 --- a/errors/404-get-initial-props.mdx +++ b/errors/404-get-initial-props.mdx @@ -13,7 +13,7 @@ Adding `getInitialProps` or `getServerSideProps` to your `404.js` page will caus To fix this error, you should remove `getInitialProps` from your `404.js` page. Additionally, ensure that no Higher-Order Components (HOCs) used in the `404.js` page are attaching `getInitialProps`. -If your `404.js` page requires data fetching, we recommend incrementall adopting the App Router and the [`not-found`](/docs/app/api-reference/file-conventions/not-found) file, which does support fetching data before displaying the 404 page. +If your `404.js` page requires data fetching, we recommend incrementally adopting the App Router and the [`not-found`](/docs/app/api-reference/file-conventions/not-found) file, which does support fetching data before displaying the 404 page. ## Useful Links