diff --git a/docs/content/2.guide/1.concepts/3.rendering.md b/docs/content/2.guide/1.concepts/3.rendering.md
index b1f79e4885..f047b91e9f 100644
--- a/docs/content/2.guide/1.concepts/3.rendering.md
+++ b/docs/content/2.guide/1.concepts/3.rendering.md
@@ -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