Skip to content

Commit 3c9c995

Browse files
docs: fix typos (#82503)
## Summary Fix typos and spelling errors in various MDX documentation files to improve clarity and consistency. Documentation: - Standardize 'cacheable' spelling across self-hosting guide - Correct 'potentionally' to 'potentially' in image component references - Fix 'unecessary' to 'unnecessary' in use-link-status guide ### Improving Documentation - [x] Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - [x] Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide Co-authored-by: Joseph <[email protected]>
1 parent 1b82138 commit 3c9c995

File tree

4 files changed

+4
-4
lines changed

4 files changed

+4
-4
lines changed

docs/01-app/02-guides/self-hosting.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,7 @@ module.exports = {
215215

216216
## Usage with CDNs
217217

218-
When using a CDN in front on your Next.js application, the page will include `Cache-Control: private` response header when dynamic APIs are accessed. This ensures that the resulting HTML page is marked as non-cachable. If the page is fully prerendered to static, it will include `Cache-Control: public` to allow the page to be cached on the CDN.
218+
When using a CDN in front on your Next.js application, the page will include `Cache-Control: private` response header when dynamic APIs are accessed. This ensures that the resulting HTML page is marked as non-cacheable. If the page is fully prerendered to static, it will include `Cache-Control: public` to allow the page to be cached on the CDN.
219219

220220
If you don't need a mix of both static and dynamic components, you can make your entire route static and cache the output HTML on a CDN. This Automatic Static Optimization is the default behavior when running `next build` if dynamic APIs are not used.
221221

docs/01-app/03-api-reference/02-components/image.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -739,7 +739,7 @@ module.exports = {
739739
}
740740
```
741741

742-
You can increase the TTL to reduce the number of revalidations and potentionally lower cost:
742+
You can increase the TTL to reduce the number of revalidations and potentially lower cost:
743743

744744
```js filename="next.config.js"
745745
module.exports = {

docs/01-app/03-api-reference/04-functions/use-link-status.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -194,7 +194,7 @@ export default function Layout({ children }) {
194194

195195
## Gracefully handling fast navigation
196196

197-
If the navigation to a new route is fast, users may see an unecessary flash of the loading indicator. One way to improve the user experience and only show the loading indicator when the navigation takes time to complete is to add an initial animation delay (e.g. 100ms) and start the animation as invisible (e.g. `opacity: 0`).
197+
If the navigation to a new route is fast, users may see an unnecessary flash of the loading indicator. One way to improve the user experience and only show the loading indicator when the navigation takes time to complete is to add an initial animation delay (e.g. 100ms) and start the animation as invisible (e.g. `opacity: 0`).
198198

199199
```css filename="app/styles/global.css"
200200
.spinner {

docs/02-pages/04-api-reference/01-components/image-legacy.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -566,7 +566,7 @@ module.exports = {
566566
}
567567
```
568568

569-
You can increase the TTL to reduce the number of revalidations and potentionally lower cost:
569+
You can increase the TTL to reduce the number of revalidations and potentially lower cost:
570570

571571
```js filename="next.config.js"
572572
module.exports = {

0 commit comments

Comments
 (0)