From aa9937f330f43fecda5bd60bdb0b18b05602da97 Mon Sep 17 00:00:00 2001 From: Christian Martinez <36577457+christianbmartinez@users.noreply.github.com> Date: Thu, 25 Apr 2024 23:09:12 -0600 Subject: [PATCH] Fixed /blog/2024/04/25/react-19.md typo Updated "feature" to "features" as this sentence was presumably intended to be plural by the original author. --- src/content/blog/2024/04/25/react-19.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/blog/2024/04/25/react-19.md b/src/content/blog/2024/04/25/react-19.md index 21784ca2135..f4d08b72c2d 100644 --- a/src/content/blog/2024/04/25/react-19.md +++ b/src/content/blog/2024/04/25/react-19.md @@ -553,7 +553,7 @@ When React renders this component, it will see the `` `<link>` and `<meta #### You may still want a Metadata library {/*you-may-still-want-a-metadata-library*/} -For simple use cases rendering Document Metadata as tags may be suitable, but libraries can offer more powerful features like overriding generic metadata with specific metadata based on the current route. So these feature make it easier for frameworks and libraries like [`react-helmet`](https://github.com/nfl/react-helmet) to support metadata tags, rather than replace them. +For simple use cases rendering Document Metadata as tags may be suitable, but libraries can offer more powerful features like overriding generic metadata with specific metadata based on the current route. So these features make it easier for frameworks and libraries like [`react-helmet`](https://github.com/nfl/react-helmet) to support metadata tags, rather than replace them. </Note>