From 5cb4e41553ffe066bf1acf9ca24934936179c6a2 Mon Sep 17 00:00:00 2001 From: Michael Brevard Date: Wed, 19 Jun 2024 12:08:39 +0300 Subject: [PATCH] docs: rephrase --- docs/2.guide/2.directory-structure/1.components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/2.guide/2.directory-structure/1.components.md b/docs/2.guide/2.directory-structure/1.components.md index 696b90be5d..119bd1155c 100644 --- a/docs/2.guide/2.directory-structure/1.components.md +++ b/docs/2.guide/2.directory-structure/1.components.md @@ -123,7 +123,7 @@ const show = ref(false) In real world applications, some pages may include a lot of content and a lot of components, and most of the time not all of them need to be interactive as soon as the page is loaded. Having them all load eagerly can negatively impact performance and increase bundle size. -In order to optimize the page, you may want to delay the hydration of some components until they're visible, or until the browser is done with more important tasks for example. Nuxt has first class support for delayed hydration components and can help you reduce your boilerplate along the way. +In order to optimize the page, you may want to delay the hydration of some components until they're visible, or until the browser is done with more important tasks for example. Nuxt has first class support for delayed hydration components without having to write all of the boilerplate. In order to use delayed hydration, you first need to enable it in your experimental config in `nuxt.config`