From b7d16563d8416907561cf30c565e9183a2fd7d92 Mon Sep 17 00:00:00 2001 From: Oscar <33732524+oscarvz@users.noreply.github.com> Date: Fri, 3 May 2024 22:35:42 +0200 Subject: [PATCH] Improve nodes description in React integrations docs (#8038) Co-authored-by: Yan <61414485+yanthomasdev@users.noreply.github.com> Co-authored-by: Sarah Rainsberger --- src/content/docs/en/guides/integrations-guide/react.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/en/guides/integrations-guide/react.mdx b/src/content/docs/en/guides/integrations-guide/react.mdx index 2ad77e5aaa66e..9c238d861b3be 100644 --- a/src/content/docs/en/guides/integrations-guide/react.mdx +++ b/src/content/docs/en/guides/integrations-guide/react.mdx @@ -152,7 +152,7 @@ import ReactComponent from './ReactComponent'; If you are using a library that *expects* more than one child element to be passed, for example so that it can slot certain elements in different places, you might find this to be a blocker. -You can set the experimental flag `experimentalReactChildren` to tell Astro to always pass children to React as React vnodes. There is some runtime cost to this, but it can help with compatibility. +You can set the experimental flag `experimentalReactChildren` to tell Astro to always pass children to React as React virtual DOM nodes. There is some runtime cost to this, but it can help with compatibility. You can enable this option in the configuration for the React integration: