Matt's review

docs/pages/blog/base-ui-2024-plans.md

@@ -9,7 +9,7 @@ card: true
 
 The [story of Base UI](/blog/introducing-base-ui/) began several years ago—long before headless React component libraries skyrocketed in popularity—when we started to imagine a world in which Material UI could exist without Material Design.
 
-We're super excited to share that this dream has become a reality!
+We're super excited to share that this dream is becoming a reality!
 This year will see a lot of investment in Base UI as we expand the team ([we're hiring!](/careers/staff-ui-engineer-base-ui/)) and focus hard on a [stable release](https://github.com/mui/material-ui/milestone/46) (tentatively planned for late 2024), which will come full of new components, features, and improvements.
 
 Let's walk through some of the things we're cooking up.
@@ -55,7 +55,8 @@ Additionally, since the `slots` and the corresponding `slotProps` are not relate
 
 To address these issues, we're considering adopting a new API that would assign a discrete subcomponent to each DOM node—the pattern favored by many other headless component libraries (think: `<Slider.Track />`, `<Slider.Thumb />`, etc.).
 This pattern has the potential to radically improve the customization experience, both for styles and structure.
-We're still fleshing out the details and plan to release an RFC on GitHub in the coming days—we'll update this blog post with the link when it's available.
+We're still fleshing out the details and plan to release an RFC on GitHub in the coming days.
+We'll update this blog post with the link when it's available.
 We know that a significant number of projects depend on the existing API, and we want to assure you that one of our top priorities is to provide a smooth migration experience.
 
 ## More thorough animation support
@@ -68,21 +69,12 @@ They're currently available for use with the Popup, Menu, and Select, and the pl
 
 <p class="blog-description" style="margin: -16px 0 0 0;">The CSS Animation transition is exaggerated here for the sake of demonstration.</p>
 
-## Independent component versioning
-
-Instead of versioning the package as a whole, we're considering offering each Base UI component as its own individual npm package with its own version.
-Although it may initially sound like a burden to install each component individually, it means that you only have to commit to those you're actually interested in using.
-Pick and choose only what you need, or even mix and match with complementary component libraries that you're already using.
-
-This would be a huge DX win because it enables us to iterate much more quickly on individual components and get bug fixes out to you on a per-component basis with no need to wait for a package-wide major release.
-
 ## A more independent product
 
-Thus far, all Base UI-related development has happened within the [Material UI GitHub repository](http://github.com/mui/material-ui).
+So far, all Base UI-related development has happened within the [Material UI GitHub repository](http://github.com/mui/material-ui).
 That made a lot of sense in the beginning because we didn't intend for Base UI to be a standalone product at the time.
 As a result of this early decision, we've seen that some developers are hesitant to try it out because of the apparent association with Material Design.
 Rest assured that Base UI _is_ a standalone library, and it doesn't come packaged with _any_ default styles or themes.
-That's why, later in the year, we plan to move it to its own dedicated GitHub repository.
 
 <img alt="Material UI vs. Base UI: independent but related products." src="/static/blog/base-ui-2024-plans/material-vs-base.png" width="1200" height="450" loading="lazy" />
 
@@ -92,15 +84,15 @@ To acknowledge that Base UI has the potential to outgrow Material UI, we plan to
 ## Getting bugs out of the way
 
 The core of what Base UI strives to deliver out of the box is first-class accessibility and an intuitive API for extensive customization.
-We've earmarked several bugs we want to tackle before the stable release in areas such as keyboard navigation, better ARIA support, focus styles, and more.
+We've earmarked several issues we want to tackle before the stable release in areas such as keyboard navigation, better ARIA support, focus styles, and more.
 
 <img alt="A screenshot of the Base UI stable release milestone on GitHub as of January 2024." src="/static/blog/base-ui-2024-plans/base-ui-milestone.png" width="1200" height="600" loading="lazy" />
 
-You can track our progress fixing any specific bugs by checking out the list of [Base UI stable release milestones on GitHub](https://github.com/mui/material-ui/milestone/46).
+You can track our progress fixing any specific issues by checking out the list of [Base UI stable release milestones on GitHub](https://github.com/mui/material-ui/milestone/46).
 
 ## Join us on the ride
 
-If you're passionate about the mission of extending the web platform with powerful, accessible, unstyled components, [we're hiring UI Engineers](/careers/staff-ui-engineer-base-ui/) to work on the Base UI team and help us accelerate its growth.
+If you're passionate about extending the web platform with powerful, accessible, unstyled components, [we're hiring UI Engineers](/careers/staff-ui-engineer-base-ui/) to work on the Base UI team and help us accelerate its growth.
 
 Lastly, we'd love to hear your feedback.
 The best place to share your ideas and requests is in [the GitHub repo](https://github.com/mui/material-ui/issues?q=is:open+is:issue+label:%22package:+base-ui%22).