From 6b41a07a8a550f494b0d5585781a426f00c26fba Mon Sep 17 00:00:00 2001
From: Alexander Harding <noreply@harding.dev>
Date: Tue, 19 Nov 2024 12:29:41 -0600
Subject: [PATCH] Update README

---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 0d49163..335f88b 100644
--- a/README.md
+++ b/README.md
@@ -125,7 +125,9 @@ const portalNode = portals.createHtmlPortalNode({
 });
 ```
 
-The div's DOM node is also available at `.element`, so you can mutate that directly with the standard DOM APIs if preferred.
+### `portals.createHtmlInlinePortalNode([options])`
+
+Same as `portal.createHtmlPortalNode`, except it uses `<span>` instead of `<div>`. This can be helpful to avoid invalid HTML when portalling videos, etc into [phrasing content](https://developer.mozilla.org/en-US/docs/Web/HTML/Content_categories#phrasing_content), which is invalid HTML markup and triggers [React validateDOMNesting](https://www.dhiwise.com/post/mastering-validatedomnesting-best-practices).
 
 ### `portals.createSvgPortalNode([options])`