Unverified Commit 3c9c9959 authored by Jam Balaya's avatar Jam Balaya Committed by GitHub

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-guideCo-authored-by: 's avatarJoseph <joseph.chamochumbi@vercel.com>
parent 1b821389
...@@ -215,7 +215,7 @@ module.exports = { ...@@ -215,7 +215,7 @@ module.exports = {
## Usage with CDNs ## Usage with CDNs
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. 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.
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. 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.
......
...@@ -739,7 +739,7 @@ module.exports = { ...@@ -739,7 +739,7 @@ module.exports = {
} }
``` ```
You can increase the TTL to reduce the number of revalidations and potentionally lower cost: You can increase the TTL to reduce the number of revalidations and potentially lower cost:
```js filename="next.config.js" ```js filename="next.config.js"
module.exports = { module.exports = {
......
...@@ -194,7 +194,7 @@ export default function Layout({ children }) { ...@@ -194,7 +194,7 @@ export default function Layout({ children }) {
## Gracefully handling fast navigation ## Gracefully handling fast navigation
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`). 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`).
```css filename="app/styles/global.css" ```css filename="app/styles/global.css"
.spinner { .spinner {
......
...@@ -566,7 +566,7 @@ module.exports = { ...@@ -566,7 +566,7 @@ module.exports = {
} }
``` ```
You can increase the TTL to reduce the number of revalidations and potentionally lower cost: You can increase the TTL to reduce the number of revalidations and potentially lower cost:
```js filename="next.config.js" ```js filename="next.config.js"
module.exports = { module.exports = {
......
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