Merge branch 'main' into new-blog-react-19

content/blog/a-quick-glance-at-the-react-19-beta-feature-set.mdx

@@ -18,8 +18,7 @@ slug: 'a-quick-glance-at-the-react-19-beta-feature-set'
 - The use function - new API to read resources in render. Which is named like a hook but doesn't have the same conditional code issue is there, you can give it promises or contexts.
 _Confusing at first glance, maybe it'll settle over time._
 - Server components and actions continue to be a thing
-- Goodbye `forwardRef`, just use ref directly in props now as the second param.
-- Goodbye `Context.Provider`, you just use `<Context>` as the provider now
+- Goodbye `forwardRef`, just use ref directly in props now as the second param. - Goodbye `Context.Provider`, you just use `<Context>` as the provider now
 - `ref` callbacks get a cleanup callback like effects
 - Goodbye `react-helmet` - React now handles HTML metadata and hoists it into the head from any component
 - Stylesheet links and `<style>` tags now available - _How was this not a thing before? 🤯_
@@ -30,13 +29,13 @@ _Confusing at first glance, maybe it'll settle over time._
 
 _**Insight:** A common misunderstanding is that Server Components are denoted by "use server", but there is no directive for Server Components. The "use server" directive is used for Server Actions._
 
-I think this was an easy misunderstanding to make so I'm glad for the clarification.
+I think this was an easy misunderstanding to make, so I'm glad for the clarification.
 
-This is a pretty exciting release given the last significant release from React was March 29, 2022. The wheels are moving again!
+This is a pretty exciting release, given the last significant release from React was March 29, 2022. The wheels are moving again!
 
 React continues to evolve and solve a combination of new problems while fixing some of the pain points with nice quality of life improvements.
 
 I do get the feeling that with the introduction of Server Components, the mental model of React now becomes dynamic and more complicated
 depending on your use case, maybe that will prove out in time as frameworks adopt it and provide opinionated workflows around it.
 
-I'm keeping an eye on the other frameworks/libraries maturing in the space like Svelte, SolidJS, Vue, AlpineJS to see how the new React features measure up and I might be back with a comparison post in the future.
+I'm keeping an eye on the other frameworks/libraries maturing in the space like Svelte, SolidJS, Vue, AlpineJS to see how the new React features measure up, and I might be back with a comparison post in the future.