Unverified Commit a3e37e32 authored by AZM's avatar AZM Committed by GitHub

Updated typo in the documentation (#43160)

It's is confusing for the first time readers and probably wrong!



## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [x] Errors have a helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [x] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have a helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `pnpm build && pnpm lint`
- [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
Co-authored-by: 's avatarSteven <229881+styfle@users.noreply.github.com>
parent 447cba0f
...@@ -22,7 +22,7 @@ export default Avatar ...@@ -22,7 +22,7 @@ export default Avatar
This folder is also useful for `robots.txt`, `favicon.ico`, Google Site Verification, and any other static files (including `.html`)! This folder is also useful for `robots.txt`, `favicon.ico`, Google Site Verification, and any other static files (including `.html`)!
> **Note**: Don't name the `public` directory anything else. The name cannot be changed and is the only directory used to serve static assets. > **Note**: Be sure the directory is named `public`. The name cannot be changed and is the only directory used to serve static assets.
> **Note**: Be sure to not have a static file with the same name as a file in the `pages/` directory, as this will result in an error. > **Note**: Be sure to not have a static file with the same name as a file in the `pages/` directory, as this will result in an error.
> >
......
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