[docs] Fix 301 link

Author: oliviertassinari

docs/data/base/components/modal/modal.md

@@ -168,7 +168,7 @@ Do not add the `ref` parameter to the root element manually, as the correct ref
 
 See the [WAI-ARIA guide on the Dialog (Modal) pattern](https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/) for complete details on accessibility best practices.
 
-- All interactive elements must have an [accessible name](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-labelledby). Use the `aria-labelledby="id..."` to give your Modal component an accessible name.
+- All interactive elements must have an [accessible name](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-labelledby). Use the `aria-labelledby="id..."` to give your Modal component an accessible name.
   You can also use `aria-describedby="id..."` to provide a description of the Modal:
 
   ```jsx

docs/data/base/getting-started/quickstart/quickstart.md

@@ -41,7 +41,7 @@ Please note that [react](https://www.npmjs.com/package/react) and [react-dom](ht
 
 ## Implementing a Button
 
-This is a quick tutorial that goes through the basics of using and styling MUI Base components by replicating a button from GitHub's UI, using their [Primer design system](https://primer.style/components/button/) as a reference.
+This is a quick tutorial that goes through the basics of using and styling MUI Base components by replicating a button from GitHub's UI, using their [Primer design system](https://primer.style/product/components/button/) as a reference.
 
 {{"demo": "Tutorial.js", "defaultCodeOpen": false, "hideToolbar": true}}
 

docs/data/joy/components/button/button.md

@@ -138,7 +138,7 @@ You can use these to customize the components with both the `sx` prop and the th
 
 ## Accessibility
 
-All Buttons must have a meaningful [`aria-label`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-label) so their purpose can be understood by users who require assistive technology.
+All Buttons must have a meaningful [`aria-label`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-label) so their purpose can be understood by users who require assistive technology.
 
 This is especially important for [Icon Buttons](#icon-button) because they don't contain any text.
 For example, an Icon Button that displays a `<FavoriteBorder />` icon might have a label that looks like this:

docs/data/joy/components/link/link.md

@@ -127,7 +127,7 @@ import Link from '@mui/joy/Link';
 
 ### React Router
 
-Here is a demo with the [Link component](https://reactrouter.com/start/library/navigating#link) of [React Router](https://github.com/remix-run/react-router).
+Here is a demo with the [Link component](https://reactrouter.com/start/declarative/navigating#link) of [React Router](https://github.com/remix-run/react-router).
 
 ```js
 import { Link as RouterLink } from 'react-router';

docs/data/joy/components/modal/modal.md

@@ -237,7 +237,7 @@ If the user needs to interact with another part of the page－for example, to in
 
 See the [WAI-ARIA guide on the Dialog (Modal) pattern](https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/) for complete details on accessibility best practices. Here are a couple of highlights:
 
-- All interactive elements must have an [accessible name](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-labelledby). Use the `aria-labelledby="id..."` to give your `Modal` component an accessible name.
+- All interactive elements must have an [accessible name](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-labelledby). Use the `aria-labelledby="id..."` to give your `Modal` component an accessible name.
   You can also use `aria-describedby="id..."` to provide a description of the `Modal`:
 
   ```jsx

docs/data/material/guides/content-security-policy/content-security-policy.md

@@ -14,7 +14,7 @@ CSP mitigates cross-site scripting (XSS) attacks by requiring developers to whit
 
 This vulnerability would allow the attacker to execute anything. However, with a secure CSP header, the browser will not load this script.
 
-You can read more about CSP on the [MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP).
+You can read more about CSP on the [MDN Web Docs](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP).
 
 ## How does one implement CSP?
 

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

@@ -13,7 +13,7 @@ Combined with [dangerJS](https://danger.systems/js/) we can inspect
 
 Tree-shaking Material UI works out of the box in modern frameworks.
 Material UI exposes its full API on the top-level `@mui` imports.
-If you're using ES6 modules and a bundler that supports tree-shaking ([`webpack` >= 2.x](https://webpack.js.org/guides/tree-shaking/), [`parcel` with a flag](https://en.parceljs.org/cli.html#enable-experimental-scope-hoisting/tree-shaking-support)) you can safely use named imports and still get an optimized bundle size automatically:
+If you're using ES modules and a bundler that supports tree-shaking ([`webpack` >= 2.x](https://webpack.js.org/guides/tree-shaking/), parcel you can safely use named imports and still get an optimized bundle size automatically:
 
 ```js
 import { Button, TextField } from '@mui/material';

docs/data/material/integrations/routing/routing.md

@@ -67,7 +67,7 @@ You can learn more about this prop in the **[composition guide](/material-ui/gui
 
 ## React Router examples
 
-Here are a few demos with the [Link component](https://reactrouter.com/start/library/navigating#link) of [React Router](https://github.com/remix-run/react-router).
+Here are a few demos with the [Link component](https://reactrouter.com/start/declarative/navigating#link) of [React Router](https://github.com/remix-run/react-router).
 You can apply the same strategy with all the components: BottomNavigation, Card, etc.
 
 ### Link

docs/data/system/getting-started/the-sx-prop/the-sx-prop.md

@@ -309,7 +309,7 @@ For highly dynamic CSS values, we recommend using inline CSS variables instead o
 This approach avoids inserting unnecessary `style` tags into the DOM, which prevents potential performance issues when dealing with CSS properties that can hold a wide range of values that change frequently—for example, a color picker with live preview.
 
 :::info
-If you're having problems with your Content Security Policy while using inline styles with the `style` attribute, make sure you've enabled the [`style-src-attr` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/style-src-attr).
+If you're having problems with your Content Security Policy while using inline styles with the `style` attribute, make sure you've enabled the [`style-src-attr` directive](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/style-src-attr).
 Visit the [Content Security Policy guide](/material-ui/guides/content-security-policy/) for configuration details.
 :::
 

docs/translations/api-docs-joy/svg-icon/svg-icon.json

@@ -16,7 +16,7 @@
       "description": "If <code>true</code>, the root node will inherit the custom <code>component</code>&#39;s viewBox and the <code>viewBox</code> prop will be ignored. Useful when you want to reference a custom <code>component</code> and have <code>SvgIcon</code> pass that <code>component</code>&#39;s viewBox to the root node."
     },
     "shapeRendering": {
-      "description": "The shape-rendering attribute. The behavior of the different options is described on the <a href=\"https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/shape-rendering\">MDN Web Docs</a>. If you are having issues with blurry icons you should investigate this prop."
+      "description": "The shape-rendering attribute. The behavior of the different options is described on the <a href=\"https://developer.mozilla.org/en-US/docs/Web/SVG/Reference/Attribute/shape-rendering\">MDN Web Docs</a>. If you are having issues with blurry icons you should investigate this prop."
     },
     "size": { "description": "The size of the component." },
     "slotProps": { "description": "The props used for each slot inside." },