Unverified Commit 6474cf0f authored by GyoHeon's avatar GyoHeon Committed by GitHub

chore(docs): fix miss spell (#67228)

### Improving Documentation

- Just add `'`


![image](https://github.com/vercel/next.js/assets/66263916/ce7c5e11-38e9-4937-9034-3278b36e1e2b)
Co-authored-by: 's avatarJiwon Choi <devjiwonchoi@gmail.com>
parent a7faeb0b
......@@ -149,7 +149,7 @@ export const fetchCache = 'auto'
- Any options set across each layout and page of a single route need to be compatible with each other.
- If both the `'only-cache'` and `'force-cache'` are provided, then `'force-cache'` wins. If both `'only-no-store'` and `'force-no-store'` are provided, then `'force-no-store'` wins. The force option changes the behavior across the route so a single segment with `'force-*'` would prevent any errors caused by `'only-*'`.
- The intention of the `'only-*'` and `force-*'` options is to guarantee the whole route is either fully static or fully dynamic. This means:
- The intention of the `'only-*'` and `'force-*'` options is to guarantee the whole route is either fully static or fully dynamic. This means:
- A combination of `'only-cache'` and `'only-no-store'` in a single route is not allowed.
- A combination of `'force-cache'` and `'force-no-store'` in a single route is not allowed.
- A parent cannot provide `'default-no-store'` if a child provides `'auto'` or `'*-cache'` since that could make the same fetch have different behavior.
......
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