Unverified Commit 705a2845 authored by Joseph's avatar Joseph Committed by GitHub

docs: typo fixes (#99350)

Found by our internal tool
parent 50199e6b
...@@ -506,7 +506,7 @@ export default function ExampleClientComponent() { ...@@ -506,7 +506,7 @@ export default function ExampleClientComponent() {
In addition, the new `useRouter` hook has the following changes: In addition, the new `useRouter` hook has the following changes:
- `isFallback` has been removed because `fallback` has [been replaced](#replacing-fallback). - `isFallback` has been removed because `fallback` has [been replaced](#replacing-fallback).
- The `locale`, `locales`, `defaultLocales`, `domainLocales` values have been removed because built-in i18n Next.js features are no longer necessary in the `app` directory. [Learn more about i18n](/docs/app/guides/internationalization). - The `locale`, `locales`, `defaultLocale`, `domainLocales` values have been removed because built-in i18n Next.js features are no longer necessary in the `app` directory. [Learn more about i18n](/docs/app/guides/internationalization).
- `basePath` has been removed. The alternative will not be part of `useRouter`. It has not yet been implemented. - `basePath` has been removed. The alternative will not be part of `useRouter`. It has not yet been implemented.
- `asPath` has been removed because the concept of `as` has been removed from the new router. - `asPath` has been removed because the concept of `as` has been removed from the new router.
- `isReady` has been removed because it is no longer necessary. During [prerendering](/docs/app/glossary#prerendering), any component that uses the [`useSearchParams()`](/docs/app/api-reference/functions/use-search-params) hook will skip the prerendering step and instead be rendered on the client at runtime. - `isReady` has been removed because it is no longer necessary. During [prerendering](/docs/app/glossary#prerendering), any component that uses the [`useSearchParams()`](/docs/app/api-reference/functions/use-search-params) hook will skip the prerendering step and instead be rendered on the client at runtime.
......
...@@ -185,7 +185,7 @@ export default function RootLayout({ ...@@ -185,7 +185,7 @@ export default function RootLayout({
return ( return (
<html lang="en"> <html lang="en">
<head> <head>
<meta charset="UTF-8" /> <meta charSet="UTF-8" />
<link rel="icon" type="image/svg+xml" href="/icon.svg" /> <link rel="icon" type="image/svg+xml" href="/icon.svg" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>My App</title> <title>My App</title>
...@@ -204,7 +204,7 @@ export default function RootLayout({ children }) { ...@@ -204,7 +204,7 @@ export default function RootLayout({ children }) {
return ( return (
<html lang="en"> <html lang="en">
<head> <head>
<meta charset="UTF-8" /> <meta charSet="UTF-8" />
<link rel="icon" type="image/svg+xml" href="/icon.svg" /> <link rel="icon" type="image/svg+xml" href="/icon.svg" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>My App</title> <title>My App</title>
......
...@@ -6,7 +6,7 @@ description: Style your Next.js application using Sass. ...@@ -6,7 +6,7 @@ description: Style your Next.js application using Sass.
{/* The content of this doc is shared between the app and pages router. You can use the `<PagesOnly>Content</PagesOnly>` component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */} {/* The content of this doc is shared between the app and pages router. You can use the `<PagesOnly>Content</PagesOnly>` component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */}
Next.js has built-in support for integrating with Sass after the package is installed using both the `.scss` and `.sass` extensions. You can use component-level Sass via CSS Modules and the `.module.scss`or `.module.sass` extension. Next.js has built-in support for integrating with Sass after the package is installed using both the `.scss` and `.sass` extensions. You can use component-level Sass via CSS Modules and the `.module.scss` or `.module.sass` extension.
First, install [`sass`](https://github.com/sass/sass): First, install [`sass`](https://github.com/sass/sass):
......
...@@ -133,7 +133,7 @@ test('should navigate to the about page', async ({ page }) => { ...@@ -133,7 +133,7 @@ test('should navigate to the about page', async ({ page }) => {
### Running your Playwright tests ### Running your Playwright tests
Playwright will simulate a user navigating your application using three browsers: Chromium, Firefox and Webkit, this requires your Next.js server to be running. We recommend running your tests against your production code to more closely resemble how your application will behave. Playwright will simulate a user navigating your application using three browsers: Chromium, Firefox and WebKit, this requires your Next.js server to be running. We recommend running your tests against your production code to more closely resemble how your application will behave.
Run `npm run build` and `npm run start`, then run `npx playwright test` in another terminal window to run the Playwright tests. Run `npm run build` and `npm run start`, then run `npx playwright test` in another terminal window to run the Playwright tests.
......
...@@ -613,7 +613,7 @@ Note that any allowed `remotePatterns` that respond with a redirect will follow ...@@ -613,7 +613,7 @@ Note that any allowed `remotePatterns` that respond with a redirect will follow
#### `loaderFile` #### `loaderFile`
`loaderFiles` allows you to use a custom image optimization service instead of Next.js. `loaderFile` allows you to use a custom image optimization service instead of Next.js.
```js filename="next.config.js" ```js filename="next.config.js"
module.exports = { module.exports = {
......
...@@ -108,7 +108,7 @@ An instance of an [`Error`](https://developer.mozilla.org/docs/Web/JavaScript/Re ...@@ -108,7 +108,7 @@ An instance of an [`Error`](https://developer.mozilla.org/docs/Web/JavaScript/Re
#### `error.message` #### `error.message`
- Errors forwarded from Client Components show the original `Error` message. - Errors forwarded from Client Components show the original `Error` message.
- Errors forwarded from Server Components show a generic message with an identifier. This is to prevent leaking sensitive details. You can use the identifier, under `errors.digest`, to match the corresponding server-side logs. - Errors forwarded from Server Components show a generic message with an identifier. This is to prevent leaking sensitive details. You can use the identifier, under `error.digest`, to match the corresponding server-side logs.
#### `error.digest` #### `error.digest`
......
--- ---
title: generateSitemaps title: generateSitemaps
nav_title: generateSitemaps nav_title: generateSitemaps
description: Learn how to use the generateSiteMaps function to create multiple sitemaps for your application. description: Learn how to use the generateSitemaps function to create multiple sitemaps for your application.
related: related:
title: Next Steps title: Next Steps
description: Learn how to create sitemaps for your Next.js application. description: Learn how to create sitemaps for your Next.js application.
......
...@@ -53,7 +53,7 @@ module.exports = { ...@@ -53,7 +53,7 @@ module.exports = {
return { return {
beforeFiles: [ beforeFiles: [
// These rewrites are checked after headers/redirects // These rewrites are checked after headers/redirects
// and before all files including _next/public files which // and before all files including _next/static and public files which
// allows overriding page files // allows overriding page files
{ {
source: '/some-page', source: '/some-page',
......
...@@ -68,7 +68,7 @@ The following options are available when running `next dev`: ...@@ -68,7 +68,7 @@ The following options are available when running `next dev`:
| `--turbopack` | Force enable [Turbopack](/docs/app/api-reference/turbopack) (enabled by default). Also available as `--turbo`. | | `--turbopack` | Force enable [Turbopack](/docs/app/api-reference/turbopack) (enabled by default). Also available as `--turbo`. |
| `--webpack` | Use Webpack instead of the default [Turbopack](/docs/app/api-reference/turbopack) bundler for development. | | `--webpack` | Use Webpack instead of the default [Turbopack](/docs/app/api-reference/turbopack) bundler for development. |
| `-p` or `--port <port>` | Specify a port number on which to start the application. Default: 3000, env: PORT | | `-p` or `--port <port>` | Specify a port number on which to start the application. Default: 3000, env: PORT |
| `-H`or `--hostname <hostname>` | Specify a hostname on which to start the application. Useful for making the application available for other devices on the network. Default: 0.0.0.0 | | `-H` or `--hostname <hostname>` | Specify a hostname on which to start the application. Useful for making the application available for other devices on the network. Default: 0.0.0.0 |
| `--experimental-https` | Starts the server with HTTPS and generates a self-signed certificate. | | `--experimental-https` | Starts the server with HTTPS and generates a self-signed certificate. |
| `--experimental-https-key <path>` | Path to a HTTPS key file. | | `--experimental-https-key <path>` | Path to a HTTPS key file. |
| `--experimental-https-cert <path>` | Path to a HTTPS certificate file. | | `--experimental-https-cert <path>` | Path to a HTTPS certificate file. |
......
...@@ -111,7 +111,7 @@ export const config = { ...@@ -111,7 +111,7 @@ export const config = {
`bodyParser` is automatically enabled. If you want to consume the body as a `Stream` or with [`raw-body`](https://www.npmjs.com/package/raw-body), you can set this to `false`. `bodyParser` is automatically enabled. If you want to consume the body as a `Stream` or with [`raw-body`](https://www.npmjs.com/package/raw-body), you can set this to `false`.
One use case for disabling the automatic `bodyParsing` is to allow you to verify the raw body of a **webhook** request, for example [from GitHub](https://docs.github.com/en/developers/webhooks-and-events/webhooks/securing-your-webhooks#validating-payloads-from-github). One use case for disabling the automatic `bodyParser` is to allow you to verify the raw body of a **webhook** request, for example [from GitHub](https://docs.github.com/en/developers/webhooks-and-events/webhooks/securing-your-webhooks#validating-payloads-from-github).
```js ```js
export const config = { export const config = {
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment