Update about-the-lab.md

docs/src/pages/components/about-the-lab/about-the-lab.md

@@ -7,7 +7,7 @@ The main difference between the lab and the core is how the components are versi
 As developers use and test the components and report issues, the maintainers learn more about shortcomings of the components: missing features, accessibility issues, bugs, API design, etc. The older and more used a component is, the less likely it is that new issues will be found and subsequently need to introduce breaking changes.
 
 For a component to be ready to move to the core, the following criteria are considered:
-* It needs to be **used**. The Material UI team uses Google Analytics stats to evaluate the usage of each component. A lab component with low usage either means that it isn't fully working yet or that there is a low demand for it.
+* It needs to be **used**. The Material-UI team uses Google Analytics stats among other metrics to evaluate the usage of each component. A lab component with low usage either means that it isn't fully working yet or that there is a low demand for it.
 * It needs to match the **code quality** of the core components. It doesn't have to be perfect to be a part of the core, but the component should be reliable enough that developers can depend on it.
     * Each component needs **type definitions**. It is not currently required that a lab component is typed, but it would need to be typed to move to the core.
     * Requires good **test coverage**. Some of the lab components don't currently have comprehensive tests.