Skip to content
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.

docs: add missing dot #5815

Merged
merged 1 commit into from
Jul 11, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Update 3.rendering.md
  • Loading branch information
valcosmos authored Jul 11, 2022
commit 08aa2a5cf2101dcf9dc09612a1fbb40b807ec14d
2 changes: 1 addition & 1 deletion docs/content/2.guide/1.concepts/3.rendering.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ Hybrid rendering allows different caching rules per route and decides how the Se

At the moment, every page (or **route**) of a Nuxt application must use the same rendering mode, client-side or universal. But in various cases, some pages could be generated at build time, while others should be client-side rendered. For example, think of a content website with an admin section. Every content page should be primarily static and generated once, but the admin section requires registration and behaves more like a dynamic application.

[Read the open RFC discussing implementation and gathering community feedback](https://github.com/nuxt/framework/discussions/560)
[Read the open RFC discussing implementation and gathering community feedback.](https://github.com/nuxt/framework/discussions/560)

### Rendering on CDN edge workers

Expand Down