polish 2

docs/pages/blog/2019.md

@@ -18,7 +18,7 @@ It's only with your trust that we could achieve the following outcomes in 2019.
 - ⭐️ From 43.1k to 53.3k stars, leave us [yours 🌟](https://github.com/mui-org/material-ui).
 - 👨‍👩‍👧‍👦 From 1,064 to [1,581](https://github.com/mui-org/material-ui/graphs/contributors) contributors.
 - 💰 Grew financial support by 1.76X in 2019, compared to 2018.
-- 🏢 From 1.5 to 3 full-time equivalent developers, spread among multiple financially supported [core team members](https://mui.com/about/).
+- 🏢 From 1.5 to 3 full-time equivalent developers, spread among multiple financially supported [core team members](/about/).
 
 The numbers speak for themselves. 2019 was super exciting and made MUI one of the most advanced open-source, React-based, UI component libraries!
 

docs/pages/blog/2020.md

@@ -18,7 +18,7 @@ It's only with your trust that we could achieve the following outcomes in 2020.
 - ⭐️ From 53.3k to 63.8k stars, leave us [yours 🌟](https://github.com/mui-org/material-ui).
 - 👨‍👩‍👧‍👦 From 1,581 to [2,052](https://github.com/mui-org/material-ui/graphs/contributors) contributors.
 - 💰 Grew financial support by 2.1X in 2020, compared to 2019.
-- 🏢 From 3 to 6 full-time equivalent developers, spread among multiple financially supported [core team members](https://mui.com/about/).
+- 🏢 From 3 to 6 full-time equivalent developers, spread among multiple financially supported [core team members](/about/).
 
 The numbers speak for themselves. We have reproduced the [traction we got in 2019](/blog/2019/#growth).
 

docs/pages/blog/2021.md

@@ -11,7 +11,8 @@ card: true
 Happy New Year from MUI!
 
 2021 has been another amazing year, not only for MUI but also for the React ecosystem and our users.
-The digitalization of the economy is accelerating, pushed by COVID-19. Developers and designers have been, more than ever, busy creating apps.
+The digitalization of the economy is accelerating, pushed by COVID-19.
+Developers and designers have been, more than ever, busy creating apps.
 
 We spent our year making it faster and easier for you to build great UIs and to delight your users with amazing UI experiences.
 Thank you for being part of this journey!
@@ -25,13 +26,14 @@ It's only with your trust that we could achieve the following outcomes in 2021.
 - ⭐️ From 63.8 to 74.0k stars, leave us [yours 🌟](https://github.com/mui-org/material-ui).
 - 👨‍👩‍👧‍👦 From 2,052 to [2,396](https://github.com/mui-org/material-ui/graphs/contributors) contributors.
 - 💰 Grew financial support by 2.9X in 2021, compared to 2020.
-- 🏢 From 6 to 14 full-time equivalent [team members](https://mui.com/about/).
+- 🏢 From 6 to 14 full-time equivalent [team members](/about/).
 
 The numbers speak for themselves. We have reproduced the [traction we got in 2020](/blog/2020/#growth).
 
 ## In review
 
-When we started 2021, we had recently released the first version of the MUI X Pro plan and were in the middle of the release of MUI v5. We had committed ourselves to fully execute these two major efforts:
+When we started 2021, we had recently released the first version of the MUI X data grid and were in the middle of the release of MUI v5.
+We had committed ourselves to fully execute these two major efforts:
 
 - On MUI Core, major releases have historically been efforts that span over a dozen months.
   v5 was no different as great work takes time.
@@ -40,23 +42,26 @@ When we started 2021, we had recently released the first version of the MUI X Pr
   With a large code and user base like MUI has, we knew it would take time.
   For example, we might have had migrated a few components to the new style engine and fix all the issues that we could find, going to production is unforgiving.
   Developers tend to surface all the cases that are overlooked in the first iteration with GitHub issues.
-- On MUI X, we had successfully sold our first Pro plan licenses.
+- On MUI X, we had successfully sold our first Pro plan licenses and reached 100k downloads/month on the MIT version.
   We had early signs from the community of a market fit for the product and that the open core model was the right one to execute our mission.
   We were determined to solely focus on the data grid component, and demonstrate that our model was viable to build the best React data grid in the space.
 
 What might have been the biggest change in 2021 is the implications of a larger team for the organization structure.
 We have reached an inflection point at around 10 people.
-Me looking at all the GitHub issues and PRs was no longer doable.
-At that point, it was requiring >70h/week to do it correctly, which was no scaling to grow the team, and more importantly, it was preventing me to focus on my core CEO responsibilities (people, vision, funding).
-We had to introduce our first layers of management and define more clearly the responsibilities of each role.
+I could no longer look at all the GitHub issues and PRs.
+At that point, it was requiring >70h/week to do it correctly.
+One individual continuing doing it was not scaling.
+It would prevent growing the team, and more importantly, distract me off the core CEO responsibilities (people, vision, funding).
+So we have broken down the responsibilities
+We have introduced our first layers of management and defined more clearly the purpose of each role.
 
 ## Achievements
 
 We have achieved most of what we could have hoped for.
 
 ### Company
 
-- The most important, we have welcomed 10 members in the company: Matheus, Michał, Jun, Danilo, Flavien, Benny, Alexandre, Jan, Bharat, Prakhar.
+- The most important, we have welcomed 10 [members](/about/) in the company: Matheus, Michał, Jun, Danilo, Flavien, Benny, Alexandre, Jan, Bharat, Prakhar.
 - We have introduced a [public handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b) on how we run the company.
   For example, we are using the OKRs work methodology to prioritize our efforts.
 - We held our first company [retreat](/blog/2021-q3-update/#retreat) 🏝 in Lisbon, Portugal 🇵🇹 , for members of the team that were not prevented by COVID-19 related travel restrictions, and who felt safe enough to travel.
@@ -108,7 +113,7 @@ Here is a breakdown of our [roadmap](/discover-more/roadmap/).
 ### MUI Core
 
 The release of v5 has introduced a significant API churn in the community.
-While our [versioning frequency](/versions/#release-frequency) aims for one major per year, we hope we can iterate on v5 during the whole year of 2022 with any breaking changes, e.g. taking full advantage of the new style engine.
+While our [versioning frequency](/versions/#release-frequency) aims for one major per year, we hope we can iterate on v5 during the whole year of 2022 without any breaking changes, e.g. taking full advantage of the new style engine.
 
 #### MUI Base
 
@@ -118,20 +123,24 @@ We still have work to do to have a full set of unstyled components.
 
 You can read more about them in [the docs](/customization/unstyled-components/) and keep track of our progress in [#27170](https://github.com/mui-org/material-ui/issues/27170).
 
-Our high-level plan is to use the unstyled components and hooks as the basis of the Material components and second design system.
+Our high-level plan is to use the unstyled components and hooks as the basis of the Material Design components and our second design system.
 
 #### MUI System
 
-There a number of improvements that we can bring to the system (the npm package `@mui/system` used to create the styled components). Hopefully, we will bring native support for CSS variables and improve performance.
+There a number of improvements that we can bring to the system (the npm package `@mui/system` used to create the styled components).
+Hopefully, we will bring native support for CSS variables, improve DX, and improve performance.
 
 #### MUI Material
 
-Google is rolling out [Material Design 3](https://m3.material.io/), we have to determine how to respond to it. Should we implement it later on for v6? Should we ignore it? Should we implement Google's UI that looks cleaner instead?
+Google is rolling out [Material Design 3](https://m3.material.io/), we have to determine how to respond to it.
+Should we implement it later on for v6? Should we ignore it? Should we implement Google's UI that looks cleaner instead?
 In the meantime, we will keep improving the components, increasingly relying on `@mui/base`.
 
 #### MUI Joy
 
-We will continue [in the direction of 2021](/blog/2020/#a-second-theme). While Material Design is a predominant design choice for building rich client-side applications, it's not the only popular design trend. We plan to provide a [second design system](https://github.com/mui-org/material-ui/issues/22485) to expand the range of use cases for MUI, striking a balance between:
+We will continue [in the direction of 2021](/blog/2020/#a-second-theme).
+While Material Design is a predominant design choice for building rich client-side applications, it's not the only popular design trend.
+We plan to provide a [second design system](https://github.com/mui-org/material-ui/issues/22485) to expand the range of use cases for MUI, striking a balance between:
 
 - alignment with the best-looking design trends of hot startups in the US.
 - optimization of its usage for rich client-side applications while keeping it good enough for landing pages.
@@ -142,13 +151,19 @@ It will be built on top of the unstyled components: MUI Base and our styling lib
 
 ### MUI X
 
-This new product initiative is working, it's time to scale it by growing the team and the scope.
-We will keep the data grid as our primary effort, there are still [many features left to be built 🚧](https://mui.com/components/data-grid/getting-started/#feature-comparison) to get closer to the alternatives.
+The data grid product initiative is working, it's time to scale it by growing the team and the product scope.
+We will keep the data grid as our primary effort, there are still [many features left to be built 🚧](/components/data-grid/getting-started/#feature-comparison) to get closer to the alternatives.
 However, we will also expand the scope to the date picker components, resuming work on it.
 
 ### Low-code
 
-TODO
+Pro-code (writing code in a regular programming language) has been an incredibly effective way to deliver on our mission so far.
+The two main benefits reported by developers in our 2021 survey for using MUI are "moving faster" and "ease of use".
+However, the data points we can find suggest that the demand for developers in the next 5-10 years is growing a lot faster than the growth of the workforce.
+The importance of these two benefits is only going to increase, it's critical for MUI to keep pushing the envelope of what development speed and ease of use look like for developers.
+
+Entering low-code, we have a small team that will keep exploring in 2022 how MUI can empower developers and knowledge workers to build apps more visually, x10 faster, with no advanced SQL or JavaScript knowledge.
+The goal is to write fewer lines of code, while still empowering developers to extend it with custom logic.
 
 ### Scale
 
@@ -157,7 +172,7 @@ The primary purpose will be to strengthen all the efforts that we have started,
 
 At a high level we are guided by the following rock beliefs:
 
-- React dominance in the UI development landscape will increase and stay for a very long time.
+- React dominance in the UI development landscape will continue to increase in the next 5 years.
 - Developers will always be looking to build faster, more appealing UIs, and with less specific knowledge.
 - Low-code will progressively become mainstream for professional developers and knowledge workers.