docs: fix several typos (#56788)
`Enviroment -> Environment` --------- Co-authored-by: Steven <steven@ceriously.com>
This commit is contained in:
parent
313ceac475
commit
869d93c777
6 changed files with 6 additions and 6 deletions
|
@ -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`.
|
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
|
## Useful Links
|
||||||
|
|
||||||
|
|
|
@ -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.
|
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.
|
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
|
## Useful Links
|
||||||
|
|
||||||
|
|
|
@ -33,7 +33,7 @@ cp .env.local.example .env.local
|
||||||
Then set each variable on `.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_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_USERNAME`: The username for the connection to the broker.
|
||||||
- `NEXT_MQTT_PASSWORD`: The password for the connection to the broker.
|
- `NEXT_MQTT_PASSWORD`: The password for the connection to the broker.
|
||||||
|
|
||||||
|
|
|
@ -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](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
|
## Deploy your own
|
||||||
|
|
||||||
|
|
|
@ -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.
|
- [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)
|
- Styling with [Tailwind CSS](https://tailwindcss.com)
|
||||||
- Optional deployment with [Supabase Vercel Integration and Vercel deploy](#deploy-your-own)
|
- 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
|
## Demo
|
||||||
|
|
||||||
|
|
|
@ -28,7 +28,7 @@ Charging user 123 for 2 of item B102
|
||||||
Here is the Temporal code:
|
Here is the Temporal code:
|
||||||
|
|
||||||
- The Workflow: `temporal/src/workflows/order.ts`
|
- 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:
|
There are three parts of this starter project that are left unimplemented:
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue