[website][docs] Resolve broken links reported by docs:link-check

docs/.link-check-errors.txt

@@ -1,5 +1,2 @@
 Broken links found by `pnpm docs:link-check` that exist:
 
-- https://mui.com/blog/material-ui-v4-is-out/#premium-themes-store-✨
-- https://mui.com/material-ui/discover-more/roadmap/#priorities
-- https://mui.com/size-snapshot/

docs/data/material/components/autocomplete/autocomplete.md

@@ -172,8 +172,6 @@ The `useAutocomplete` hook is also reexported from @mui/material for convenience
 import useAutocomplete from '@mui/material/useAutocomplete';
 ```
 
-- 📦 [4.5 kB gzipped](/size-snapshot/).
-
 {{"demo": "UseAutocomplete.js", "defaultCodeOpen": false}}
 
 ### Customized hook

docs/data/material/components/popper/popper.md

@@ -14,7 +14,6 @@ Some important features of the `Popper` component:
 
 - 🕷 Popper relies on the 3rd party library ([Popper.js](https://popper.js.org/)) for perfect positioning.
 - 💄 It's an alternative API to react-popper. It aims for simplicity.
-- 📦 [24.9 kB gzipped](/size-snapshot/).
 - The children is [`Portal`](/material-ui/react-portal/) to the body of the document to avoid rendering problems.
   You can disable this behavior with `disablePortal`.
 - The scroll isn't blocked like with the [`Popover`](/material-ui/react-popover/) component.

docs/data/material/components/use-media-query/use-media-query.md

@@ -12,7 +12,6 @@ Some of the key features:
 
 - ⚛️ It has an idiomatic React API.
 - 🚀 It's performant, it observes the document to detect when its media queries change, instead of polling the values periodically.
-- 📦 [1 kB gzipped](/size-snapshot/).
 - 🤖 It supports server-side rendering.
 
 {{"component": "modules/components/ComponentLinkHeader.js", "design": false}}

docs/data/material/guides/minimizing-bundle-size/minimizing-bundle-size.md

@@ -5,7 +5,7 @@
 ## Bundle size matters
 
 Material UI's maintainers take bundle size very seriously. Size snapshots are taken
-on every commit for every package and critical parts of those packages ([view the latest snapshot](/size-snapshot/)).
+on every commit for every package and critical parts of those packages.
 Combined with [dangerJS](https://danger.systems/js/) we can inspect
 [detailed bundle size changes](https://github.com/mui/material-ui/pull/14638#issuecomment-466658459) on every Pull Request.
 

docs/pages/blog/material-ui-v4-is-out.md

@@ -22,15 +22,15 @@ Material UI v4 has finally arrived. We are so excited about this release, as it
 - [High-level goals for v4](#high-level-goals-for-v4)
 - [What's new?](#whats-new)
 - [What's next?](#whats-next)
-- [Premium themes store](#premium-themes-store-✨)
+- [Premium theme store](#premium-theme-store)
 
 ## High-level goals for v4
 
 Material UI v1 was [released](https://medium.com/material-ui/material-ui-v1-is-out-e73ce13463eb) one year ago. Version 4 is our most important major release since then. For those unfamiliar with the history of the project, we didn't release a v2, and v3 only introduced a slight browsers support change.
 
 This release happens within our [fixed frequency](https://mui.com/versions/#release-frequency) release strategy. We try to release a major at least every 12 months and at most every 6 months. The migration from v0 to v1 was painful, it almost felt like using two different UI libraries. We've done our best to minimize the time needed to migrate from v3 to v4. To help ease the transition, you can follow this [migration guide](/material-ui/migration/migration-v3/) 📚. It shouldn't take more than a few hours.
 
-This release is influenced by two major factors. First, following the Developer Survey we ran in March, we have [analyzed the results](/blog/2019-developer-survey-results/) and used them to change [our priorities](/material-ui/discover-more/roadmap/#priorities) for the coming year. Secondly, we needed to be up to date with the latest best practices in the React community and with the Material Design Specification.
+This release is influenced by two major factors. First, following the Developer Survey we ran in March, we have [analyzed the results](/blog/2019-developer-survey-results/) and used them to change [our priorities](/material-ui/discover-more/roadmap/) for the coming year. Secondly, we needed to be up to date with the latest best practices in the React community and with the Material Design Specification.
 
 ### Customization
 
@@ -314,11 +314,11 @@ import { Button } from '@mui/material';
   Developers should be able to use their preferred styling solution without paying the cost of two CSS-in-JS runtimes.
 - **Accessibility.** While we try to fix all accessibility issues as they are reported by our users, we feel that we can do better. We want to run a professional ADA audit of all our components ♿️.
 
-## Premium themes store ✨
+## Premium theme store
 
 How are we going to sustain this ambitious roadmap?
 We will follow the Bootstrap model.
-We are working on [a Premium themes store](https://mui.com/store/).
+We are working on [a Premium theme store](https://mui.com/store/).
 
 We have built partnerships with the best theme authors of the ecosystem.
 Within a few weeks, you should find a collection of the best Material UI templates and themes 😍.

docs/pages/blog/mui-core-v5.md

@@ -687,7 +687,7 @@ Some statistics with the released of v5.0.0 compared to the one of v4.0.0:
 - From 2M downloads/month to 9.5M downloads/month on npm
 - From 350k users/month to 700k users/month on the documentation
 
-We're also proud to share that the monetization initiatives we started right after the release of v4, such as [the store](/blog/material-ui-v4-is-out/#premium-themes-store-✨), are working. We incorporated the company two years ago, have grown 2-3X per year since, and we're now over 10 people, with a positive cash flow 🚀. We are on track to reach 16 people by December 2021.
+We're also proud to share that the monetization initiatives we started right after the release of v4, such as [the store](/blog/material-ui-v4-is-out/#premium-theme-store), are working. We incorporated the company two years ago, have grown 2-3X per year since, and we're now over 10 people, with a positive cash flow 🚀. We are on track to reach 16 people by December 2021.
 [We're hiring](/careers/) to grow our existing products, but also to explore a bold new product vertical, aligned with our mission.
 
 We couldn't be more grateful for the trust that the React community puts in us.