Unverified Commit 4e055447 authored by Lee Robinson's avatar Lee Robinson Committed by GitHub

docs: small updates for canary docs (#71317)

- Rework bullet points from blog post
- Fix relative links mentioning Notion from copy/pasta
- Move the unstable APIs to the bottom of the list
parent b3d9b15d
...@@ -880,8 +880,8 @@ and should be treated with the same security assumptions and authorization check ...@@ -880,8 +880,8 @@ and should be treated with the same security assumptions and authorization check
To improve security, Next.js has the following built-in features: To improve security, Next.js has the following built-in features:
- **Dead code elimination:** Unused Server Actions won’t have their IDs exposed to the client-side JavaScript bundle, reducing bundle size and improving performance. - **Secure action IDs:** Next.js creates unguessable, non-deterministic IDs to allow the client to reference and call the Server Action. These IDs are periodically recalculated between builds for enhanced security.
- **Secure action IDs:** Next.js creates unguessable, non-deterministic IDs to allow the client to reference and call the Server Action. These IDs are periodically recalculated for enhanced security. - **Dead code elimination:** Unused Server Actions (referenced by their IDs) are automatically removed.
```jsx ```jsx
// app/actions.js // app/actions.js
......
...@@ -99,13 +99,13 @@ As a developer, you do not need to choose between static and dynamic rendering a ...@@ -99,13 +99,13 @@ As a developer, you do not need to choose between static and dynamic rendering a
Dynamic APIs rely on information that can only be known at request time (and not ahead of time during prerendering). Using any of these APIs signals the developer's intention and will opt the whole route into dynamic rendering at the request time. These APIs include: Dynamic APIs rely on information that can only be known at request time (and not ahead of time during prerendering). Using any of these APIs signals the developer's intention and will opt the whole route into dynamic rendering at the request time. These APIs include:
- [`cookies`](https://www.notion.so/docs/app/api-reference/functions/cookies) - [`cookies`](/docs/app/api-reference/functions/cookies)
- [`headers`](https://www.notion.so/docs/app/api-reference/functions/headers) - [`headers`](/docs/app/api-reference/functions/headers)
- [`unstable_noStore`](https://www.notion.so/docs/app/api-reference/functions/unstable_noStore) - [`connection`](/docs/app/api-reference/functions/connection)
- [`unstable_after`](https://www.notion.so/docs/app/api-reference/functions/unstable_after) - [`draftMode`](/docs/app/api-reference/functions/draft-mode)
- [`connection`](https://www.notion.so/docs/app/api-reference/functions/connection) - [`searchParams` prop](/docs/app/api-reference/file-conventions/page#searchparams-optional)
- [`draftMode`](https://www.notion.so/docs/app/api-reference/functions/draft-mode) - [`unstable_noStore`](/docs/app/api-reference/functions/unstable_noStore)
- [`searchParams` prop](https://www.notion.so/docs/app/api-reference/file-conventions/page#searchparams-optional) - [`unstable_after`](/docs/app/api-reference/functions/unstable_after)
### Streaming ### Streaming
......
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