From 72aa3bf6641e68c1a08618157aa1d5a3fd9ad837 Mon Sep 17 00:00:00 2001
From: Olivier Tassinari <olivier.tassinari@gmail.com>
Date: Mon, 24 Apr 2023 23:18:35 +0200
Subject: [PATCH 1/2] [Doc] Fix reference to Material UI

---
 CHANGELOG.md                                  | 24 +++++++-------
 README.md                                     |  4 +--
 docs/Admin.md                                 | 10 +++---
 docs/AdvancedTutorials.md                     |  2 +-
 docs/AppBar.md                                | 16 +++++-----
 docs/Architecture.md                          |  8 ++---
 docs/Authentication.md                        |  4 +--
 docs/AutocompleteArrayInput.md                | 18 +++++------
 docs/AutocompleteInput.md                     | 16 +++++-----
 docs/BooleanField.md                          |  4 +--
 docs/BooleanInput.md                          |  6 ++--
 docs/Breadcrumb.md                            |  2 +-
 docs/Buttons.md                               | 20 ++++++------
 docs/CheckboxGroupInput.md                    | 10 +++---
 docs/ChipField.md                             | 10 +++---
 docs/Community.md                             |  2 +-
 docs/Confirm.md                               |  8 ++---
 docs/ContainerLayout.md                       | 10 +++---
 docs/Count.md                                 |  2 +-
 docs/Create.md                                | 10 +++---
 docs/CreateInDialogButton.md                  |  4 +--
 docs/Datagrid.md                              | 10 +++---
 docs/DateInput.md                             |  4 +--
 docs/DateTimeInput.md                         |  2 +-
 docs/DualListInput.md                         |  8 ++---
 docs/Edit.md                                  |  8 ++---
 docs/EditInDialogButton.md                    |  4 +--
 docs/EditTutorial.md                          |  4 +--
 docs/EmailField.md                            |  2 +-
 docs/FAQ.md                                   |  2 +-
 docs/Features.md                              | 14 ++++----
 docs/Fields.md                                |  4 +--
 docs/FileField.md                             |  4 +--
 docs/FileInput.md                             |  6 ++--
 docs/IconMenu.md                              | 10 +++---
 docs/ImageField.md                            |  4 +--
 docs/ImageInput.md                            |  4 +--
 docs/Inputs.md                                | 22 ++++++-------
 docs/Labeled.md                               |  6 ++--
 docs/Layout.md                                |  8 ++---
 docs/List.md                                  |  4 +--
 docs/ListTutorial.md                          |  6 ++--
 docs/LocalesMenuButton.md                     |  6 ++--
 docs/LongForm.md                              |  4 +--
 docs/Menu.md                                  |  8 ++---
 docs/MenuLive.md                              |  2 +-
 docs/MultiLevelMenu.md                        |  8 ++---
 docs/NullableBooleanInput.md                  |  6 ++--
 docs/RadioButtonGroupInput.md                 | 12 +++----
 docs/Readme.md                                |  6 ++--
 docs/ReferenceArrayField.md                   |  6 ++--
 docs/ReferenceField.md                        |  4 +--
 docs/ReferenceManyCount.md                    |  2 +-
 docs/ReferenceManyInput.md                    |  4 +--
 docs/ReferenceOneInput.md                     |  8 ++---
 docs/SaveButton.md                            |  6 ++--
 docs/SelectArrayInput.md                      | 16 +++++-----
 docs/SelectInput.md                           | 12 +++----
 docs/Show.md                                  |  8 ++---
 docs/ShowTutorial.md                          |  2 +-
 docs/SimpleForm.md                            |  4 +--
 docs/SimpleFormIterator.md                    |  4 +--
 docs/SimpleList.md                            |  4 +--
 docs/SimpleShowLayout.md                      |  8 ++---
 docs/SingleFieldList.md                       |  2 +-
 docs/TabbedForm.md                            | 10 +++---
 docs/TabbedShowLayout.md                      | 10 +++---
 docs/TextField.md                             |  4 +--
 docs/TextInput.md                             |  4 +--
 docs/Theming.md                               | 32 +++++++++----------
 docs/TimeInput.md                             |  2 +-
 docs/ToggleThemeButton.md                     |  4 +--
 docs/Toolbar.md                               |  6 ++--
 docs/TranslatableFields.md                    |  2 +-
 docs/TranslatableInputs.md                    |  2 +-
 docs/Tutorial.md                              | 12 +++----
 docs/Upgrade.md                               | 30 ++++++++---------
 docs/UrlField.md                              |  2 +-
 docs/Vite.md                                  |  2 +-
 docs/useInput.md                              |  4 +--
 docs/useLogout.md                             |  4 +--
 docs/useNotify.md                             |  6 ++--
 examples/no-code/src/main.tsx                 |  2 +-
 packages/ra-ui-materialui/README.md           |  2 +-
 packages/ra-ui-materialui/package.json        |  2 +-
 .../src/button/Button.stories.tsx             |  2 +-
 .../src/button/DeleteButton.tsx               |  4 +--
 .../src/button/SaveButton.tsx                 |  2 +-
 .../src/detail/SimpleShowLayout.tsx           |  2 +-
 packages/ra-ui-materialui/src/detail/Tab.tsx  |  2 +-
 .../src/detail/TabbedShowLayout.tsx           |  2 +-
 .../ra-ui-materialui/src/field/TextField.tsx  |  2 +-
 .../src/field/TranslatableFields.tsx          |  2 +-
 .../src/form/FormTabHeader.tsx                |  2 +-
 .../src/input/AutocompleteInput.tsx           |  4 +--
 .../src/input/CheckboxGroupInput.tsx          |  2 +-
 .../src/input/InputHelperText.tsx             |  6 ++--
 .../src/input/RadioButtonGroupInput.tsx       |  2 +-
 .../src/input/ResettableTextField.tsx         |  2 +-
 .../src/input/SelectInput.tsx                 |  2 +-
 .../src/input/TranslatableInputs.tsx          |  2 +-
 .../src/layout/AppBar.stories.tsx             |  4 +--
 .../src/layout/CardContentInner.tsx           |  2 +-
 .../src/layout/MenuItemLink.tsx               |  2 +-
 .../src/layout/Theme/ThemeProvider.tsx        |  2 +-
 .../src/list/SimpleList/SimpleList.tsx        |  2 +-
 .../src/list/SingleFieldList.tsx              |  4 +--
 .../src/list/datagrid/DatagridBody.tsx        |  4 +--
 .../src/list/pagination/Pagination.tsx        |  2 +-
 .../src/list/pagination/PaginationActions.tsx |  4 +--
 packages/react-admin/README.md                |  6 ++--
 111 files changed, 340 insertions(+), 342 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 65151bd940a..b47091fc2f4 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,7 +9,7 @@
 * [Doc] Fix examples of custom UserMenu items across the docs to support keyboard navigation ([#8837](https://github.com/marmelab/react-admin/pull/8837)) ([@smeng9](https://github.com/smeng9))
 * [Doc] Fix WithRecord usage in Datagrid to remind the label requirement ([#8851](https://github.com/marmelab/react-admin/pull/8851)) ([@fzaninotto](https://github.com/fzaninotto))
 * [Doc] Add more details about `useDefineAppLocation` in the `MultiLevelMenu` docs ([#8841](https://github.com/marmelab/react-admin/pull/8841)) ([@slax57](https://github.com/slax57))
-* [TypeScript] Fix `<Button>` should accept user defined MUI color palettes as `color` prop ([#8832](https://github.com/marmelab/react-admin/pull/8832)) ([@septentrion-730n](https://github.com/septentrion-730n))
+* [TypeScript] Fix `<Button>` should accept user defined Material UI color palettes as `color` prop ([#8832](https://github.com/marmelab/react-admin/pull/8832)) ([@septentrion-730n](https://github.com/septentrion-730n))
 * [TypeScript] Fix `<DateField>` props types ([#8844](https://github.com/marmelab/react-admin/pull/8844)) ([@elstgav](https://github.com/elstgav))
 
 ## v4.9.3
@@ -100,7 +100,7 @@ We also released new landing pages for both [React-admin](https://marmelab.com/r
 
 ## v4.8.1
 
-* Fix `<Notification>` raises a MUI warning when message is a string ([#8666](https://github.com/marmelab/react-admin/pull/8666)) ([slax57](https://github.com/slax57))
+* Fix `<Notification>` raises a Material UI warning when message is a string ([#8666](https://github.com/marmelab/react-admin/pull/8666)) ([slax57](https://github.com/slax57))
 * Fix `<ArrayField>` breaks when value is `null` ([#8659](https://github.com/marmelab/react-admin/pull/8659)) ([slax57](https://github.com/slax57))
 * Fix `<SimpleForm>` save toolbar hides content on mobile ([#8656](https://github.com/marmelab/react-admin/pull/8656)) ([fzaninotto](https://github.com/fzaninotto))
 * [TypeScript] Fix bad type deprecation on `onError` type ([#8668](https://github.com/marmelab/react-admin/pull/8668)) ([djhi](https://github.com/djhi))
@@ -198,8 +198,8 @@ We also released new landing pages for both [React-admin](https://marmelab.com/r
 ## 4.6.3
 
 * Fix `<ListGuesser>` links to Edit view even though there is only a ShowView ([#8546](https://github.com/marmelab/react-admin/pull/8546)) ([WiXSL](https://github.com/WiXSL))
-* Fix notifications with type 'warning' should use the warning text color from the MUI palette ([#8532](https://github.com/marmelab/react-admin/pull/8532)) ([Seojun-Park](https://github.com/Seojun-Park))
-* Fix notifications with type 'warning' should use the warning color from the MUI palette ([#8519](https://github.com/marmelab/react-admin/pull/8519)) ([Seojun-Park](https://github.com/Seojun-Park))
+* Fix notifications with type 'warning' should use the warning text color from the Material UI palette ([#8532](https://github.com/marmelab/react-admin/pull/8532)) ([Seojun-Park](https://github.com/Seojun-Park))
+* Fix notifications with type 'warning' should use the warning color from the Material UI palette ([#8519](https://github.com/marmelab/react-admin/pull/8519)) ([Seojun-Park](https://github.com/Seojun-Park))
 * [Doc] Improve Index/Reference page ([#8550](https://github.com/marmelab/react-admin/pull/8550)) ([fzaninotto](https://github.com/fzaninotto))
 * [Doc] Improve `<Search>` usage documentation ([#8527](https://github.com/marmelab/react-admin/pull/8527)) ([fzaninotto](https://github.com/fzaninotto))
 * [Doc] Fix `<ContainerLayout>` is hard to find ([#8547](https://github.com/marmelab/react-admin/pull/8547)) ([fzaninotto](https://github.com/fzaninotto))
@@ -227,7 +227,7 @@ We also released new landing pages for both [React-admin](https://marmelab.com/r
 ## 4.6.1
 
 * Fix `<SelectColumnsButton referenceKey>` prop handling ([#8432](https://github.com/marmelab/react-admin/pull/8432)) ([wcoppens](https://github.com/wcoppens))
-* Fix `<TextInput>` missing placeholder with MUI v5.4 ([#8439](https://github.com/marmelab/react-admin/pull/8439)) ([kosmotema](https://github.com/kosmotema))
+* Fix `<TextInput>` missing placeholder with Material UI v5.4 ([#8439](https://github.com/marmelab/react-admin/pull/8439)) ([kosmotema](https://github.com/kosmotema))
 * Fix `<ResourceMenuItem>` throws an error when used with only `<Resource>` as `<Admin>` children ([#8473](https://github.com/marmelab/react-admin/pull/8473)) ([slax57](https://github.com/slax57))
 * Fix `useReferenceInputController` does not pass meta to `useReference` ([#8477](https://github.com/marmelab/react-admin/pull/8477)) ([stesie](https://github.com/stesie))
 * Fix `ra-input-richtext` TipTap dependencies on prosemirror ([#8470](https://github.com/marmelab/react-admin/pull/8470)) ([slax57](https://github.com/slax57))
@@ -445,7 +445,7 @@ We also released new landing pages for both [React-admin](https://marmelab.com/r
 
 ## v4.3.3
 
-* Fix `<Confirm>` doesn't pass props to the underlying MUI `<Dialog>` component ([#8176](https://github.com/marmelab/react-admin/pull/8176)) ([WiXSL](https://github.com/WiXSL))
+* Fix `<Confirm>` doesn't pass props to the underlying Material UI `<Dialog>` component ([#8176](https://github.com/marmelab/react-admin/pull/8176)) ([WiXSL](https://github.com/WiXSL))
 * Fix performance issue in `useGetList` and `useGetManyReferences` ([#8174](https://github.com/marmelab/react-admin/pull/8174)) ([djhi](https://github.com/djhi))
 * Fix `localStorageStore.reset()` does not remove all items ([#8161](https://github.com/marmelab/react-admin/pull/8161)) ([fzaninotto](https://github.com/fzaninotto))
 * [Doc] Fix upgrade doc mentions wrong syntax for `<Admin layout>` prop ([#8169](https://github.com/marmelab/react-admin/pull/8169)) ([herndlm](https://github.com/herndlm))
@@ -649,7 +649,7 @@ We also released new landing pages for both [React-admin](https://marmelab.com/r
 * Fix `<Logout />` appears even when not logged in ([#7842](https://github.com/marmelab/react-admin/pull/7842)) ([septentrion-730n](https://github.com/septentrion-730n))
 * Fix `<Show disableAuthentication>` prop is ignored ([#7837](https://github.com/marmelab/react-admin/pull/7837)) ([septentrion-730n](https://github.com/septentrion-730n))
 * Fix `<ImageField>` style is ignored for single images ([#7836](https://github.com/marmelab/react-admin/pull/7836)) ([fzaninotto](https://github.com/fzaninotto))
-* Fix `<FileInput>` and  `<ImageInput>` style don't use MUI theme ([#7835](https://github.com/marmelab/react-admin/pull/7835)) ([septentrion-730n](https://github.com/septentrion-730n))
+* Fix `<FileInput>` and  `<ImageInput>` style don't use Material UI theme ([#7835](https://github.com/marmelab/react-admin/pull/7835)) ([septentrion-730n](https://github.com/septentrion-730n))
 * Fix `<NumberInput>` seems buggy when used in a Filter Form ([#7830](https://github.com/marmelab/react-admin/pull/7830)) ([fzaninotto](https://github.com/fzaninotto))
 * Fix `<Datagrid expand>` expands ALL rows when used as a child of `<ArrayField>` ([#7828](https://github.com/marmelab/react-admin/pull/7828)) ([septentrion-730n](https://github.com/septentrion-730n))
 * Fix `<ReferenceInput>` generated label in Filter Form ([#7825](https://github.com/marmelab/react-admin/pull/7825)) ([septentrion-730n](https://github.com/septentrion-730n))
@@ -826,7 +826,7 @@ The following list concerns version 4.0.0, as well as all the pre-releases (alph
 ### 📦 Dependency Updates
 
 - Add React 18 compatibility (#7377)
-- Upgrade `material-ui` to v5 (and it's now called `MUI`) (#6650)
+- Upgrade `material-ui` to v5 (#6650)
 - Use `react-query` for data fetching instead of home made solution (#6779, #6916, #7006, #7016, #7025, #6891, #7035, #7020, #7035, #7001)
 - Replace `react-final-form` with `react-hook-form` (#7087)
 - Upgrade `react-router` to [V6](https://reactrouter.com/docs/en/v6/api) (#6873)
@@ -846,7 +846,7 @@ The following list concerns version 4.0.0, as well as all the pre-releases (alph
 - Move `bulkActionButtons` from `<List>` to `<Datagrid>` (#7114)
 - Rename `currentSort` to `sort` (#7076)
 - Change `setSort` signature to make it consistent across components (#7065)
-- Use MUI autocomplete instead of our own (#6924, #6971)
+- Use Material UI autocomplete instead of our own (#6924, #6971)
 - Rename `<TranslationProvider>` to `<I18nContextProvider>`
 - Switch `<WithPermissions>` wrapping to a `useAuthenticated` hook in main controllers (#6921)
 - Move `<Notification>` component into `<AdminUI>` to avoid gotchas when overriding the layout (#7082)
@@ -1031,7 +1031,7 @@ Many thanks to all the contributors (whether they helped developing, testing, do
 * Fix `<SimpleFormIterator>` transition animations on add and remove items ([#6871](https://github.com/marmelab/react-admin/pull/6871)) ([WiXSL](https://github.com/WiXSL))
 * Fix simple CodeSandbox ([#6781](https://github.com/marmelab/react-admin/pull/6781)) ([djhi](https://github.com/djhi))
 * Fix `<DateInput>` breaks `<SimpleFormIterator>` ([#6763](https://github.com/marmelab/react-admin/pull/6763)) ([djhi](https://github.com/djhi))
-* Fix `<Login>` page isn't customizable through MUI theme ([#6762](https://github.com/marmelab/react-admin/pull/6762)) ([djhi](https://github.com/djhi))
+* Fix `<Login>` page isn't customizable through Material UI theme ([#6762](https://github.com/marmelab/react-admin/pull/6762)) ([djhi](https://github.com/djhi))
 * Fix call time parameters don't take priority in `useMutation` ([#6761](https://github.com/marmelab/react-admin/pull/6761)) ([djhi](https://github.com/djhi))
 * Bump minor dependencies
 * [TypeScript] Fix Graphql Providers Types ([#6724](https://github.com/marmelab/react-admin/pull/6724)) ([djhi](https://github.com/djhi))
@@ -1041,7 +1041,7 @@ Many thanks to all the contributors (whether they helped developing, testing, do
 * [Doc] Add link to images in tutorial ([#6771](https://github.com/marmelab/react-admin/pull/6771)) ([ocxers](https://github.com/ocxers))
 * [Doc] Fix typo in Architecture chapter ([#6740](https://github.com/marmelab/react-admin/pull/6740)) ([HobbitCodes](https://github.com/HobbitCodes))
 * [Doc] Fix typo in Theming chapter ([#6714](https://github.com/marmelab/react-admin/pull/6714)) ([afilp](https://github.com/afilp))
-* Fix MUI's urls reference for version 4 ([#6702](https://github.com/marmelab/react-admin/pull/6702)) ([WiXSL](https://github.com/WiXSL))
+* Fix Material UI's urls reference for version 4 ([#6702](https://github.com/marmelab/react-admin/pull/6702)) ([WiXSL](https://github.com/WiXSL))
 * [Doc] Add `getIdentity` function to the authProvider reference ([#6697](https://github.com/marmelab/react-admin/pull/6697)) ([WiXSL](https://github.com/WiXSL))
 * [Doc] Improve `useRedirect` description and examples ([#6696](https://github.com/marmelab/react-admin/pull/6696)) ([WiXSL](https://github.com/WiXSL))
 
@@ -1061,7 +1061,7 @@ Many thanks to all the contributors (whether they helped developing, testing, do
 
 ### 🐛 Bug Fixes
 
-- Fix MUI 4.12 deprecation warnings ([#6587](https://github.com/marmelab/react-admin/pull/6587)) ([fzaninotto](https://github.com/fzaninotto))
+- Fix Material UI 4.12 deprecation warnings ([#6587](https://github.com/marmelab/react-admin/pull/6587)) ([fzaninotto](https://github.com/fzaninotto))
 - Refactor ArrayInput and SimpleFormIterator with context ([#6612](https://github.com/marmelab/react-admin/pull/6612)) ([djhi](https://github.com/djhi))
 - Refactor graphql providers and migrate to the new dataProvider signature ([#6628](https://github.com/marmelab/react-admin/pull/6628)) ([djhi](https://github.com/djhi))
 - [GraphQL]: Fix Simple Response Parser Modify all Objects ([#6643](https://github.com/marmelab/react-admin/pull/6643)) ([djhi](https://github.com/djhi))
diff --git a/README.md b/README.md
index d23418e2f88..d951e76c157 100644
--- a/README.md
+++ b/README.md
@@ -22,7 +22,7 @@ A frontend Framework for building data-driven applications running in the browse
 
 * ☂️ **Opt-In Types**: Develop either in TypeScript or JavaScript
 
-* 👨‍👩‍👧‍👦 Powered by [MUI](https://mui.com/), [react-hook-form](https://react-hook-form.com), [react-router](https://reacttraining.com/react-router/), [react-query](https://react-query-v3.tanstack.com/), [TypeScript](https://www.typescriptlang.org/) and a few more
+* 👨‍👩‍👧‍👦 Powered by [Material UI](https://mui.com/material-ui/getting-started/overview/), [react-hook-form](https://react-hook-form.com), [react-router](https://reacttraining.com/react-router/), [react-query](https://react-query-v3.tanstack.com/), [TypeScript](https://www.typescriptlang.org/) and a few more
 
 ## Installation
 
@@ -58,7 +58,7 @@ render(
 );
 ```
 
-The `<Resource>` component is a configuration component that allows you to define sub components for each of the admin view: `list`, `edit`, and `create`. These components use MUI and custom components from react-admin:
+The `<Resource>` component is a configuration component that allows you to define sub components for each of the admin view: `list`, `edit`, and `create`. These components use Material UI and custom components from react-admin:
 
 ```jsx
 // in posts.js
diff --git a/docs/Admin.md b/docs/Admin.md
index b8e9fc62c7f..a259e44a3e1 100644
--- a/docs/Admin.md
+++ b/docs/Admin.md
@@ -209,7 +209,7 @@ const App = () => (
 
 ## `dashboard`
 
-By default, the homepage of an admin app is the `list` of the first child `<Resource>`. But you can also specify a custom component instead. To fit in the general design, use MUI's `<Card>` component, and [react-admin's `<Title>` component](./Title.md) to set the title in the AppBar:
+By default, the homepage of an admin app is the `list` of the first child `<Resource>`. But you can also specify a custom component instead. To fit in the general design, use Material UI's `<Card>` component, and [react-admin's `<Title>` component](./Title.md) to set the title in the AppBar:
 
 ```jsx
 // in src/Dashboard.js
@@ -270,7 +270,7 @@ When users type URLs that don't match any of the children `<Resource>` component
 
 ![Not Found](./img/not-found.png)
 
-You can customize this page to use the component of your choice by passing it as the `catchAll` prop. To fit in the general design, use MUI's `<Card>` component, and [react-admin's `<Title>` component](./Title.md):
+You can customize this page to use the component of your choice by passing it as the `catchAll` prop. To fit in the general design, use Material UI's `<Card>` component, and [react-admin's `<Title>` component](./Title.md):
 
 ```jsx
 // in src/NotFound.js
@@ -342,7 +342,7 @@ export const MyMenu = () => {
 };
 ```
 
-**Tip**: `<Menu.Item>` must be used to avoid unwanted side effects in mobile views. It supports a custom text and icon (which must be a MUI `<SvgIcon>`).
+**Tip**: `<Menu.Item>` must be used to avoid unwanted side effects in mobile views. It supports a custom text and icon (which must be a Material UI `<SvgIcon>`).
 
 Then, pass it to the `<Admin>` component as the `menu` prop:
 
@@ -361,7 +361,7 @@ See the [Theming documentation](./Theming.md#using-a-custom-menu) for more detai
 
 ## `theme`
 
-MUI supports [theming](https://mui.com/customization/themes). This lets you customize the look and feel of an admin by overriding fonts, colors, and spacing. You can provide a custom MUI theme by using the `theme` prop:
+Material UI supports [theming](https://mui.com/material-ui/customization/theming/). This lets you customize the look and feel of an admin by overriding fonts, colors, and spacing. You can provide a custom Material UI theme by using the `theme` prop:
 
 ```jsx
 import { defaultTheme } from 'react-admin';
@@ -450,7 +450,7 @@ You can also disable it completely along with the `/login` route by passing `fal
 
 See The [Authentication documentation](./Authentication.md#customizing-the-login-component) for more details.
 
-**Tip**: Before considering writing your own login page component, please take a look at how to change the default [background image](./Theming.md#using-a-custom-login-page) or the [MUI theme](#theme). See the [Authentication documentation](./Authentication.md#customizing-the-login-component) for more details.
+**Tip**: Before considering writing your own login page component, please take a look at how to change the default [background image](./Theming.md#using-a-custom-login-page) or the [Material UI theme](#theme). See the [Authentication documentation](./Authentication.md#customizing-the-login-component) for more details.
 
 ## `authCallbackPage`
 
diff --git a/docs/AdvancedTutorials.md b/docs/AdvancedTutorials.md
index 9762deacde8..f81d93fcc30 100644
--- a/docs/AdvancedTutorials.md
+++ b/docs/AdvancedTutorials.md
@@ -68,7 +68,7 @@ This article shows how you can customize many parts of the framework without rep
 
 ## Changing The Look And Feel Of React-Admin Without JSX
 
-This article shows how to customize react-admin look and feel using only the MUI theme.
+This article shows how to customize react-admin look and feel using only the Material UI theme.
 
 ![Screencast](https://marmelab.com/097bee867a1d1dc55dec5456732fe94a/screencast.gif)
 
diff --git a/docs/AppBar.md b/docs/AppBar.md
index b5964385adf..b6e50dbb99e 100644
--- a/docs/AppBar.md
+++ b/docs/AppBar.md
@@ -22,7 +22,7 @@ By default, the `<AppBar>` component displays:
 
 You can customize the App Bar by creating a custom component based on `<AppBar>`, with different props.
 
-**Tip**: Don't mix react-admin's `<AppBar>` component with [MUI's `<AppBar>` component](https://mui.com/material-ui/api/app-bar/). The first one leverages the second but adds some react-admin-specific features.
+**Tip**: Don't mix react-admin's `<AppBar>` component with [Material UI's `<AppBar>` component](https://mui.com/material-ui/api/app-bar/). The first one leverages the second but adds some react-admin-specific features.
 
 ## Usage
 
@@ -67,11 +67,11 @@ const App = () => (
 | `alwaysOn`          | Optional | `boolean`      | -        | When true, the app bar is always visible            |
 | `children`          | Optional | `ReactElement` | -        | What to display in the central part of the app bar  |
 | `color`             | Optional | `string`       | -        | The background color of the app bar                 |
-| `sx`                | Optional | `SxProps`      | -        | Style overrides, powered by MUI System              |
+| `sx`                | Optional | `SxProps`      | -        | Style overrides, powered by Material UI System              |
 | `toolbar`           | Optional | `ReactElement` | -        | The content of the toolbar                          |
 | `userMenu`          | Optional | `ReactElement` | -        | The content of the dropdown user menu               |
 
-Additional props are passed to [the underlying MUI `<AppBar>` element](https://mui.com/material-ui/api/app-bar/).
+Additional props are passed to [the underlying Material UI `<AppBar>` element](https://mui.com/material-ui/api/app-bar/).
 
 ## `alwaysOn`
 
@@ -133,7 +133,7 @@ const MyAppBar = () => (
 
 ## `color`
 
-React-admin's `<AppBar>` renders an MUI `<AppBar>`, which supports a `color` prop to set the app bar color depending on the theme. By default, the app bar color is set to the `secondary` theme color.
+React-admin's `<AppBar>` renders an Material UI `<AppBar>`, which supports a `color` prop to set the app bar color depending on the theme. By default, the app bar color is set to the `secondary` theme color.
 
 This means you can set the app bar color to 'default', 'inherit', 'primary', 'secondary', 'transparent', or any string.
 
@@ -174,7 +174,7 @@ This property accepts the following subclasses:
 | `& .RaAppBar-menuButton` | Applied to the hamburger icon |
 | `& .RaAppBar-title`      | Applied to the title portal   |
 
-To override the style of `<AppBar>` using the [MUI style overrides](https://mui.com/customization/theme-components/), use the `RaAppBar` key.
+To override the style of `<AppBar>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaAppBar` key.
 
 ## `toolbar`
 
@@ -243,7 +243,7 @@ import { AppBar, UserMenu, useUserMenu } from 'react-admin';
 import { MenuItem, ListItemIcon, ListItemText } from '@mui/material';
 import SettingsIcon from '@mui/icons-material/Settings';
 
-// It's important to pass the ref to allow MUI to manage the keyboard navigation
+// It's important to pass the ref to allow Material UI to manage the keyboard navigation
 const SettingsMenuItem = React.forwardRef((props, ref) => {
     // We are not using MenuItemLink so we retrieve the onClose function from the UserContext
     const { onClose } = useUserMenu();
@@ -251,7 +251,7 @@ const SettingsMenuItem = React.forwardRef((props, ref) => {
         <MenuItem
             onClick={onClose}
             ref={ref}
-            // It's important to pass the props to allow MUI to manage the keyboard navigation
+            // It's important to pass the props to allow Material UI to manage the keyboard navigation
             {...props}
         >
             <ListItemIcon>
@@ -404,7 +404,7 @@ export const MyAppbar = () => (
 
 ## Building Your Own AppBar
 
-If react-admin's `<AppBar>` component doesn't meet your needs, you can build your own component using MUI's `<AppBar>`. Here is an example:
+If react-admin's `<AppBar>` component doesn't meet your needs, you can build your own component using Material UI's `<AppBar>`. Here is an example:
 
 ```jsx
 // in src/MyAppBar.js
diff --git a/docs/Architecture.md b/docs/Architecture.md
index 0d0ac5440c7..cef497fdc4b 100644
--- a/docs/Architecture.md
+++ b/docs/Architecture.md
@@ -99,7 +99,7 @@ React-admin has two sets of users:
 
 For each feature, we design the User Experience (UX) and the Developer Experience (DX) carefully. 
 
-For the visual part, react-admin builds upon MUI, which is the implementation of the Material Design System. It's a great help to build usable, consistent user interfaces, but it's not enough. 
+For the visual part, react-admin builds upon Material UI, which is the implementation of the Material Design System. It's a great help to build usable, consistent user interfaces, but it's not enough. 
 
 We spend a great deal of time refining the UI to make it as intuitive as possible. We pay attention to small alignment glitches, screen flashes, and color inconsistencies. We iterate with every customer feedback, to remove visual and animation problems that occur in real-life applications.
 
@@ -115,7 +115,7 @@ Many excellent open-source libraries already address partial requirements of B2B
 
 Rather than reinventing the wheel, react-admin uses the best tools in each category (in terms of features, developer experience, active maintenance, documentation, user base), and provides a glue around these libraries.
 
-In react-admin v4, these libraries are called react-query, react-router, react-hook-form, MUI, testing-library, date-fns, and lodash.
+In react-admin v4, these libraries are called react-query, react-router, react-hook-form, Material UI, testing-library, date-fns, and lodash.
 
 When a new requirement arises, the react-admin teams always looks for an existing solution, and prefers integrating it rather than redeveloping it.
 
@@ -172,7 +172,7 @@ const MyRefreshButton = () => {
 
 Before adding a new hook or a new prop to an existing component, we always check if there isn't a simple way to implement the feature in pure React. If it's the case, then we don't add the new prop. We prefer to keep the react-admin API, code, test, and documentation simple. This choice is crucial to keep the learning curve acceptable, and maintenance burden low.
 
-For instance, the `<SimpleShowLayout>` component displays Field elements in a column. How can you put two fields in a single column? We could add a specific syntax allowing to specify the number of elements per column and per line. This would complicate the usage and documentation for simple use cases. Besides, it's doable in pure React, without any change in the react-admin core, e.g. by leveraging MUI's `<Stack>` component:
+For instance, the `<SimpleShowLayout>` component displays Field elements in a column. How can you put two fields in a single column? We could add a specific syntax allowing to specify the number of elements per column and per line. This would complicate the usage and documentation for simple use cases. Besides, it's doable in pure React, without any change in the react-admin core, e.g. by leveraging Material UI's `<Stack>` component:
 
 ```jsx
 import * as React from 'react';
@@ -224,7 +224,7 @@ Every time we implemented child inspection, we regretted it afterward. We tend t
 React-admin is a *distribution* of several packages, each of which handles a specific feature. The packages are all located in the `packages/` directory. The most notable packages are:
     
 * `ra-core`: The core react-admin logic, without any UI.
-* `ra-ui-materialui`: The MUI skin for react-admin.
+* `ra-ui-materialui`: The Material UI skin for react-admin.
 * `ra-data-*`: Data providers for various data backends.
 * `ra-language-*`: Interface translations for various languages.
 * `react-admin`: the standard distribution of react-admin
diff --git a/docs/Authentication.md b/docs/Authentication.md
index 135456b9aa4..03629d469d7 100644
--- a/docs/Authentication.md
+++ b/docs/Authentication.md
@@ -342,7 +342,7 @@ import { useLogout } from 'react-admin';
 import MenuItem from '@mui/material/MenuItem';
 import ExitIcon from '@mui/icons-material/PowerSettingsNew';
 
-// It's important to pass the ref to allow MUI to manage the keyboard navigation
+// It's important to pass the ref to allow Material UI to manage the keyboard navigation
 const MyLogoutButton = forwardRef((props, ref) => {
     const logout = useLogout();
     const handleClick = () => logout();
@@ -350,7 +350,7 @@ const MyLogoutButton = forwardRef((props, ref) => {
         <MenuItem
             onClick={handleClick}
             ref={ref}
-            // It's important to pass the props to allow MUI to manage the keyboard navigation
+            // It's important to pass the props to allow Material UI to manage the keyboard navigation
             {...props}
         >
             <ExitIcon /> Logout
diff --git a/docs/AutocompleteArrayInput.md b/docs/AutocompleteArrayInput.md
index c8bd49441ee..332da8c3b05 100644
--- a/docs/AutocompleteArrayInput.md
+++ b/docs/AutocompleteArrayInput.md
@@ -6,11 +6,11 @@ title: "The AutocompleteArrayInput Component"
 # `<AutocompleteArrayInput>`
 
 To let users choose multiple values in a list using a dropdown with autocompletion, use `<AutocompleteArrayInput>`.
-It renders using MUI [Autocomplete](https://mui.com/components/autocomplete/).
+It renders using Material UI [Autocomplete](https://mui.com/material-ui/react-autocomplete/).
 
 ![AutocompleteArrayInput](./img/autocomplete-array-input.gif)
 
-This input allows editing values that are arrays of scalar values, e.g. `[123, 456]`. 
+This input allows editing values that are arrays of scalar values, e.g. `[123, 456]`.
 
 **Tip**: React-admin includes other components allowing the edition of such values:
 
@@ -18,7 +18,7 @@ This input allows editing values that are arrays of scalar values, e.g. `[123, 4
 - [`<CheckboxGroupInput>`](./CheckboxGroupInput.md) renders a list of checkbox options
 - [`<DualListInput>`](./DualListInput.md) renders a list of choices that can be moved from one list to another
 
-**Tip**: `<AutocompleteArrayInput>` is a stateless component, so it only allows to *filter* the list of choices, not to *extend* it. If you need to populate the list of choices based on the result from a `fetch` call (and if [`<ReferenceArrayInput>`](./ReferenceArrayInput.md) doesn't cover your need), you'll have to [write your own Input component](./Inputs.md#writing-your-own-input-component) based on MUI `<Autocomplete>` component.
+**Tip**: `<AutocompleteArrayInput>` is a stateless component, so it only allows to *filter* the list of choices, not to *extend* it. If you need to populate the list of choices based on the result from a `fetch` call (and if [`<ReferenceArrayInput>`](./ReferenceArrayInput.md) doesn't cover your need), you'll have to [write your own Input component](./Inputs.md#writing-your-own-input-component) based on Material UI `<Autocomplete>` component.
 
 ## Usage
 
@@ -396,11 +396,11 @@ If you're using `<AutocompleteArrayInput>` inside a [`<ReferenceArrayInput>`](./
 
 ## `sx`: CSS API
 
-The `<AutocompleteArrayInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)).
+The `<AutocompleteArrayInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)).
 
-`<AutocompleteArrayInput>` renders an [`<AutocompleteInput>`](./AutocompleteInput.md) and reuses its styles. To override the style of all instances of `<AutocompleteInput>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaAutocompleteInput` key.
+`<AutocompleteArrayInput>` renders an [`<AutocompleteInput>`](./AutocompleteInput.md) and reuses its styles. To override the style of all instances of `<AutocompleteInput>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaAutocompleteInput` key.
 
-Refer to the [MUI `<Autocomplete>` component](https://mui.com/components/autocomplete/) to know its CSS API.
+Refer to the [Material UI `<Autocomplete>` component](https://mui.com/material-ui/react-autocomplete/) to know its CSS API.
 
 ## `translateChoice`
 
@@ -424,7 +424,7 @@ In that case, set the `translateChoice` prop to `false`.
 
 ## Additional Props
 
-`<AutocompleteArrayInput>` renders a [MUI `<Autocomplete>` component](https://mui.com/components/autocomplete/) and accepts the `<Autocomplete>` props:
+`<AutocompleteArrayInput>` renders a [Material UI `<Autocomplete>` component](https://mui.com/material-ui/react-autocomplete/) and accepts the `<Autocomplete>` props:
 
 {% raw %}
 ```jsx
@@ -491,7 +491,7 @@ You can pass a custom element as [`optionText`](#optiontext) to have `<Autocompl
 
 `<AutocompleteArrayInput>` will render the custom option element inside a [`<RecordContext>`](./useRecordContext.md), using the related choice as the `record` prop. You can use Field components there.
 
-However, as the underlying MUI `<Autocomplete>` component requires that the current selection is a string, you must also pass a function as the `inputText` prop. This function should return a text representation of the current selection. You should also pass a `matchSuggestion` function to filter the choices based on the current selection.
+However, as the underlying Material UI `<Autocomplete>` component requires that the current selection is a string, you must also pass a function as the `inputText` prop. This function should return a text representation of the current selection. You should also pass a `matchSuggestion` function to filter the choices based on the current selection.
 
 ```jsx
 const choices = [
@@ -560,7 +560,7 @@ const PostCreate = () => {
 ```
 {% endraw %}
 
-Use the `create` prop when you want a more polished or complex UI. For example a MUI `<Dialog>` asking for multiple fields because the choices are from a referenced resource.
+Use the `create` prop when you want a more polished or complex UI. For example a Material UI `<Dialog>` asking for multiple fields because the choices are from a referenced resource.
 
 {% raw %}
 ```jsx
diff --git a/docs/AutocompleteInput.md b/docs/AutocompleteInput.md
index c084ae46520..64cad6d5106 100644
--- a/docs/AutocompleteInput.md
+++ b/docs/AutocompleteInput.md
@@ -6,7 +6,7 @@ title: "The AutocompleteInput Component"
 # `<AutocompleteInput>`
 
 To let users choose a value in a list using a dropdown with autocompletion, use `<AutocompleteInput>`.
-It renders using [MUI's `<Autocomplete>`](https://mui.com/components/autocomplete/).
+It renders using [Material UI's `<Autocomplete>`](https://mui.com/material-ui/react-autocomplete/).
 
 ![AutocompleteInput](./img/autocomplete-input.gif)
 
@@ -47,7 +47,7 @@ The form value for the source must be the selected value, e.g.
 
 **Tip**: If you need to let users select more than one item in the list, check out the [`<AutocompleteArrayInput>`](./AutocompleteArrayInput.md) component.
 
-**Tip**: `<AutocompleteInput>` is a stateless component, so it only allows to *filter* the list of choices, not to *extend* it. If you need to populate the list of choices based on the result from a `fetch` call (and if [`<ReferenceInput>`](./ReferenceInput.md) doesn't cover your need), you'll have to [write your own Input component](./Inputs.md#writing-your-own-input-component) based on MUI `<Autocomplete>` component.
+**Tip**: `<AutocompleteInput>` is a stateless component, so it only allows to *filter* the list of choices, not to *extend* it. If you need to populate the list of choices based on the result from a `fetch` call (and if [`<ReferenceInput>`](./ReferenceInput.md) doesn't cover your need), you'll have to [write your own Input component](./Inputs.md#writing-your-own-input-component) based on Material UI `<Autocomplete>` component.
 
 ## Props
 
@@ -444,15 +444,15 @@ If you're using `<AutocompleteInput>` inside a [`<ReferenceInput>`](./ReferenceI
 
 ## `sx`: CSS API
 
-The `<AutocompleteInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<AutocompleteInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                    | Description                                     |
 |------------------------------|-------------------------------------------------|
 | `& .RaSelectInput-textField` | Applied to the underlying `TextField` component |
 
-To override the style of all instances of `<AutocompleteInput>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaAutocompleteInput` key.
+To override the style of all instances of `<AutocompleteInput>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaAutocompleteInput` key.
 
-Refer to the [MUI `<Autocomplete>` component](https://mui.com/components/autocomplete/) to know its CSS API.
+Refer to the [Material UI `<Autocomplete>` component](https://mui.com/material-ui/react-autocomplete/) to know its CSS API.
 
 ## `translateChoice`
 
@@ -474,7 +474,7 @@ In that case, set the `translateChoice` prop to `false`.
 
 ## Additional Props
 
-`<AutocompleteInput>` renders a [MUI `<Autocomplete>` component](https://mui.com/components/autocomplete/) and it accepts the `<Autocomplete>` props:
+`<AutocompleteInput>` renders a [Material UI `<Autocomplete>` component](https://mui.com/material-ui/react-autocomplete/) and it accepts the `<Autocomplete>` props:
 
 {% raw %}
 ```jsx
@@ -616,7 +616,7 @@ You can pass a custom element as [`optionText`](#optiontext) to have `<Autocompl
 
 `<AutocompleteInput>` will render the custom option element inside a [`<RecordContext>`](./useRecordContext.md), using the related choice as the `record` prop. You can use Field components there.
 
-However, as the underlying MUI `<Autocomplete>` component requires that the current selection is a string, you must also pass a function as the `inputText` prop. This function should return a text representation of the current selection. You should also pass a `matchSuggestion` function to filter the choices based on the current selection.
+However, as the underlying Material UI `<Autocomplete>` component requires that the current selection is a string, you must also pass a function as the `inputText` prop. This function should return a text representation of the current selection. You should also pass a `matchSuggestion` function to filter the choices based on the current selection.
 
 ```jsx
 const choices = [
@@ -685,7 +685,7 @@ const PostCreate = () => {
 ```
 {% endraw %}
 
-Use the `create` prop when you want a more polished or complex UI. For example an MUI `<Dialog>` asking for multiple fields because the choices are from a referenced resource.
+Use the `create` prop when you want a more polished or complex UI. For example an Material UI `<Dialog>` asking for multiple fields because the choices are from a referenced resource.
 
 {% raw %}
 ```js
diff --git a/docs/BooleanField.md b/docs/BooleanField.md
index 56547c8f247..62f66d10b29 100644
--- a/docs/BooleanField.md
+++ b/docs/BooleanField.md
@@ -29,9 +29,9 @@ import { BooleanField } from 'react-admin';
 
 ## `sx`: CSS API
 
-The `<BooleanField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)).
+The `<BooleanField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)).
 
-To override the style of all instances of `<BooleanField>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaBooleanField` key.
+To override the style of all instances of `<BooleanField>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaBooleanField` key.
 
 ## Usage
 
diff --git a/docs/BooleanInput.md b/docs/BooleanInput.md
index 752aec35a0c..c77ee192b40 100644
--- a/docs/BooleanInput.md
+++ b/docs/BooleanInput.md
@@ -29,7 +29,7 @@ import { BooleanInput } from 'react-admin';
 
 ## `options`
 
-Use the `options` prop to pass any option supported by the MUI's `Switch` components. For example, here's how to set a custom checked icon:
+Use the `options` prop to pass any option supported by the Material UI's `Switch` components. For example, here's how to set a custom checked icon:
 
 {% raw %}
 ```jsx
@@ -42,6 +42,4 @@ import FavoriteIcon from '@mui/icons-material/Favorite';
 
 ![CustomBooleanInputCheckIcon](./img/custom-switch-icon.png)
 
-Refer to [MUI Switch documentation](https://mui.com/api/switch) for more details.
-
-
+Refer to [Material UI Switch documentation](https://mui.com/material-ui/api/switch/) for more details.
diff --git a/docs/Breadcrumb.md b/docs/Breadcrumb.md
index e30d3dd2a26..08da73256ac 100644
--- a/docs/Breadcrumb.md
+++ b/docs/Breadcrumb.md
@@ -138,7 +138,7 @@ Check [the ra-navigation documentation](https://marmelab.com/ra-enterprise/modul
 | ----------- | -------- | ------------------- | -------- | -------------------------------------- |
 | `children`  | required | `ReactNode`         | -        | The Breadcrumb Items to be rendered.   |
 | `separator` | Optional | `string | function` | '/'      | The character user as separator        |
-| `sx`        | Optional | `SxProps`           | -        | Style overrides, powered by MUI System |
+| `sx`        | Optional | `SxProps`           | -        | Style overrides, powered by Material UI System |
 
 Additional props are passed down to the root `<nav>` component.
 
diff --git a/docs/Buttons.md b/docs/Buttons.md
index 43ee9fd1d68..03b27ae7178 100644
--- a/docs/Buttons.md
+++ b/docs/Buttons.md
@@ -101,7 +101,7 @@ It also supports [all the other `<Button>` props](#button).
 |-----------------------------|--------------------------------------------------------------------|
 | `&.RaCreateButton-floating` | Applied to the underlying `MuiFab` component used in small screens |
 
-To override the style of all instances of `<CreateButton>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaCreateButton` key.
+To override the style of all instances of `<CreateButton>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaCreateButton` key.
 
 ### `<ListButton>`
 
@@ -260,7 +260,7 @@ This button is an internal component used by react-admin in [the Filter button/f
 
 #### `sx`: CSS API
 
-To override the style of all instances of `<FilterButton>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaFilterButton` key.
+To override the style of all instances of `<FilterButton>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaFilterButton` key.
 
 ## Record Buttons
 
@@ -314,11 +314,11 @@ const MyEdit = () => (
 
 ### `disableRipple`
 
-The ripple effect can cause [performance issues](https://github.com/marmelab/react-admin/issues/5587) for large datagrids. It's possible to remove the ripple effect from within your MUI theme. The [MUI docs](https://mui.com/material-ui/getting-started/faq/#how-can-i-disable-the-ripple-effect-globally) provide instructions on how to do this.
+The ripple effect can cause [performance issues](https://github.com/marmelab/react-admin/issues/5587) for large datagrids. It's possible to remove the ripple effect from within your Material UI theme. The [Material UI docs](https://mui.com/material-ui/getting-started/faq/#how-can-i-disable-the-ripple-effect-globally) provide instructions on how to do this.
 
 It's worth noting that removing the ripple will cause accessibility issues, including a lack of focus states during tab navigating for components like `BooleanInput` and `CheckboxGroupInput`. 
 
-Note: The `disableRipple` was set to `true` in React Admin for a time, but was reimplemented due to accessibility concerns. If you'd like to reimplement the static ripple colour effect, you can use the [React Admin's previous implementation](https://github.com/marmelab/react-admin/blob/994079cbca810a2e74d85329e684811645b04ae2/packages/ra-ui-materialui/src/defaultTheme.ts#L31) as a starting point. [The MUI docs](https://mui.com/material-ui/api/button-base/#props) also gives details on how to reimplement focus styles using the `Mui-focusVisible` class.
+Note: The `disableRipple` was set to `true` in React Admin for a time, but was reimplemented due to accessibility concerns. If you'd like to reimplement the static ripple colour effect, you can use the [React Admin's previous implementation](https://github.com/marmelab/react-admin/blob/994079cbca810a2e74d85329e684811645b04ae2/packages/ra-ui-materialui/src/defaultTheme.ts#L31) as a starting point. [The Material UI docs](https://mui.com/material-ui/api/button-base/#props) also gives details on how to reimplement focus styles using the `Mui-focusVisible` class.
 
 ## Miscellaneous
 
@@ -335,7 +335,7 @@ Base component for most react-admin buttons. Responsive (displays only the icon
 | `disabled`   | Optional | `boolean`                      | `false`   | If `true`, the button will be disabled |
 | `size`       | Optional | `'large' | 'medium' | 'small'` | `'small'` | Button size                            |
 
-Other props are passed down to [the underlying MUI `<Button>`](https://mui.com/api/button/).
+Other props are passed down to [the underlying Material UI `<Button>`](https://mui.com/material-ui/api/button/).
 
 #### `sx`: CSS API
 
@@ -348,7 +348,7 @@ Other props are passed down to [the underlying MUI `<Button>`](https://mui.com/a
 | `& .RaButton-mediumIcon`     | Applied to the Button's `children` when `size` prop is `medium` and `alignIcon` prop is 'right' |
 | `& .RaButton-largeIcon`      | Applied to the Button's `children` when `size` prop is `large` and `alignIcon` prop is 'right'  |
 
-To override the style of all instances of `<Button>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaButton` key.
+To override the style of all instances of `<Button>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaButton` key.
 
 ### `<RefreshButton>`
 ### `<SkipNavigationButton>`
@@ -359,7 +359,7 @@ To override the style of all instances of `<Button>` using the [MUI style overri
 |-----------------------------------------------|-------------------------------------------------|
 | `&.RaSkipNavigationButton-skipToContentButton` | Applied to the underlying `MuiButton` component |
 
-To override the style of all instances of `<SkipNavigationButton>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaSkipNavigationButton` key.
+To override the style of all instances of `<SkipNavigationButton>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaSkipNavigationButton` key.
 
 ### `<MenuItemLink>`
 
@@ -373,7 +373,7 @@ The `<MenuItemLink>` component displays a menu item with a label and an icon - o
 | `primaryText` | Required | `ReactNode`          | -       | The menu content, displayed when the menu isn't minimized. |
 | `leftIcon`    | Optional | `ReactNode`          | -       | The menu icon |
 
-Additional props are passed down to [the underling MUI `<MenuItem>` component](https://mui.com/api/menu-item/#menuitem-api).
+Additional props are passed down to [the underling Material UI `<MenuItem>` component](https://mui.com/material-ui/api/menu-item/).
 
 You can create a custom menu component using the `<DashboardMenuItem>` and `<MenuItemLink>` components:
 
@@ -435,7 +435,7 @@ See [The theming documentation](./Theming.md#menuitemlink) for more details.
 | `&.RaMenuItemLink-active`  | Applied to the underlying `MuiMenuItem`'s `activeClassName` prop    |
 | `& .RaMenuItemLink-icon`    | Applied to the `ListItemIcon` component when `leftIcon` prop is set |
 
-To override the style of all instances of `<MenuItemLink>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaMenuItemLink` key.
+To override the style of all instances of `<MenuItemLink>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaMenuItemLink` key.
 
 ### `<UserMenu>`
 
@@ -452,6 +452,6 @@ To override the style of all instances of `<MenuItemLink>` using the [MUI style
 | `& .RaUserMenu-userButton` | Applied to the underlying `MuiButton` component when `useGetIdentity().loaded` is `true` and `useGetIdentity().identity.fullName` is set |
 | `& .RaUserMenu-avatar`     | Applied to the underlying `MuiAvatar` component when `useGetIdentity().avatar` is `true`                                                 |
 
-To override the style of all instances of `<UserMenu>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaUserMenu` key.
+To override the style of all instances of `<UserMenu>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaUserMenu` key.
 
 See [The theming documentation](./Theming.md#usermenu-customization) for more details.
diff --git a/docs/CheckboxGroupInput.md b/docs/CheckboxGroupInput.md
index 2d4651c66ab..2cb45fcd7cd 100644
--- a/docs/CheckboxGroupInput.md
+++ b/docs/CheckboxGroupInput.md
@@ -54,7 +54,7 @@ The form value for the source must be an array of the selected values, e.g.
 | ----------------- | -------- | -------------------------- | ------- | ----------------------------------------------------------------- |
 | `choices`         | Required | `Object[]`                 | -       | List of choices                                                   |
 | `labelPlacement`  | Optional | `"bottom" `&#124;`"end"`&#124;`"start"`&#124;`"top" ` | `"end"` | The position of the checkbox label.    |
-| `options`         | Optional | `Object`                   | -       | Props to pass to the MUI `<CheckboxGroup>` component.             |
+| `options`         | Optional | `Object`                   | -       | Props to pass to the Material UI `<CheckboxGroup>` component.             |
 | `optionText`      | Optional | `string` &#124; `Function` | `name`  | Field name of record to display in the suggestion item or function which accepts the correct record as argument (`record => {string}`) |
 | `optionValue`     | Optional | `string`                   | `id`    | Field name of record containing the value to use as input value   |
 | `row`             | Optional | `boolean`                  | `true`  | Display group of elements in a compact row.                       |
@@ -129,7 +129,7 @@ By default, this inputs renders a checkbox and a label for each choice, with the
 
 ## `options`
 
-Use the `options` attribute if you want to override any of MUI's [MUI Checkbox documentation](https://mui.com/api/checkbox/) attributes:
+Use the `options` attribute if you want to override any of Material UI's [Material UI Checkbox documentation](https://mui.com/material-ui/api/checkbox/) attributes:
 
 {% raw %}
 ```jsx
@@ -220,13 +220,13 @@ By default, the checkboxes are displayed in a row. You can change that and let r
 
 ## `sx`: CSS API
 
-The `<CheckboxGroupInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<CheckboxGroupInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                       | Description                                              |
 |---------------------------------|----------------------------------------------------------|
-| `& .RaCheckboxGroupInput-label` | Applied to the underlying MUI's `FormLabel` component    |
+| `& .RaCheckboxGroupInput-label` | Applied to the underlying Material UI's `FormLabel` component    |
 
-To override the style of all instances of `<CheckboxGroupInput>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaCheckboxGroupInput` key.
+To override the style of all instances of `<CheckboxGroupInput>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaCheckboxGroupInput` key.
 
 ## `translateChoice`
 
diff --git a/docs/ChipField.md b/docs/ChipField.md
index 624b1c80dac..4bf0ec0d78a 100644
--- a/docs/ChipField.md
+++ b/docs/ChipField.md
@@ -5,7 +5,7 @@ title: "The ChipField Component"
 
 # `<ChipField>`
 
-Displays a value inside a ["Chip"](https://mui.com/components/chips), which is MUI's term for a label.
+Displays a value inside a ["Chip"](https://mui.com/components/chips), which is Material UI's term for a label.
 
 ## Usage
 
@@ -29,14 +29,14 @@ import { ChipField, SingleFieldList, ReferenceManyField } from 'react-admin';
 </ReferenceManyField>
 ```
 
-Additional props are passed down to MUI's `<Chip>` element. Check [The MUI `<Chip>` documentation](https://mui.com/api/chip/) for details.
+Additional props are passed down to Material UI's `<Chip>` element. Check [The Material UI `<Chip>` documentation](https://mui.com/material-ui/api/chip/) for details.
 
 ## `sx`: CSS API
 
-The `<ChipField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<ChipField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name            | Description                                              |
 |----------------------|----------------------------------------------------------|
-| `&.RaChipField-chip` | Applied to the underlying MUI's `Chip` component |
+| `&.RaChipField-chip` | Applied to the underlying Material UI's `Chip` component |
 
-To override the style of all instances of `<ChipField>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaChipField` key.
+To override the style of all instances of `<ChipField>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaChipField` key.
diff --git a/docs/Community.md b/docs/Community.md
index aa034821a02..ac86821a924 100644
--- a/docs/Community.md
+++ b/docs/Community.md
@@ -37,7 +37,7 @@ See the [Discord](#discord) section above.
 
 If your problem is related to a library used by react-admin, you should ask for help on the dependency's support channel:
 
-* MUI: [Documentation](https://mui.com/material-ui/getting-started/overview/), [Support](https://mui.com/material-ui/getting-started/support/)
+* Material UI: [Documentation](https://mui.com/material-ui/getting-started/overview/), [Support](https://mui.com/material-ui/getting-started/support/)
 * react-router: [Documentation](https://reactrouter.com/en/main), [Discord](https://rmx.as/discord)
 * react-query: [Documentation](https://tanstack.com/query/v3/docs/react/overview), [Discord](https://tlinz.com/discord)
 * react-hook-form: [Documentation](https://react-hook-form.com/get-started), [Discord](https://discord.gg/yYv7GZ8)
diff --git a/docs/Confirm.md b/docs/Confirm.md
index e7ace096b19..4eea67556f2 100644
--- a/docs/Confirm.md
+++ b/docs/Confirm.md
@@ -5,7 +5,7 @@ title: "The Confirm Component"
 
 # `<Confirm>`
 
-`<Confirm>` leverages MUI's [`<Dialog>` component](https://mui.com/components/dialogs) to implement a confirmation popup.
+`<Confirm>` leverages Material UI's [`<Dialog>` component](https://mui.com/material-ui/react-dialog/) to implement a confirmation popup.
 
 ![Confirm dialog](./img/confirm.webp)
 
@@ -72,20 +72,20 @@ const BulkResetViewsButton = () => {
 | `ConfirmIcon`      | Optional | `ReactElement`                   | `<CheckCircle/>`      | Icon element of the confirm button                                 |
 | `CancelIcon`       | Optional | `ReactElement`                   | `<ErrorOutlineIcon/>` | Icon element of the cancel button                                  |
 | `translateOptions` | Optional | `{ id?: string, name?: string }` | {}                    | Custom id and name to be used in the dialog title                  |
-| `sx`               | Optional | `SxProps`                        | ''                    | MUI shortcut for defining custom styles with access to the theme   |
+| `sx`               | Optional | `SxProps`                        | ''                    | Material UI shortcut for defining custom styles with access to the theme   |
 
 Text props such as `title`, `content`, `cancel`, `confirm` and `translateOptions` are translatable. You can pass translation keys in these props. Note: `content` is only translatable when value is `string`, otherwise it renders the content as a `ReactNode`.
 
 ## `sx`: CSS API
 
-The `<Confirm>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<Confirm>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                       | Description                                                    |
 |---------------------------------|----------------------------------------------------------------|
 | `& .RaConfirm-confirmPrimary`   | Applied to the confirm button when `confirmColor` is `primary` |
 | `& .RaConfirm-confirmWarning`   | Applied to the confirm button when `confirmColor` is `warning` |
 
-To override the style of all instances of `<Confirm>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaConfirm` key.
+To override the style of all instances of `<Confirm>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaConfirm` key.
 
 ## Delete With Confirmation
 
diff --git a/docs/ContainerLayout.md b/docs/ContainerLayout.md
index 934b669f24c..635c2bcf61a 100644
--- a/docs/ContainerLayout.md
+++ b/docs/ContainerLayout.md
@@ -41,7 +41,7 @@ See more details in the [ra-navigation documentation](https://marmelab.com/ra-en
 
 ## `appBar`
 
-If you want to use a different color for the AppBar, or to make it sticky, pass a custom `appBar` element based on `<Header>`, which is a simple wrapper around [MUI's `<AppBar>` component](https://mui.com/material-ui/react-app-bar/#main-content).
+If you want to use a different color for the AppBar, or to make it sticky, pass a custom `appBar` element based on `<Header>`, which is a simple wrapper around [Material UI's `<AppBar>` component](https://mui.com/material-ui/react-app-bar/).
 
 ```jsx
 import { ContainerLayout, Header } from '@react-admin/ra-navigation';
@@ -62,7 +62,7 @@ const MyLayout = props => <ContainerLayout {...props} fixed />;
 
 ## `maxWidth`
 
-This prop allows to set the maximum width of the content [`<Container>`](https://mui.com/material-ui/react-container/#main-content). It accepts a string, one of `xs`, `sm`, `md`, `lg`, `xl`, or `false` to remove side margins and occupy the full width of the screen.
+This prop allows to set the maximum width of the content [`<Container>`](https://mui.com/material-ui/react-container/). It accepts a string, one of `xs`, `sm`, `md`, `lg`, `xl`, or `false` to remove side margins and occupy the full width of the screen.
 
 ```jsx
 import { ContainerLayout } from '@react-admin/ra-navigation';
@@ -121,7 +121,7 @@ export const App = () => (
 
 ## `sx`
 
-The `sx` prop allows to customize the style of the layout, and the underlying component. It accepts a [MUI `sx` prop](https://mui.com/system/the-sx-prop/#main-content).
+The `sx` prop allows to customize the style of the layout, and the underlying component. It accepts a [Material UI `sx` prop](https://mui.com/system/the-sx-prop/).
 
 {% raw %}
 ```jsx
@@ -167,13 +167,13 @@ import { MenuList, MenuItem, ListItemIcon, ListItemText } from '@mui/material';
 import SettingsIcon from '@mui/icons-material/Settings';
 import { ContainerLayout } from '@react-admin/ra-navigation';
 
-// It's important to pass the ref to allow MUI to manage the keyboard navigation
+// It's important to pass the ref to allow Material UI to manage the keyboard navigation
 const ConfigurationMenu = React.forwardRef((props, ref) => {
     const { onClose } = useUserMenu();
     return (
         <MenuItem
             ref={ref}
-            // It's important to pass the props to allow MUI to manage the keyboard navigation
+            // It's important to pass the props to allow Material UI to manage the keyboard navigation
             {...props}
             to="/configuration"
             onClick={onClose}
diff --git a/docs/Count.md b/docs/Count.md
index 7bc36a50186..0786f07ffe2 100644
--- a/docs/Count.md
+++ b/docs/Count.md
@@ -76,7 +76,7 @@ const TicketListAside = () => {
 | `sort`     | Optional | `{ field: string, order: 'ASC' or 'DESC' }` | `{ field: 'id', order: 'DESC' }`  | The sort option sent to `getList`                                       |
 | `timeout`  | Optional | number                                     | 1000                              | Number of milliseconds to wait before displaying the loading indicator. |
 
-Additional props are passed to [the underlying MUI `<Typography>` element](https://mui.com/material-ui/api/typography/).
+Additional props are passed to [the underlying Material UI `<Typography>` element](https://mui.com/material-ui/api/typography/).
 
 ## `filter`
 
diff --git a/docs/Create.md b/docs/Create.md
index 1932c3678c7..7d04c3889b6 100644
--- a/docs/Create.md
+++ b/docs/Create.md
@@ -116,7 +116,7 @@ const PostCreate = () => (
 
 ## `component`
 
-By default, the `<Create>` view render the main form inside a MUI `<Card>` element. The actual layout of the form depends on the `Form` component you're using ([`<SimpleForm>`](./SimpleForm.md), [`<TabbedForm>`](./TabbedForm.md), or a custom form component).
+By default, the `<Create>` view render the main form inside a Material UI `<Card>` element. The actual layout of the form depends on the `Form` component you're using ([`<SimpleForm>`](./SimpleForm.md), [`<TabbedForm>`](./TabbedForm.md), or a custom form component).
 
 Some form layouts also use `Card`, in which case the user ends up seeing a card inside a card, which is bad UI. To avoid that, you can override the main page container by passing a `component` prop :
 
@@ -290,15 +290,15 @@ const PostCreate = () => (
 
 ## `sx`: CSS API
 
-The `<Create>` components accept the usual `className` prop, but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following keys:
+The `<Create>` components accept the usual `className` prop, but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following keys:
 
 | Rule name               | Description                                                                          |
 |-------------------------|--------------------------------------------------------------------------------------|
 | `& .RaCreate-main`      | Applied to the main container                                                        |
 | `& .RaCreate-noActions` | Applied to the main container when `actions` prop is `false`                         |
-| `& .RaCreate-card`      | Applied to the child component inside the main container (MUI's `Card` by default)   |
+| `& .RaCreate-card`      | Applied to the child component inside the main container (Material UI's `Card` by default)   |
 
-To override the style of all instances of `<Create>` components using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaCreate` key.
+To override the style of all instances of `<Create>` components using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaCreate` key.
 
 ## `title`
 
@@ -463,7 +463,7 @@ export default PostList = () => (
 ```
 {% endraw %}
 
-**Tip**: To style the button with the main color from the MUI theme, use the `Link` component from the `react-admin` package rather than the one from `react-router-dom`.
+**Tip**: To style the button with the main color from the Material UI theme, use the `Link` component from the `react-admin` package rather than the one from `react-router-dom`.
 
 **Tip**: The `<Create>` component also watches the "source" parameter of `location.search` (the query string in the URL) in addition to `location.state` (a cross-page message hidden in the router memory). So the `CreateRelatedCommentButton` could also be written as:
 
diff --git a/docs/CreateInDialogButton.md b/docs/CreateInDialogButton.md
index 62b72ad6c48..8b4dd8b586f 100644
--- a/docs/CreateInDialogButton.md
+++ b/docs/CreateInDialogButton.md
@@ -61,10 +61,10 @@ In the above example, `<CreateInDialogButton>` is used to create a new employee
 
 `<CreateInDialogButton>` accepts the following props:
 
-* `inline`: set to true to display only an MUI `<IconButton>` instead of the full `<Button>`. The label will still be available as a `<Tooltip>` though.
+* `inline`: set to true to display only an Material UI `<IconButton>` instead of the full `<Button>`. The label will still be available as a `<Tooltip>` though.
 * `icon`: allows to override the default icon.
 * `label`: allows to override the default button label. I18N is supported.
-* `ButtonProps`: object containing props to pass to MUI's `<Button>`.
+* `ButtonProps`: object containing props to pass to Material UI's `<Button>`.
 * remaining props will be passed to the [`<CreateDialog>`](./CreateDialog.md) dialog component.
 
 Check out [the `ra-form-layout` documentation](https://marmelab.com/ra-enterprise/modules/ra-form-layout#createindialogbutton-editindialogbutton-and-showindialogbutton) for more details.
diff --git a/docs/Datagrid.md b/docs/Datagrid.md
index bdedfa47241..9934395eabe 100644
--- a/docs/Datagrid.md
+++ b/docs/Datagrid.md
@@ -56,7 +56,7 @@ Here are all the props accepted by the component:
 * [`size`](#size)
 * [`sx`](#sx-css-api)
 
-Additional props are passed down to [the MUI `<Table>` element](https://mui.com/api/table/).
+Additional props are passed down to [the Material UI `<Table>` element](https://mui.com/material-ui/api/table/).
 
 ## `body`
 
@@ -312,11 +312,11 @@ const CustomResetViewsButton = () => {
 export default CustomResetViewsButton;
 ```
 
-**Tip**: [`<Confirm>`](./Confirm.md) leverages MUI's `<Dialog>` component to implement a confirmation popup. Feel free to use it in your admins!
+**Tip**: [`<Confirm>`](./Confirm.md) leverages Material UI's `<Dialog>` component to implement a confirmation popup. Feel free to use it in your admins!
 
 **Tip**: `<Confirm>` text props such as `title` and `content` are translatable. You can pass translation keys in these props. Note: `content` is only translatable when value is `string`, otherwise it renders the content as a `ReactNode`.
 
-**Tip**: You can customize the text of the two `<Confirm>` component buttons using the `cancel` and `confirm` props which accept translation keys. You can customize the icons by setting the `ConfirmIcon` and `CancelIcon` props, which accept a [SvgIcon](https://mui.com/components/icons/) type.
+**Tip**: You can customize the text of the two `<Confirm>` component buttons using the `cancel` and `confirm` props which accept translation keys. You can customize the icons by setting the `ConfirmIcon` and `CancelIcon` props, which accept a [SvgIcon](https://mui.com/material-ui/icons/#svgicon) type.
 
 **Tip**: React-admin doesn't use the `<Confirm>` component internally, because deletes and updates are applied locally immediately, then dispatched to the server after a few seconds, unless the user chooses to undo the modification. That's what we call optimistic rendering. You can do the same for the `<ResetViewsButton>` by setting `undoable: true` in the last argument of `useUpdateMany()`, as follows:
 
@@ -689,7 +689,7 @@ export const PostList = () => (
 );
 ```
 
-**Tip**: `size` is actually a prop of the MUI `<Table>` component. Just like all additional `<Datagrid>` props, it is passed down to the `<Table>` component. 
+**Tip**: `size` is actually a prop of the Material UI `<Table>` component. Just like all additional `<Datagrid>` props, it is passed down to the `<Table>` component. 
 
 ## `sx`: CSS API
 
@@ -741,7 +741,7 @@ const PostList = () => (
 ```
 {% endraw %}
 
-**Tip**: `sx` is the standard for style customization in MUI . Check [the sx documentation](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles) for more advanced usage.
+**Tip**: `sx` is the standard for style customization in Material UI . Check [the sx documentation](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles) for more advanced usage.
 
 **Tip**: The `Datagrid` component `classes` can also be customized for all instances of the component with its global css name `"RaDatagrid"` as [describe here](https://marmelab.com/blog/2019/12/18/react-admin-3-1.html#theme-overrides)
 
diff --git a/docs/DateInput.md b/docs/DateInput.md
index ed4d3e6ee6e..42db07f17f3 100644
--- a/docs/DateInput.md
+++ b/docs/DateInput.md
@@ -40,6 +40,6 @@ import { DateInput, minValue } from 'react-admin';
 
 It is not possible to customize the date format. Browsers use the user locale to display the date in the correct format.
 
-If you need to render a UI despite the browser locale, MUI also proposes a [Date Picker](https://mui.com/components/pickers/#date-pickers) component, which is more customizable than the native date picker, but requires additional packages.
+If you need to render a UI despite the browser locale, MUI also proposes a [Date Picker](https://mui.com/x/react-date-pickers/date-picker/) component, which is more customizable than the native date picker, but requires additional packages.
 
-![MUI Date picker](./img/date-picker.gif)
+![MUI X Date picker](./img/date-picker.gif)
diff --git a/docs/DateTimeInput.md b/docs/DateTimeInput.md
index 527aae89a4d..b66bc15b7ef 100644
--- a/docs/DateTimeInput.md
+++ b/docs/DateTimeInput.md
@@ -23,7 +23,7 @@ The input value must be a valid date string, i.e. a string understood by JavasSr
 
 After modification by the user, the value is stored as a `Date` object, using the browser's timezone. When transformed to JSON, the date is serialized as a string in the ISO 8601 format ('yyyy-MM-ddThh:mm').
 
-**Tip**: For a MUI styled `<DateTimeInput>` component, check out [MUI Date pickers](https://mui.com/x/react-date-pickers/getting-started/#date-pickers)
+**Tip**: For a Material UI styled `<DateTimeInput>` component, check out [MUI X Date Pickers](https://mui.com/x/react-date-pickers/getting-started/#date-pickers)
 
 ## Props
 
diff --git a/docs/DualListInput.md b/docs/DualListInput.md
index 8cb1cf3abdb..30f6a7460d2 100644
--- a/docs/DualListInput.md
+++ b/docs/DualListInput.md
@@ -60,14 +60,14 @@ Check [the `ra-relationships` documentation](https://marmelab.com/ra-enterprise/
 | Prop                   | Required | Type                                                         | Default                                           | Description                                                                                                                            |
 |------------------------|----------|--------------------------------------------------------------|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
 | `choices`              | Optional | `Object[]`                                                   | -                                                 | List of items to show as options. Required unless inside a ReferenceArray Input.                                                                                                       |
-| `addButton`            | Optional | 'outlined' &#124; 'contained' &#124; 'text' &#124; `element` | -                                                 | A MUI `variant` value for the add button or a React element to replace it.                                                             |
+| `addButton`            | Optional | 'outlined' &#124; 'contained' &#124; 'text' &#124; `element` | -                                                 | A Material UI `variant` value for the add button or a React element to replace it.                                                             |
 | `addButtonLabel`       | Optional | `string`                                                     | `ra-relationships. duallistinput. select`         | The text or translation key to use as the label for the add button                                                                     |
 | `availableItems Label` | Optional | `string`                                                     | `ra-relationships. duallistinput. availableItems` | The text or translation key to use as the label for the list of available choices                                                      |
 | `dense`                | Optional | `boolean`                                                    | `false`                                           | Visual density of the list component                                                                                                   |
 | `disableValue`         | Optional | `string`                                                     | 'disabled'                                        | The custom field name used in `choices` to disable some choices                                                                        |
 | `optionText`           | Optional | `string` &#124; `Function`                                   | `name`                                            | Field name of record to display in the suggestion item or function which accepts the current record as argument (`record => {string}`) |
 | `optionValue`          | Optional | `string`                                                     | `id`                                              | Field name of record containing the value to use as input value                                                                        |
-| `removeButton`         | Optional | 'outlined' &#124; 'contained' &#124; 'text' &#124; `element` | -                                                 | A MUI `variant` value for the remove button or a React element to replace it.                                                          |
+| `removeButton`         | Optional | 'outlined' &#124; 'contained' &#124; 'text' &#124; `element` | -                                                 | A Material UI `variant` value for the remove button or a React element to replace it.                                                          |
 | `removeButton Label`   | Optional | `string`                                                     | `ra-relationships duallistinput. unselect`        | The text or translation key to use as the label for the remove button                                                                  |
 | `selectedItems Label`  | Optional | `string`                                                     | `ra-relationships. duallistinput. selectedItems`  | The text or translation key to use as the label for the list of selected choices                                                       |
 | `translateChoice`      | Optional | `boolean`                                                    | `true`                                            | Whether the choices should be translated                                                                                               |
@@ -232,7 +232,7 @@ const choices = [
 
 ## `sx`: CSS API
 
-The `<DualListInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<DualListInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                          | Description                      |
 |------------------------------------|----------------------------------|
@@ -247,7 +247,7 @@ The `<DualListInput>` component accepts the usual `className` prop. You can also
 | `& .RaDualListInput-selectedList`  | Applied to the selected list     |
 | `& .RaDualListInput-availableList` | Applied to the available list    |
 
-To override the style of all instances of `<DualListInput>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaDualListInput` key.
+To override the style of all instances of `<DualListInput>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaDualListInput` key.
 
 
 ## `translateChoice`
diff --git a/docs/Edit.md b/docs/Edit.md
index c8818b2a741..0e18e266839 100644
--- a/docs/Edit.md
+++ b/docs/Edit.md
@@ -150,7 +150,7 @@ const Aside = () => {
 
 ## `component`
 
-By default, the `<Edit>` view render the main form inside a MUI `<Card>` element. The actual layout of the form depends on the `Form` component you're using ([`<SimpleForm>`](./SimpleForm.md), [`<TabbedForm>`](./TabbedForm.md), or a custom form component).
+By default, the `<Edit>` view render the main form inside a Material UI `<Card>` element. The actual layout of the form depends on the `Form` component you're using ([`<SimpleForm>`](./SimpleForm.md), [`<TabbedForm>`](./TabbedForm.md), or a custom form component).
 
 Some form layouts also use `Card`, in which case the user ends up seeing a card inside a card, which is bad UI. To avoid that, you can override the main page container by passing a `component` prop :
 
@@ -470,15 +470,15 @@ const PostEdit = () => (
 
 ## `sx`: CSS API
 
-The `<Edit>` components accept the usual `className` prop, but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following keys:
+The `<Edit>` components accept the usual `className` prop, but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following keys:
 
 | Rule name               | Description                                                                          |
 |-------------------------|--------------------------------------------------------------------------------------|
 | `& .RaEdit-main`      | Applied to the main container                                                        |
 | `& .RaEdit-noActions` | Applied to the main container when `actions` prop is `false`                         |
-| `& .RaEdit-card`      | Applied to the child component inside the main container (MUI's `Card` by default)   |
+| `& .RaEdit-card`      | Applied to the child component inside the main container (Material UI's `Card` by default)   |
 
-To override the style of all instances of `<Edit>` components using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaEdit` key.
+To override the style of all instances of `<Edit>` components using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaEdit` key.
 
 ## `title`
 
diff --git a/docs/EditInDialogButton.md b/docs/EditInDialogButton.md
index e20c4feb0d3..db09ac0773a 100644
--- a/docs/EditInDialogButton.md
+++ b/docs/EditInDialogButton.md
@@ -54,10 +54,10 @@ const CompanyShow = () => (
 
 It accepts the following props:
 
-* `inline`: set to true to display only an MUI `<IconButton>` instead of the full `<Button>`. The label will still be available as a `<Tooltip>` though.
+* `inline`: set to true to display only an Material UI `<IconButton>` instead of the full `<Button>`. The label will still be available as a `<Tooltip>` though.
 * `icon`: allows to override the default icon.
 * `label`: allows to override the default button label. I18N is supported.
-* `ButtonProps`: object containing props to pass to MUI's `<Button>`.
+* `ButtonProps`: object containing props to pass to Material UI's `<Button>`.
 * remaining props will be passed to the [`<EditDialog>`](./EditDialog.md) dialog component.
 
 Check out [the `ra-form-layout` documentation](https://marmelab.com/ra-enterprise/modules/ra-form-layout#createindialogbutton-editindialogbutton-and-showindialogbutton) for more details.
diff --git a/docs/EditTutorial.md b/docs/EditTutorial.md
index 1ee948001aa..a0177361502 100644
--- a/docs/EditTutorial.md
+++ b/docs/EditTutorial.md
@@ -5,7 +5,7 @@ title: "The Creation and Edition Pages"
 
 # The Creation and Edition Pages
 
-React-admin provides many hooks and components to let you build custom user experiences for editing and creating records, leveraging MUI and react-hook-form.
+React-admin provides many hooks and components to let you build custom user experiences for editing and creating records, leveraging Material UI and react-hook-form.
 
 ![Edit view example](./img/edit-view-example.png)
 
@@ -91,7 +91,7 @@ It's a super common component. In fact, many of its features could be extracted
 
 ### `<Form>`: Form Logic
 
-To use `react-hook-form` with MUI inputs, the previous example leverages the `<Controller>` tag, which expects a `control` object generated by the `useForm` hook ([see the related `react-hook-form` doc](https://react-hook-form.com/get-started#IntegratingControlledInputs)).
+To use `react-hook-form` with Material UI inputs, the previous example leverages the `<Controller>` tag, which expects a `control` object generated by the `useForm` hook ([see the related `react-hook-form` doc](https://react-hook-form.com/get-started#IntegratingControlledInputs)).
 
 We can avoid the call to `useForm` by putting its logic inside a custom component. That's exaclty what react-admin's [`<Form>` component](./Form.md) does. `<Form>` also creates a react-hook-form `<FormProvider>`, so we no longer need to pass the `control` prop to each `<Controller>` element. 
 
diff --git a/docs/EmailField.md b/docs/EmailField.md
index 638c1d79781..092609ba9b1 100644
--- a/docs/EmailField.md
+++ b/docs/EmailField.md
@@ -5,7 +5,7 @@ title: "The EmailField Component"
 
 # `<EmailField>`
 
-`<EmailField>` displays an email as a MUI's `<Link href="mailto:" />` component.
+`<EmailField>` displays an email as a Material UI's `<Link href="mailto:" />` component.
 
 ```jsx
 import { EmailField } from 'react-admin';
diff --git a/docs/FAQ.md b/docs/FAQ.md
index 8ff8c7b9577..bb1ed6ba2a5 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -139,7 +139,7 @@ For all those cases, you can use the [`<FormDataConsumer>`](https://marmelab.com
 
 ## UI in production build is empty or broke
 
-You have probably specified a version requirement for `@mui/material` that is incompatible with the one required by `react-admin`. As a consequence, npm bundled two copies of `MUI` in your application, and `MUI` doesn't work in that case.
+You have probably specified a version requirement for `@mui/material` that is incompatible with the one required by `react-admin`. As a consequence, npm bundled two copies of Material UI in your application, and doesn't work in that case.
 
 Please align your version requirement with the one of the `ra-ui-materialui` package.
 
diff --git a/docs/Features.md b/docs/Features.md
index 9a0fd167695..7b4dab71475 100644
--- a/docs/Features.md
+++ b/docs/Features.md
@@ -19,7 +19,7 @@ React-admin provides the **best-in-class documentation**, demo apps, and support
 
 That probably explains why more than 3,000 new apps are published every month using react-admin. 
 
-So react-admin is not just the assembly of [react-query](https://react-query.tanstack.com/), [react-hook-form](https://marmelab.com/react-admin/assets/techs/react-hook-form.jpeg), [react-router](https://reacttraining.com/react-router/), [MUI](https://mui.com/) and [Emotion](https://github.com/emotion-js/emotion). It's a **framework** made to speed up and facilitate the development of single-page apps in React.
+So react-admin is not just the assembly of [react-query](https://react-query.tanstack.com/), [react-hook-form](https://marmelab.com/react-admin/assets/techs/react-hook-form.jpeg), [react-router](https://reacttraining.com/react-router/), [Material UI](https://mui.com/material-ui/getting-started/overview/) and [Emotion](https://github.com/emotion-js/emotion). It's a **framework** made to speed up and facilitate the development of single-page apps in React.
 
 ## Basic CRUD
 
@@ -243,7 +243,7 @@ Reference components are a tremendous development accelerator for complex fronte
 
 Let's be realistic: Many developers focus on features first and don't have much time to spend polishing the User Interface (UI). We tend to be like that, too! The result is that quite often, admin apps are ugly. Spacing isn't consistent, buttons aren't in the best place, and color schemes hurt the eyes.
 
-React-admin provides **components that look pretty good out of the box**, so even if you don't spend time on the UI, it won't look bad (unless you try hard). React-admin uses [MUI](https://mui.com), which is a React implementation of the [Material Design](https://m3.material.io/) guidelines, the most battle-tested design system.
+React-admin provides **components that look pretty good out of the box**, so even if you don't spend time on the UI, it won't look bad (unless you try hard). React-admin uses [Material UI](https://mui.com/material-ui/getting-started/overview/), which is a React implementation of the [Material Design](https://material.io/) guidelines, the most battle-tested design system.
 
 <video controls autoplay muted loop width="100%">
   <source src="https://user-images.githubusercontent.com/99944/116970434-4a926480-acb8-11eb-8ce2-0602c680e45e.mp4" type="video/webm" />
@@ -398,7 +398,7 @@ Check the [Building A Custom Filter Tutorial](./FilteringTutorial.md#building-a-
 
 Many admin apps let users perform complex tasks implying the update of many fields and records. To allow such complex workflows, developers must be able to build sophisticated forms, with elaborate validation rules.
 
-React-admin offers a **rich set of input components** to build forms, powered by [MUI](https://mui.com) and [react-hook-form](https://react-hook-form.com/). React-admin's form components also take care of binding the form values to the record being edited and validating the form inputs.
+React-admin offers a **rich set of input components** to build forms, powered by [Material UI](https://mui.com/material-ui/getting-started/overview/) and [react-hook-form](https://react-hook-form.com/). React-admin's form components also take care of binding the form values to the record being edited and validating the form inputs.
 
 For instance, here is how to group inputs into tabs using `<TabbedForm>`:
 
@@ -825,11 +825,11 @@ export const CategoriesList = () => (
 Check out the following components for displaying hierarchical data:
 
 - [`<TreeWithDetails>`](./TreeWithDetails.md): A list view for tree structures, with a details panel.
-- [`<Tree>`](https://marmelab.com/ra-enterprise/modules/ra-tree#tree-component): A list view for tree structures, with a MUI skin.
+- [`<Tree>`](https://marmelab.com/ra-enterprise/modules/ra-tree#tree-component): A list view for tree structures, with a Material UI skin.
 
 ## Application Building Blocks
 
-A UI kit like MUI provides basic building blocks like a button, a form, a table, etc. React-admin goes one level higher and provides a set of **[application components](./Reference.md#components)** specifically designed for building admin and B2B *applications*.
+A UI kit like Material UI provides basic building blocks like a button, a form, a table, etc. React-admin goes one level higher and provides a set of **[application components](./Reference.md#components)** specifically designed for building admin and B2B *applications*.
 
 ![editable Datagrid](https://marmelab.com/ra-enterprise/modules/assets/ra-editable-datagrid/latest/ra-editable-datagrid-overview.gif)
 
@@ -1100,7 +1100,7 @@ Check the following components for details:
 
 ## Theming
 
-The default [Material Design](https://m3.material.io/) look and feel is nice, but a bit... Google-y. If this bothers you, or if you need to brand your app, rest assured: react-admin is fully themeable.
+The default [Material Design](https://material.io/) look and feel is nice, but a bit... Google-y. If this bothers you, or if you need to brand your app, rest assured: react-admin is fully themeable.
 
 For instance, you can use react-admin to build a [Music Player](https://demo.navidrome.org/app/):
 
@@ -1276,7 +1276,7 @@ React-admin is used by thousands of companies across the world, so the internati
 
 ## Accessibility
 
-The react-admin core team has a **strong commitment to accessibility**. React-admin uses the [MUI](https://mui.com/) components, which are accessible by default. For its own components, react-admin uses the [WAI-ARIA](https://www.w3.org/TR/wai-aria/) standard to make them accessible. This includes `aria-` attributes, keyboard navigation, and focus management.
+The react-admin core team has a **strong commitment to accessibility**. React-admin uses the [Material UI](https://mui.com/material-ui/getting-started/overview/) components, which are accessible by default. For its own components, react-admin uses the [WAI-ARIA](https://www.w3.org/TR/wai-aria/) standard to make them accessible. This includes `aria-` attributes, keyboard navigation, and focus management.
 
 We routinely test react-admin with the [WAVE](https://wave.webaim.org/) and [Axe](https://www.deque.com/axe/) accessibility tools.
 
diff --git a/docs/Fields.md b/docs/Fields.md
index dd8091606ab..8521bf85f44 100644
--- a/docs/Fields.md
+++ b/docs/Fields.md
@@ -130,7 +130,7 @@ All Field components accept the following props:
 | [`className`](#classname)     | Optional | `string`                       | -        | A class name (usually generated by JSS) to customize the look and feel of the field element itself                                                      |
 | [`textAlign`](#textalign)     | Optional | `string`                       | 'left'   | Defines the text alignment inside a cell. Set to `right` for right alignment (e.g. for numbers)                                                         |
 | [`emptyText`](#emptytext)     | Optional | `string`                       | ''       | Defines a text to be shown when a field has no value (not supported in array fields)                                                                    |
-| [`sx`](#sx)                   | Optional | `SxProps`                      | ''       | MUI shortcut for defining custom styles with access to the theme                                                                                        |
+| [`sx`](#sx)                   | Optional | `SxProps`                      | ''       | Material UI shortcut for defining custom styles with access to the theme                                                                                        |
 
 ## `className`
 
@@ -282,7 +282,7 @@ const UserList = () => (
 
 In addition to the root component, the `sx` prop also allows you to override the style of inner components. Refer to the documentation of each Field component to see the classes that you can override.
 
-And see [the MUI system documentation](https://mui.com/system/the-sx-prop/#main-content) for more information.
+And see [the Material UI system documentation](https://mui.com/system/the-sx-prop/) for more information.
 
 ## `textAlign`
 
diff --git a/docs/FileField.md b/docs/FileField.md
index b9fb741664f..434d028d23e 100644
--- a/docs/FileField.md
+++ b/docs/FileField.md
@@ -35,9 +35,9 @@ This field is also often used within a [`<FileInput />`](./FileInput.md) compone
 
 ## `sx`: CSS API
 
-The `<FileField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)).
+The `<FileField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)).
 
-To override the style of all instances of `<FileField>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaFileField` key.
+To override the style of all instances of `<FileField>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaFileField` key.
 
 ## Usage
 
diff --git a/docs/FileInput.md b/docs/FileInput.md
index 224e33a0f2a..0d2c48abf5c 100644
--- a/docs/FileInput.md
+++ b/docs/FileInput.md
@@ -154,14 +154,14 @@ If that's not enough, you can pass a `placeholder` prop to overwrite it. The val
 
 ## `sx`: CSS API
 
-The `<FileInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<FileInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                     | Description                                                                |
 |-------------------------------|----------------------------------------------------------------------------|
 | `& .RaFileInput-dropZone`     | Applied to the main container of the component                             |
-| `& .RaFileInput-removeButton` | Applied to each of the MUI's `IconButton` component used as remove button  |
+| `& .RaFileInput-removeButton` | Applied to each of the Material UI's `IconButton` component used as remove button  |
 
-To override the style of all instances of `<FileInput>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaFileInput` key.
+To override the style of all instances of `<FileInput>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaFileInput` key.
 
 ## `validateFileRemoval`
 
diff --git a/docs/IconMenu.md b/docs/IconMenu.md
index c87282d010e..cb807e4c89e 100644
--- a/docs/IconMenu.md
+++ b/docs/IconMenu.md
@@ -75,7 +75,7 @@ const App = () => (
 | Prop        | Required | Type        | Default  | Description                            |
 | ----------- | -------- | ----------- | -------- | -------------------------------------- |
 | `children`  | Optional | `ReactNode` | -        | The Menu Item Links to be rendered.    |
-| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by MUI System |
+| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by Material UI System |
 
 Additional props are passed down to the root `<div>` component.
 
@@ -116,7 +116,7 @@ export const MyMenu = () => (
 ```
 {% endraw %}
 
-To override the style of `<IconMenu>` using the [MUI style overrides](https://mui.com/customization/theme-components/), use the `RaMenuRoot` key.
+To override the style of `<IconMenu>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaMenuRoot` key.
 
 ## `<IconMenu.Item>`
 
@@ -141,13 +141,13 @@ It requires the following props:
 It accepts optional props:
 
 - `children`: Content of a sliding panel displayed when the menu is clicked (see [Adding sub menus](#adding-sub-menus) below)
-- `sx`: Style overrides, powered by MUI System
+- `sx`: Style overrides, powered by Material UI System
 
-Additional props are passed down to [the underling MUI `<listItem>` component](https://mui.com/api/list-item/#listitem-api).
+Additional props are passed down to [the underling Material UI `<listItem>` component](https://mui.com/material-ui/api/list-item/).
 
 ## Adding Sub Menus
 
-You can define the content of the sliding panel revealed when the user clicks on a menu by adding children to `<IconMenu.Item>`. `<IconMenu>` renders its children inside a MUI `<Card>`, so it's common to wrap the content in `<CardContent>`.
+You can define the content of the sliding panel revealed when the user clicks on a menu by adding children to `<IconMenu.Item>`. `<IconMenu>` renders its children inside a Material UI `<Card>`, so it's common to wrap the content in `<CardContent>`.
 
 For instance, here is how to add a sub menu to the Artists menu with one entry for each artist category:
 
diff --git a/docs/ImageField.md b/docs/ImageField.md
index 9e37b9fb71a..53770fe9707 100644
--- a/docs/ImageField.md
+++ b/docs/ImageField.md
@@ -82,7 +82,7 @@ The optional `title` prop points to the picture title property, used for both `a
 
 ## `sx`: CSS API
 
-The `<ImageField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<ImageField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name               | Description                                                                    |
 |-------------------------|--------------------------------------------------------------------------------|
@@ -100,4 +100,4 @@ For instance, to specify a size for the image:
 ```
 {% endraw %}
 
-To override the style of all instances of `<ImageField>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaImageField` key.
+To override the style of all instances of `<ImageField>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaImageField` key.
diff --git a/docs/ImageInput.md b/docs/ImageInput.md
index 4d86a21a1bc..4b9c4f28eee 100644
--- a/docs/ImageInput.md
+++ b/docs/ImageInput.md
@@ -151,11 +151,11 @@ If that's not enough, you can pass a `placeholder` prop to overwrite it. The val
 
 ## `sx`: CSS API
 
-The `<ImageInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<ImageInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                       | Description                                         |
 |---------------------------------|-----------------------------------------------------|
 | `& .RaFileInput-dropZone`      | Styles pass to the underlying `FileInput` component |
 | `& .RaFileInput-removeButton`  | Styles pass to the underlying `FileInput` component |
 
-To override the style of all instances of `<ImageInput>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaImageInput` key.
+To override the style of all instances of `<ImageInput>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaImageInput` key.
diff --git a/docs/Inputs.md b/docs/Inputs.md
index 38f36ccf9ae..51dcef8fd98 100644
--- a/docs/Inputs.md
+++ b/docs/Inputs.md
@@ -9,7 +9,7 @@ An `Input` component displays an input, or a dropdown list, a list of radio butt
 
 ![Inputs](./img/inputs.webp)
 
-Input components are usually wrappers around MUI form components, bound to the current react-hook-form context.
+Input components are usually wrappers around Material UI form components, bound to the current react-hook-form context.
 
 ## Usage
 
@@ -49,12 +49,12 @@ All input components accept the following props:
 | `helperText`    | Optional | `string`                  | -       | Text to be displayed under the input (cannot be used inside a filter)                                                                                                          |
 | `label`         | Optional | `string`                  | -       | Input label. In i18n apps, the label is passed to the `translate` function. Defaults to the humanized `source` when omitted. Set `label={false}` to hide the label. |
 | `parse`         | Optional | `Function`                | `value => value === '' ? null : value` | Callback taking the input value, and returning the value you want stored in the form state.                                                                         |
-| `sx`            | Optional | `SxProps`                 | -       | MUI shortcut for defining custom styles                                                                                                                             |
+| `sx`            | Optional | `SxProps`                 | -       | Material UI shortcut for defining custom styles                                                                                                                             |
 | `validate`      | Optional | `Function` &#124; `array` | -       | Validation rules for the current property. See the [Validation Documentation](./Validation.md#per-input-validation-built-in-field-validators) for details.          |
 
 React-admin uses [react-hook-form](https://react-hook-form.com/) to control form inputs. Each input component also accepts all react-hook-form [useController](https://react-hook-form.com/api/usecontroller) hook options.
 
-Additional props are passed down to the underlying component (usually an MUI component). For instance, when setting the `variant` prop on a `<TextInput>` component, the underlying MUI `<TextField>` receives it, and renders it with a different variant. Refer to the documentation of each Input component to see the underlying MUI component and its props.
+Additional props are passed down to the underlying component (usually an Material UI component). For instance, when setting the `variant` prop on a `<TextInput>` component, the underlying Material UI `<TextField>` receives it, and renders it with a different variant. Refer to the documentation of each Input component to see the underlying Material UI component and its props.
 
 ## Which Input Component to Use?
 
@@ -290,7 +290,7 @@ Then you can display a text input to edit the author's first name as follows:
 
 ## `sx`
 
-Each individual input supports an `sx` prop to pass custom styles to the underlying component, relying on [MUI system](https://mui.com/system/basics/#the-sx-prop).
+Each individual input supports an `sx` prop to pass custom styles to the underlying component, relying on [Material UI system](https://mui.com/system/basics/#the-sx-prop).
 
 {% raw %}
 ```jsx
@@ -570,9 +570,9 @@ import { FormDataConsumer } from 'react-admin';
 
 ## Overriding The Input Variant
 
-MUI offers [3 variants for text fields](https://mui.com/material-ui/react-text-field/#basic-textfield): `outlined`, `filled`, and `standard`. The default react-admin theme uses the `filled` variant.
+Material UI offers [3 variants for text fields](https://mui.com/material-ui/react-text-field/#basic-textfield): `outlined`, `filled`, and `standard`. The default react-admin theme uses the `filled` variant.
 
-Most Input components pass their additional props down to the root component, which is often an MUI Field component. This means you can pass a `variant` prop to override the variant of a single input:
+Most Input components pass their additional props down to the root component, which is often an Material UI Field component. This means you can pass a `variant` prop to override the variant of a single input:
 
 ```jsx
 <TextInput source="name" variant="outlined" />
@@ -735,9 +735,9 @@ Now the component will render with a label:
 </span>
 ```
 
-### Using MUI Field Components
+### Using Material UI Field Components
 
-Instead of HTML `input` elements, you can use an MUI component like `TextField`. To bind MUI components to the form values, use the `useController()` hook:
+Instead of HTML `input` elements, you can use an Material UI component like `TextField`. To bind Material UI components to the form values, use the `useController()` hook:
 
 ```jsx
 // in LatLongInput.js
@@ -768,13 +768,13 @@ const LatLngInput = () => (
 );
 ```
 
-**Tip**: MUI's `<TextField>` component already includes a label, so you don't need to use `<Labeled>` in this case.
+**Tip**: Material UI's `<TextField>` component already includes a label, so you don't need to use `<Labeled>` in this case.
 
 **Tip**: Notice that we have added `defaultValue: ''` as one of the `useController` params. This is a good practice to avoid getting console warnings about controlled/uncontrolled components, that may arise if the value of `record.lat` or `record.lng` is `undefined` or `null`.
 
 `useController()` returns three values: `field`, `fieldState`, and `formState`. To learn more about these props, please refer to the [useController](https://react-hook-form.com/api/usecontroller) hook documentation.
 
-Instead of HTML `input` elements or MUI components, you can use react-admin input components, like `<NumberInput>` for instance. React-admin components already use `useController()`, and already include a label, so you don't need either `useController()` or `<Labeled>` when using them:
+Instead of HTML `input` elements or Material UI components, you can use react-admin input components, like `<NumberInput>` for instance. React-admin components already use `useController()`, and already include a label, so you don't need either `useController()` or `<Labeled>` when using them:
 
 ```jsx
 // in LatLongInput.js
@@ -844,7 +844,7 @@ const LatLngInput = props => {
 };
 ```
 
-Here is another example, this time using an MUI `Select` component:
+Here is another example, this time using an Material UI `Select` component:
 
 ```jsx
 // in SexInput.js
diff --git a/docs/Labeled.md b/docs/Labeled.md
index a29e4c38c91..aeb55f6797e 100644
--- a/docs/Labeled.md
+++ b/docs/Labeled.md
@@ -80,12 +80,12 @@ const BookShow = () => (
 
 ## `sx`: CSS API
 
-The `<Labeled>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<Labeled>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                 | Description                                             |
 |---------------------------|---------------------------------------------------------|
 | `&.RaLabeled-fullWidth`   | Applied to the root component                           |
-| `& .RaLabeled-label`      | Applied to the underlying MUI's `Typography` component  |
+| `& .RaLabeled-label`      | Applied to the underlying Material UI's `Typography` component  |
 
 
-To override the style of all instances of `<Labeled>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaLabeled` key.
+To override the style of all instances of `<Labeled>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaLabeled` key.
diff --git a/docs/Layout.md b/docs/Layout.md
index 5a0e11a8a16..a2053869739 100644
--- a/docs/Layout.md
+++ b/docs/Layout.md
@@ -52,7 +52,7 @@ const App = () => (
 | `error`     | Optional | `Component` | -        | A React component rendered in the content area in case of error       |
 | `menu`      | Optional | `Component` | -        | A React component rendered at the side of the screen                  |
 | `sidebar`   | Optional | `Component` | -        | A React component responsible for rendering the menu (e.g. in a drawer) |
-| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by MUI System                                |
+| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by Material UI System                                |
 
 React-admin injects more props at runtime based on the `<Admin>` props:
 
@@ -232,11 +232,11 @@ React-admin provides alternative menu layouts that you can use as a base for you
 
 ![MegaMenu and Breadcrumb](https://marmelab.com/ra-enterprise/modules/assets/ra-multilevelmenu-categories.gif)
 
-And you can build a totally custom menu using [MUI's `<Menu>` component](https://mui.com/material-ui/react-menu/).
+And you can build a totally custom menu using [Material UI's `<Menu>` component](https://mui.com/material-ui/react-menu/).
 
 ## `sidebar`
 
-You can override the default sidebar using this prop. The default sidebar will display a permanent drawer when the window size is above MUI theme's `sm` breakpoint, and a temporary drawer when the window size is less than that.
+You can override the default sidebar using this prop. The default sidebar will display a permanent drawer when the window size is above Material UI theme's `sm` breakpoint, and a temporary drawer when the window size is less than that.
 
 If you wish to always display a temporary drawer, you can customize using the following sample code:
 
@@ -294,7 +294,7 @@ This property accepts the following subclasses:
 | `& .RaLayout-contentWithSidebar` | Applied to the main part containing the sidebar and the content                           |
 | `& .RaLayout-content`            | Applied to the content area                                                               |
 
-To override the style of `<Layout>` using the [MUI style overrides](https://mui.com/customization/theme-components/), use the `RaLayout` key.
+To override the style of `<Layout>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaLayout` key.
 
 **Tip**: If you need to override global styles (like the default font size or family), you should [write a custom theme](./Theming.md#theming) rather than override the `<Layout sx>` prop. And if you need to tweak the default layout to add a right column or move the menu to the top, you're probably better off [writing your own layout component](./Theming.md#layout-from-scratch). 
 
diff --git a/docs/List.md b/docs/List.md
index 7ea6957b71a..b687f5e0a0d 100644
--- a/docs/List.md
+++ b/docs/List.md
@@ -239,7 +239,7 @@ You can also pass React elements as children, to build a custom iterator. Check
 
 ## `component`
 
-By default, the List view renders the main content area inside a MUI `<Card>` element. The actual layout of the list depends on the child component you're using (`<Datagrid>`, `<SimpleList>`, or a custom layout component).
+By default, the List view renders the main content area inside a Material UI `<Card>` element. The actual layout of the list depends on the child component you're using (`<Datagrid>`, `<SimpleList>`, or a custom layout component).
 
 Some List layouts display each record in a `<Card>`, in which case the user ends up seeing a card inside a card, which is bad UI. To avoid that, you can override the main area container by passing a `component` prop:
 
@@ -819,7 +819,7 @@ The title can be either a string or an element of your own.
 
 ## `sx`: CSS API
 
-The `<List>` component accepts the usual `className` prop but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<List>` component accepts the usual `className` prop but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name             | Description                                                   |
 |-----------------------|---------------------------------------------------------------|
diff --git a/docs/ListTutorial.md b/docs/ListTutorial.md
index 608721f66a7..ce9716b8c9c 100644
--- a/docs/ListTutorial.md
+++ b/docs/ListTutorial.md
@@ -401,7 +401,7 @@ const Pagination = () => {
 
 ### `<List>` Renders Title, Filters, And Pagination
 
-`<ListBase>` is a headless component: it renders only its children. But almost every List view needs a wrapping `<div>`, a title, filters, pagination, a MUI `<Card>`, etc. That's why react-admin provides [the `<List>` component](./List.md), which includes the `<ListBase>` component and a "classic" layout to reduce the boilerplate even further:
+`<ListBase>` is a headless component: it renders only its children. But almost every List view needs a wrapping `<div>`, a title, filters, pagination, a Material UI `<Card>`, etc. That's why react-admin provides [the `<List>` component](./List.md), which includes the `<ListBase>` component and a "classic" layout to reduce the boilerplate even further:
 
 ```diff
 import { 
@@ -803,7 +803,7 @@ import {
 export const PaginationActions = props => (
     <RaPaginationActions
         {...props}
-        // these props are passed down to the MUI <Pagination> component
+        // these props are passed down to the Material UI <Pagination> component
         color="primary"
         showFirstButton
         showLastButton
@@ -824,4 +824,4 @@ export const UserList = () => (
 You can find more List components for react-admin in third-party repositories.
 
 - [ra-customizable-datagrid](https://github.com/fizix-io/ra-customizable-datagrid): plugin that allows to hide / show columns dynamically.
-- [ra-datagrid](https://github.com/marmelab/ra-datagrid): Integration of [MUI's `<Datagrid>`](https://mui.com/components/data-grid/) into react-admin.
+- [ra-datagrid](https://github.com/marmelab/ra-datagrid): Integration of [Material UI's `<Datagrid>`](https://mui.com/components/data-grid/) into react-admin.
diff --git a/docs/LocalesMenuButton.md b/docs/LocalesMenuButton.md
index 37f7e17c4cd..6f3bfa50a48 100644
--- a/docs/LocalesMenuButton.md
+++ b/docs/LocalesMenuButton.md
@@ -13,7 +13,7 @@ The `<LocalesMenuButton>` component, also known as the "language switcher", disp
 
 **Tip**: For most users, this component will be automatically added to react-admin's `<AppBar>` if the `i18nProvider` is configured properly to return a list of available locales. React-admin will use the optional `getLocales` method of your `i18nProvider` (or the `availableLocales` parameter if you are using `polyglotI18nProvider`) to generate a list of locale menu items for this component.
 
-For advanced users who wish to use the customized `<AppBar>` from MUI package or place `<LocalesMenuButton>` elsewhere e.g. on a custom configuration page, they can do the following:
+For advanced users who wish to use the customized `<AppBar>` from Material UI package or place `<LocalesMenuButton>` elsewhere e.g. on a custom configuration page, they can do the following:
 
 ```jsx
 // in src/MyAppBar.js
@@ -75,9 +75,9 @@ The `locale` will be passed to `setLocale` when the user selects the language, a
 
 ## `sx`: CSS API
 
-The `<LocalesMenuButton>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)).
+The `<LocalesMenuButton>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)).
 
-To override the style of all instances of `<LocalesMenuButton>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaLocalesMenuButton` key.
+To override the style of all instances of `<LocalesMenuButton>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaLocalesMenuButton` key.
 
 ## API
 
diff --git a/docs/LongForm.md b/docs/LongForm.md
index 22a1c775380..a6af286531e 100644
--- a/docs/LongForm.md
+++ b/docs/LongForm.md
@@ -141,7 +141,7 @@ The `<LongForm>` component accepts the usual `className` prop. You can also over
 
 The children of `<LongForm>` must be `<LongForm.Section>` elements.
 
-This component adds a section title (using a `<Typography variant="h4">`), then renders each child inside a [MUI `<Stack>`](https://mui.com/material-ui/react-stack/), and finally adds an MUI `<Divider>` at the bottom of the section.
+This component adds a section title (using a `<Typography variant="h4">`), then renders each child inside a [Material UI `<Stack>`](https://mui.com/material-ui/react-stack/), and finally adds an Material UI `<Divider>` at the bottom of the section.
 
 It accepts the following props:
 
@@ -150,7 +150,7 @@ It accepts the following props:
 | `label`           | Required | `string`    | -       | The main label used as the section title. Appears in red when the section has errors |
 | `children`        | Required | `ReactNode` | -       | A list of `<Input>` elements                                                         |
 | `cardinality`     | Optional | `number`    | -       | A number to be displayed next to the label in TOC, to quantify it                    |
-| `sx`              | Optional | `object`    | -       | An object containing the MUI style overrides to apply to the root component          |
+| `sx`              | Optional | `object`    | -       | An object containing the Material UI style overrides to apply to the root component          |
 
 ### `cardinality`
 
diff --git a/docs/Menu.md b/docs/Menu.md
index f59c7f68877..e6087c1dddb 100644
--- a/docs/Menu.md
+++ b/docs/Menu.md
@@ -60,9 +60,9 @@ const App = () => (
 | Prop        | Required | Type        | Default  | Description                                                                          |
 | ----------- | -------- | ----------- | -------- | ------------------------------------------------------------------------------------ |
 | `children`  | Optional | `ReactNode` | -        | The Menu Item Links to be rendered. If not provided, defaults to the Resource names. |
-| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by MUI System                                               |
+| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by Material UI System                                               |
 
-Additional props are passed down to the root component (the MUI [`<MenuList>`](https://mui.com/material-ui/api/menu-list/) component)
+Additional props are passed down to the root component (the Material UI [`<MenuList>`](https://mui.com/material-ui/api/menu-list/) component)
 
 ## `children`
 
@@ -135,7 +135,7 @@ This property accepts the following subclasses:
 | `&.RaMenu-open`   | Applied the menu when it's open      |
 | `&.RaMenu-closed` | Applied to the menu when it's closed |
 
-To override the style of `<Menu>` using the [MUI style overrides](https://mui.com/customization/theme-components/), use the `RaMenu` key.
+To override the style of `<Menu>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaMenu` key.
 
 ## `<Menu.Item>`
 
@@ -155,7 +155,7 @@ import Badge from '@mui/material/Badge';
 
 The `letfIcon` prop allows setting the menu left icon.
 
-Additional props are passed down to [the underling MUI `<MenuItem>` component](https://mui.com/api/menu-item/#menuitem-api).
+Additional props are passed down to [the underling Material UI `<MenuItem>` component](https://mui.com/material-ui/api/menu-item/).
 
 **Tip**: The `<Menu.Item>` component makes use of the React Router [NavLink](https://reactrouter.com/docs/en/v6/components/nav-link) component, hence allowing to customize the active menu style. For instance, here is how to use a custom theme to show a left border for the active menu:
 
diff --git a/docs/MenuLive.md b/docs/MenuLive.md
index 5c4ead399f7..63467197ffe 100644
--- a/docs/MenuLive.md
+++ b/docs/MenuLive.md
@@ -68,7 +68,7 @@ const CustomMenuLive = () => (
 `<MenuLiveItemLink>` has two additional props compared to `<MenuItemLink>`:
 
 -   `resource`: Needed, The name of the concerned resource (can be different from the path in the `to` prop)
--   `badgeColor`: Optional, It's the MUI color used to display the color of the badge. The default is `alert` (not far from the red). It can also be `primary`, `secondary`, or any of the MUI colors available in the [MUI palette](https://material-ui.com/customization/palette/).
+-   `badgeColor`: Optional, It's the Material UI color used to display the color of the badge. The default is `alert` (not far from the red). It can also be `primary`, `secondary`, or any of the Material UI colors available in the [Material UI palette](https://material-ui.com/customization/palette/).
 
 The badge displays the total number of changed records since the last time the `<MenuItem>` opened. The badge value resets whenever the user opens the resource list page, and the `<MenuItem>` becomes active.
 
diff --git a/docs/MultiLevelMenu.md b/docs/MultiLevelMenu.md
index 710ac5ea566..3c06074892b 100644
--- a/docs/MultiLevelMenu.md
+++ b/docs/MultiLevelMenu.md
@@ -111,7 +111,7 @@ const App = () => (
 | ------------- | -------- | ----------- | -------- | -------------------------------------- |
 | `children`    | Optional | `ReactNode` | -        | The Menu Items  to be rendered.        |
 | `initialOpen` | Optional | `boolean`   | `false`  | Whether the menu is initially open.    |
-| `sx`          | Optional | `SxProps`   | -        | Style overrides, powered by MUI System |
+| `sx`          | Optional | `SxProps`   | -        | Style overrides, powered by Material UI System |
 
 Additional props are passed down to the root `<div>` component.
 
@@ -164,7 +164,7 @@ export const MyMenu = () => (
 ```
 {% endraw %}
 
-To override the style of `<MultiLevelMenu>` using the [MUI style overrides](https://mui.com/customization/theme-components/), use the `RaMenuRoot` key.
+To override the style of `<MultiLevelMenu>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaMenuRoot` key.
 
 ## `<MultiLevelMenu.Item>`
 
@@ -189,9 +189,9 @@ It accepts optional props:
 
 - `icon`: the icon to display.
 - `children`: Other `<MultiLevelMenu.Item>` children.
-- `sx`: Style overrides, powered by MUI System
+- `sx`: Style overrides, powered by Material UI System
 
-Additional props are passed down to [the underling MUI `<listItem>` component](https://mui.com/api/list-item/#listitem-api).
+Additional props are passed down to [the underling Material UI `<listItem>` component](https://mui.com/api/list-item/#listitem-api).
 
 ## Creating Menu Items For Resources
 
diff --git a/docs/NullableBooleanInput.md b/docs/NullableBooleanInput.md
index cda7f5435fd..5d6ad1a9fb6 100644
--- a/docs/NullableBooleanInput.md
+++ b/docs/NullableBooleanInput.md
@@ -23,13 +23,13 @@ import { NullableBooleanInput } from 'react-admin';
 
 ## `sx`: CSS API
 
-The `<NullableBooleanInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<NullableBooleanInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                         | Description                                                   |
 |-----------------------------------|---------------------------------------------------------------|
-| `& .RaNullableBooleanInput-input` | Applied to the underlying MUI's `TextField` component |
+| `& .RaNullableBooleanInput-input` | Applied to the underlying Material UI's `TextField` component |
 
-To override the style of all instances of `<NullableBooleanInput>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaNullableBooleanInput` key.
+To override the style of all instances of `<NullableBooleanInput>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaNullableBooleanInput` key.
 
 ## Translation
 
diff --git a/docs/RadioButtonGroupInput.md b/docs/RadioButtonGroupInput.md
index 33c01a655f3..329cd0538b6 100644
--- a/docs/RadioButtonGroupInput.md
+++ b/docs/RadioButtonGroupInput.md
@@ -5,7 +5,7 @@ title: "The RadioButtonGroupInput Component"
 
 # `<RadioButtonGroupInput>`
 
-If you want to let the user choose a value among a list of possible values that are always shown, `<RadioButtonGroupInput>` is the right component. It renders using [MUI's `<RadioGroup>`](https://mui.com/material-ui/react-radio-button/).
+If you want to let the user choose a value among a list of possible values that are always shown, `<RadioButtonGroupInput>` is the right component. It renders using [Material UI's `<RadioGroup>`](https://mui.com/material-ui/react-radio-button/).
 
 ![RadioButtonGroupInput](./img/radio-button-group-input.gif)
 
@@ -145,7 +145,7 @@ const UserCountry = () => {
 
 ## `options`
 
-Use the `options` attribute if you want to override any of MUI's `<RadioGroup>` attributes:
+Use the `options` attribute if you want to override any of Material UI's `<RadioGroup>` attributes:
 
 {% raw %}
 ```jsx
@@ -156,7 +156,7 @@ Use the `options` attribute if you want to override any of MUI's `<RadioGroup>`
 ```
 {% endraw %}
 
-Refer to [MUI RadioGroup documentation](https://mui.com/api/radio-group) for more details.
+Refer to [Material UI RadioGroup documentation](https://mui.com/api/radio-group) for more details.
 
 ## `optionText`
 
@@ -243,13 +243,13 @@ By default, the radio buttons are displayed in a row. You can change that and le
 
 ## `sx`: CSS API
 
-The `<RadioButtonGroupInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<RadioButtonGroupInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                          | Description                                                   |
 |------------------------------------|---------------------------------------------------------------|
-| `& .RaRadioButtonGroupInput-label` | Applied to the underlying MUI's `FormLabel` component |
+| `& .RaRadioButtonGroupInput-label` | Applied to the underlying Material UI's `FormLabel` component |
 
-To override the style of all instances of `<RadioButtonGroupInput>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaRadioButtonGroupInput` key.
+To override the style of all instances of `<RadioButtonGroupInput>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaRadioButtonGroupInput` key.
 
 ## `translateChoice`
 
diff --git a/docs/Readme.md b/docs/Readme.md
index 2710504d0ae..bfcaae4aba4 100644
--- a/docs/Readme.md
+++ b/docs/Readme.md
@@ -51,7 +51,7 @@ render(
 );
 ```
 
-The `<Resource>` component is a configuration component that allows defining sub components for each of the admin view: `list`, `edit`, and `create`. These components use MUI and custom components from react-admin:
+The `<Resource>` component is a configuration component that allows defining sub components for each of the admin view: `list`, `edit`, and `create`. These components use Material UI and custom components from react-admin:
 
 {% raw %}
 ```jsx
@@ -119,7 +119,7 @@ See the [Data Providers documentation](./DataProviders.md) for details.
 
 ## Architecture: Batteries Included But Removable
 
-React-admin is designed as a library of loosely coupled React components built on top of [MUI](https://mui.com/), in addition to React hooks allowing to reuse the logic with a custom UI. 
+React-admin is designed as a library of loosely coupled React components built on top of [Material UI](https://mui.com/material-ui/getting-started/overview/), in addition to React hooks allowing to reuse the logic with a custom UI. 
 
 You may replace one part of react-admin with your own, e.g. to use a custom Datagrid, GraphQL instead of REST, or Bootstrap instead of Material Design.
 
@@ -142,7 +142,7 @@ The [React-Admin Enterprise Edition](https://marmelab.com/ra-enterprise) <img cl
   - `ra-form-layout`: New form layouts for complex data entry tasks (accordion, wizard, etc.)
   - `ra-relationships`: Visualize and edit complex relationships, including many-to-many relationships.
   - `ra-tree`: Edit and visualize tree structures. Reorganize by drag and drop. Adapts to any data structure on the backend (parent_id, children, nested sets, etc.).
-  - `ra-tour`: Guided tours for react-admin applications. Step-by-step instructions, MUI skin.
+  - `ra-tour`: Guided tours for react-admin applications. Step-by-step instructions, Material UI skin.
   - `ra-markdown`: Read Markdown data, and edit it using a WYSIWYG editor in your admin
 - Get **Support** from experienced react and react-admin developers, who will help you find the right information and troubleshoot your bugs.
 - Get a **50% Discount on Professional Services** in case you need coaching, audit, or custom development by our experts.
diff --git a/docs/ReferenceArrayField.md b/docs/ReferenceArrayField.md
index 37f830b634c..4b22c067105 100644
--- a/docs/ReferenceArrayField.md
+++ b/docs/ReferenceArrayField.md
@@ -246,11 +246,11 @@ For instance, to sort tags by title in ascending order, you can use the followin
 
 ## `sx`: CSS API
 
-The `<ReferenceArrayField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<ReferenceArrayField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                           | Description                                                                              |
 |-------------------------------------|------------------------------------------------------------------------------------------|
-| `& .RaReferenceArrayField-progress` | Applied to the MUI's `LinearProgress` component while `isLoading` prop is `true` |
+| `& .RaReferenceArrayField-progress` | Applied to the Material UI's `LinearProgress` component while `isLoading` prop is `true` |
 
-To override the style of all instances of `<ReferenceArrayField>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaReferenceArrayField` key.
+To override the style of all instances of `<ReferenceArrayField>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaReferenceArrayField` key.
 
diff --git a/docs/ReferenceField.md b/docs/ReferenceField.md
index 977fb824ef5..c4861fd620c 100644
--- a/docs/ReferenceField.md
+++ b/docs/ReferenceField.md
@@ -163,13 +163,13 @@ By default, when used in a `<Datagrid>`, and when the user clicks on the column
 
 ## `sx`: CSS API
 
-The `<ReferenceField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<ReferenceField>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                  | Description                   |
 |----------------------------|-------------------------------|
 | `& .RaReferenceField-link` | Applied to each child element |
 
-To override the style of all instances of `<ReferenceField>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaReferenceField` key.
+To override the style of all instances of `<ReferenceField>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaReferenceField` key.
 
 ## Rendering More Than One Field
 
diff --git a/docs/ReferenceManyCount.md b/docs/ReferenceManyCount.md
index d265862ab6f..8d1e35d9c52 100644
--- a/docs/ReferenceManyCount.md
+++ b/docs/ReferenceManyCount.md
@@ -72,7 +72,7 @@ export const PostList = () => (
 
 `<ReferenceManyCount>` also accepts the [common field props](./Fields.md#common-field-props).
 
-Additional props are passed to [the underlying MUI `<Typography>` element](https://mui.com/material-ui/api/typography/).
+Additional props are passed to [the underlying Material UI `<Typography>` element](https://mui.com/material-ui/api/typography/).
 
 ## `filter`
 
diff --git a/docs/ReferenceManyInput.md b/docs/ReferenceManyInput.md
index 31e2e839b9d..668b9b43d1c 100644
--- a/docs/ReferenceManyInput.md
+++ b/docs/ReferenceManyInput.md
@@ -81,7 +81,7 @@ const ProductEdit = () => (
 | `sort`         | Optional | `{ field, order }`        | `{ field: 'id', order: 'DESC' }` | Sort order to use when fetching the related records, passed to `getManyReference()`                                                                                 |
 | `defaultValue` | Optional | `array`                   | -                                | Default value of the input.                                                                                                                                         |
 | `validate`     | Optional | `Function` &#124; `array` | -                                | Validation rules for the array. See the [Validation Documentation](./Validation.md) for details.                                   |
-| `sx`           | Optional | `SxProps`                 | -                                | MUI shortcut for defining custom styles                                                                                                                             |
+| `sx`           | Optional | `SxProps`                 | -                                | Material UI shortcut for defining custom styles                                                                                                                             |
 
 ## `children`
 
@@ -236,7 +236,7 @@ By default, `<ReferenceManyInput>` ferchers the `references` for which the `targ
 
 ## `sx`
 
-You can override the style of the root component (a MUI [`<FormControl>`](https://mui.com/material-ui/api/form-control/#main-content)) and its child components by setting the `sx` prop.
+You can override the style of the root component (a Material UI [`<FormControl>`](https://mui.com/material-ui/api/form-control/)) and its child components by setting the `sx` prop.
 
 {% raw %}
 
diff --git a/docs/ReferenceOneInput.md b/docs/ReferenceOneInput.md
index 54c7a292739..1962c874910 100644
--- a/docs/ReferenceOneInput.md
+++ b/docs/ReferenceOneInput.md
@@ -77,13 +77,13 @@ const BookEdit = () => (
 | `filter`       | Optional | `Object`                  | -                                | Filters to use when fetching the related record, passed to `getManyReference()`                                                                                        |
 | `sort`         | Optional | `{ field, order }`        | `{ field: 'id', order: 'ASC' }`  | Sort order to use when fetching the related record, passed to `getManyReference()`                                                                                     |
 | `defaultValue` | Optional | `Object`                  | -                                | Default value for the related record (in case it does not yet exist)                                                                                                   |
-| `sx`           | Optional | `SxProps`                 | -                                | MUI shortcut for defining custom styles                                                                                                                                |
+| `sx`           | Optional | `SxProps`                 | -                                | Material UI shortcut for defining custom styles                                                                                                                                |
 
-Additional props are passed to the MUI `<Stack>` component.
+Additional props are passed to the Material UI `<Stack>` component.
 
 ## `children`
 
-`<ReferenceOneInput>` expects input components as its children (like `<TextInput>`, `<NumberInput>`, etc.), which will allow to edit the related record. The inputs will be rendered inside an [MUI `<Stack>`](https://mui.com/material-ui/react-stack/).
+`<ReferenceOneInput>` expects input components as its children (like `<TextInput>`, `<NumberInput>`, etc.), which will allow to edit the related record. The inputs will be rendered inside an [Material UI `<Stack>`](https://mui.com/material-ui/react-stack/).
 
 ```jsx
 <ReferenceOneInput reference="book_details" target="book_id">
@@ -205,7 +205,7 @@ By default, `<ReferenceManyInput>` fetches the `reference` for which the `target
 
 ## `sx`
 
-You can override the style of the root component (a MUI [`<FormControl>`](https://mui.com/material-ui/api/form-control/#main-content)) and its child components by setting the `sx` prop.
+You can override the style of the root component (a Material UI [`<FormControl>`](https://mui.com/material-ui/api/form-control/)) and its child components by setting the `sx` prop.
 
 {% raw %}
 
diff --git a/docs/SaveButton.md b/docs/SaveButton.md
index e1136fb47db..01b65e218af 100644
--- a/docs/SaveButton.md
+++ b/docs/SaveButton.md
@@ -55,7 +55,7 @@ const PostEdit = () => (
 - [`transform`](#transform)
 - [`type`](#type)
 
-Additional props (e.g. `color`, `variant`) are passed to [the underlying MUI `<Button>` component](https://mui.com/components/buttons/).
+Additional props (e.g. `color`, `variant`) are passed to [the underlying Material UI `<Button>` component](https://mui.com/components/buttons/).
 
 ## `icon`
 
@@ -223,7 +223,7 @@ const MyToolbar = () => (
 
 ## `sx`: CSS API
 
-The `<SaveButton>` components accept the usual `className` prop, but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)).
+The `<SaveButton>` components accept the usual `className` prop, but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)).
 
 {% raw %}
 ```jsx
@@ -235,7 +235,7 @@ const PostCreateToolbar = () => (
 ```
 {% endraw %}
 
-To override the style of all instances of `<SaveButton>` components using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaSaveButton` key.
+To override the style of all instances of `<SaveButton>` components using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaSaveButton` key.
 
 ## `transform`
 
diff --git a/docs/SelectArrayInput.md b/docs/SelectArrayInput.md
index 32af158f3db..ada4fba7665 100644
--- a/docs/SelectArrayInput.md
+++ b/docs/SelectArrayInput.md
@@ -5,7 +5,7 @@ title: "The SelectArrayInput Component"
 
 # `<SelectArrayInput>`
 
-To let users choose several values in a list using a dropdown, use `<SelectArrayInput>`. It renders using [MUI's `<Select>`](https://mui.com/api/select).
+To let users choose several values in a list using a dropdown, use `<SelectArrayInput>`. It renders using [Material UI's `<Select>`](https://mui.com/api/select).
 
 ![SelectArrayInput](./img/select-array-input.gif)
 
@@ -278,7 +278,7 @@ If a prompt is not enough, you can use [the `create` prop](#create) to render a
 
 ## `options`
 
-Use the `options` attribute if you want to override any of MUI's `<Select>` attributes:
+Use the `options` attribute if you want to override any of Material UI's `<Select>` attributes:
 
 {% raw %}
 ```jsx
@@ -286,7 +286,7 @@ Use the `options` attribute if you want to override any of MUI's `<Select>` attr
 ```
 {% endraw %}
 
-Refer to [MUI Select documentation](https://mui.com/api/select) for more details.
+Refer to [Material UI Select documentation](https://mui.com/api/select) for more details.
 
 ## `optionText`
 
@@ -354,14 +354,14 @@ const choices = [
 
 ## `sx`: CSS API
 
-The `<SelectArrayInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<SelectArrayInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                     | Description                                                                        |
 |-------------------------------|------------------------------------------------------------------------------------|
-| `& .RaSelectArrayInput-chip`  | Applied to each MUI's `Chip` component used as selected item               |
-| `& .RaSelectArrayInput-chips` | Applied to the container of MUI's `Chip` components used as selected items |
+| `& .RaSelectArrayInput-chip`  | Applied to each Material UI's `Chip` component used as selected item               |
+| `& .RaSelectArrayInput-chips` | Applied to the container of Material UI's `Chip` components used as selected items |
 
-To override the style of all instances of `<SelectArrayInput>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaSelectArrayInput` key.
+To override the style of all instances of `<SelectArrayInput>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaSelectArrayInput` key.
 
 ## `translateChoice`
 
@@ -452,7 +452,7 @@ const PostCreate = () => {
 ```
 {% endraw %}
 
-Use the `create` prop when you want a more polished or complex UI. For example a MUI `<Dialog>` asking for multiple fields because the choices are from a referenced resource.
+Use the `create` prop when you want a more polished or complex UI. For example a Material UI `<Dialog>` asking for multiple fields because the choices are from a referenced resource.
 
 {% raw %}
 ```jsx
diff --git a/docs/SelectInput.md b/docs/SelectInput.md
index 499e6c86de5..2c685f93bbb 100644
--- a/docs/SelectInput.md
+++ b/docs/SelectInput.md
@@ -5,7 +5,7 @@ title: "The SelectInput Component"
 
 # `<SelectInput>`
 
-To let users choose a value in a list using a dropdown, use `<SelectInput>`. It renders using [MUI's `<Select>`](https://mui.com/api/select).
+To let users choose a value in a list using a dropdown, use `<SelectInput>`. It renders using [Material UI's `<Select>`](https://mui.com/api/select).
 
 ![SelectInput](./img/select-input.gif)
 
@@ -334,7 +334,7 @@ If a prompt is not enough, you can use [the `create` prop](#create) to render a
 
 ## `options`
 
-Use the `options` attribute if you want to override any of MUI's `<Select>` attributes:
+Use the `options` attribute if you want to override any of Material UI's `<Select>` attributes:
 
 {% raw %}
 ```jsx
@@ -342,7 +342,7 @@ Use the `options` attribute if you want to override any of MUI's `<Select>` attr
 ```
 {% endraw %}
 
-Refer to [MUI Select documentation](https://mui.com/api/select) for more details.
+Refer to [Material UI Select documentation](https://mui.com/api/select) for more details.
 
 ## `optionText`
 
@@ -455,13 +455,13 @@ You can make the `SelectInput` component resettable using the `resettable` prop.
 
 ## `sx`: CSS API
 
-The `<SelectInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<SelectInput>` component accepts the usual `className` prop. You can also override many styles of the inner components thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                | Description                                               |
 |--------------------------|-----------------------------------------------------------|
 | `& .RaSelectInput-input` | Applied to the underlying `ResettableTextField` component |
 
-To override the style of all instances of `<SelectInput>` using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaSelectInput` key.
+To override the style of all instances of `<SelectInput>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaSelectInput` key.
 
 ## `translateChoice`
 
@@ -626,7 +626,7 @@ const PostCreate = () => {
 ```
 {% endraw %}
 
-Use the `create` prop when you want a more polished or complex UI. For example an MUI `<Dialog>` asking for multiple fields because the choices are from a referenced resource.
+Use the `create` prop when you want a more polished or complex UI. For example an Material UI `<Dialog>` asking for multiple fields because the choices are from a referenced resource.
 
 {% raw %}
 ```jsx
diff --git a/docs/Show.md b/docs/Show.md
index 798b3827d35..2037266f5aa 100644
--- a/docs/Show.md
+++ b/docs/Show.md
@@ -11,7 +11,7 @@ The `<Show>` component handles the logic of the Show page:
 - it computes the default page title
 - it creates a `ShowContext` and a `RecordContext`,
 - it renders the page layout with the correct title and actions
-- it renders its child component (a show layout component like `<SimpleShowLayout>`) in a MUI `<Card>`
+- it renders its child component (a show layout component like `<SimpleShowLayout>`) in a Material UI `<Card>`
 
 ## Usage
 
@@ -261,7 +261,7 @@ The default `onError` function is:
 
 ## `component`
 
-By default, the Show view renders the main content area inside a MUI `<Card>`. The actual layout of the record fields depends on the Show Layout component you're using (`<SimpleShowLayout>`, `<TabbedShowLayout>`, or a custom layout component).
+By default, the Show view renders the main content area inside a Material UI `<Card>`. The actual layout of the record fields depends on the Show Layout component you're using (`<SimpleShowLayout>`, `<TabbedShowLayout>`, or a custom layout component).
 
 You can override the main area container by passing a `component` prop:
 
@@ -300,7 +300,7 @@ const PostShow = () => (
 
 ## `sx`: CSS API
 
-The `<Show>` component accepts the usual `className` prop but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<Show>` component accepts the usual `className` prop but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name        | Description                                                   |
 |------------------| ------------------------------------------------------------- |
@@ -326,7 +326,7 @@ const PostShow = () => (
 ```
 {% endraw %}
 
-To override the style of all instances of `<Show>` using the [MUI style overrides](https://mui.com/customization/theme-components/), use the `RaShow` key.
+To override the style of all instances of `<Show>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaShow` key.
 
 ## Loading State
 
diff --git a/docs/ShowTutorial.md b/docs/ShowTutorial.md
index 92e720c64ba..ec19c90e501 100644
--- a/docs/ShowTutorial.md
+++ b/docs/ShowTutorial.md
@@ -388,7 +388,7 @@ const BookShow = () => (
 
 In many cases, neither the `<SimpleShowLayout>` nor the `<TabbedShowLayout>` components are enough to display the fields you want. In these cases, pass your layout components directly as children of the `<Show>` component. As `<Show>` takes care of fetching the record and putting it in a `<RecordContextProvider>`, you can use Field components directly. 
 
-For instance, to display several fields in a single line, you can use MUI's `<Grid>` component:
+For instance, to display several fields in a single line, you can use Material UI's `<Grid>` component:
 
 {% raw %}
 ```jsx
diff --git a/docs/SimpleForm.md b/docs/SimpleForm.md
index 059bf264c05..98ec6f3e32f 100644
--- a/docs/SimpleForm.md
+++ b/docs/SimpleForm.md
@@ -11,7 +11,7 @@ The `<SimpleForm>` creates a `<form>` to edit a record, and renders its children
 
 ## Usage
 
-`<SimpleForm>` reads the `record` from the `RecordContext`, uses it to initialize the defaultValues of a `<Form>`, renders its children in a MUI `<Stack>`, and renders a toolbar with a `<SaveButton>` that calls the `save` callback prepared by the edit or the create controller when pressed. 
+`<SimpleForm>` reads the `record` from the `RecordContext`, uses it to initialize the defaultValues of a `<Form>`, renders its children in a Material UI `<Stack>`, and renders a toolbar with a `<SaveButton>` that calls the `save` callback prepared by the edit or the create controller when pressed. 
 
 `<SimpleForm>` is often used as child of `<Create>` or `<Edit>`. It accepts Input and Field components as children. It relies on [react-hook-form](https://react-hook-form.com/) for form handling. It requires no prop by default.
 
@@ -55,7 +55,7 @@ const formState = useFormState(); // ❌ should deconstruct the formState
 
 ## `component`
 
-`<SimpleForm>` renders a MUI `<CardContent>` by default. You replace it by any component you want as wrapper, just pass it as the `component` prop.
+`<SimpleForm>` renders a Material UI `<CardContent>` by default. You replace it by any component you want as wrapper, just pass it as the `component` prop.
 
 ```jsx
 const PostCreate = () => (
diff --git a/docs/SimpleFormIterator.md b/docs/SimpleFormIterator.md
index 18eb947e0c1..d654db8730c 100644
--- a/docs/SimpleFormIterator.md
+++ b/docs/SimpleFormIterator.md
@@ -81,7 +81,7 @@ const OrderEdit = () => (
 | `inline` | Optional | `boolean` | `false` | When true, inputs are put on the same line |
 | `removeButton` | Optional | `ReactElement` | - | Component to render for the remove button |
 | `reOrderButtons` | Optional | `ReactElement` | - | Component to render for the up / down button |
-| `sx` | Optional | `SxProps` | - | MUI shortcut for defining custom styles |
+| `sx` | Optional | `SxProps` | - | Material UI shortcut for defining custom styles |
 
 ## `addButton`
 
@@ -349,7 +349,7 @@ const OrderEdit = () => (
 
 ## `sx`
 
-You can override the style of the root element (a `<div>` element) as well as those of the inner components thanks to the `sx` property. It relies on MUI System and supports CSS and shorthand properties (see [their documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)).
+You can override the style of the root element (a `<div>` element) as well as those of the inner components thanks to the `sx` property. It relies on Material UI System and supports CSS and shorthand properties (see [their documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)).
 
 This property accepts the following subclasses:
 
diff --git a/docs/SimpleList.md b/docs/SimpleList.md
index af167f49551..0f6c02f6e5f 100644
--- a/docs/SimpleList.md
+++ b/docs/SimpleList.md
@@ -7,7 +7,7 @@ title: "The SimpleList Component"
 
 <a href="./img/simple-list.gif"><img src="./img/simple-list.gif" style="height:300px" alt="The `<SimpleList>` component" /></a>
 
-For mobile devices, a `<Datagrid>` is often unusable - there is simply not enough space to display several columns. The convention in that case is to use a simple list, with only one column per row. The `<SimpleList>` component serves that purpose, leveraging [MUI's `<List>` and `<ListItem>` components](https://mui.com/components/lists/). 
+For mobile devices, a `<Datagrid>` is often unusable - there is simply not enough space to display several columns. The convention in that case is to use a simple list, with only one column per row. The `<SimpleList>` component serves that purpose, leveraging [Material UI's `<List>` and `<ListItem>` components](https://mui.com/components/lists/). 
 
 `<SimpleList>` is an **iterator** component: it gets an array of ids and a data store from the `ListContext`, and iterates over the ids to display each record.
 
@@ -201,7 +201,7 @@ const PostList = () => (
 
 ## Using `<SimpleList>` On Small Screens
 
-To use `<SimpleList>` on small screens and a `<Datagrid>` on larger screens, use MUI's `useMediaQuery` hook:
+To use `<SimpleList>` on small screens and a `<Datagrid>` on larger screens, use Material UI's `useMediaQuery` hook:
 
 ```jsx
 import { useMediaQuery } from '@mui/material';
diff --git a/docs/SimpleShowLayout.md b/docs/SimpleShowLayout.md
index f5a64a1cf99..d831f0b3283 100644
--- a/docs/SimpleShowLayout.md
+++ b/docs/SimpleShowLayout.md
@@ -5,7 +5,7 @@ title: "SimpleShowLayout"
 
 # `<SimpleShowLayout>`
 
-The `<SimpleShowLayout>` pulls the `record` from the `RecordContext`. It renders the record fields in a single-column layout (via MUI's `<Stack>` component). `<SimpleShowLayout>` delegates the actual rendering of fields to its children. It wraps each field inside [a `<Labeled>` component](./Labeled.md) to add a label.
+The `<SimpleShowLayout>` pulls the `record` from the `RecordContext`. It renders the record fields in a single-column layout (via Material UI's `<Stack>` component). `<SimpleShowLayout>` delegates the actual rendering of fields to its children. It wraps each field inside [a `<Labeled>` component](./Labeled.md) to add a label.
 
 ## Usage
 
@@ -123,7 +123,7 @@ const PostShow = () => (
 
 ## Spacing
 
-`<SimpleShowLayout>` renders a MUI `<Stack>`. You can customize the spacing of each row by passing a `spacing` prop:
+`<SimpleShowLayout>` renders a Material UI `<Stack>`. You can customize the spacing of each row by passing a `spacing` prop:
 
 ```jsx
 const PostShow = () => (
@@ -197,14 +197,14 @@ When passed a `record`, `<SimpleShowLayout>` creates a `RecordContext` with the
 
 ## `sx`: CSS API
 
-The `<SimpleShowLayout>` component accepts the usual `className` prop but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<SimpleShowLayout>` component accepts the usual `className` prop but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                     | Description                                             |
 |-------------------------------|---------------------------------------------------------|
 | `& .RaSimpleShowLayout-stack` | Applied to the `<Stack>` element                        |
 | `& .RaSimpleShowLayout-row`   | Applied to each child of the stack (i.e. to each field) |
 
-To override the style of all instances of `<SimpleShowLayout>` using the [MUI style overrides](https://mui.com/customization/theme-components/), use the `RaSimpleShowLayout` key.
+To override the style of all instances of `<SimpleShowLayout>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaSimpleShowLayout` key.
 
 ## See Also
 
diff --git a/docs/SingleFieldList.md b/docs/SingleFieldList.md
index 2c849ccfe57..b971c046f1a 100644
--- a/docs/SingleFieldList.md
+++ b/docs/SingleFieldList.md
@@ -94,4 +94,4 @@ The `<SingleFieldList>` component accepts the usual `className` prop. You can al
 |-----------------------------|-------------------------|
 | `& .RaSingleFieldList-link` | Applied to each link    |
 
-**Tip**: You can override these classes for all `<SingleFieldList>` instances by overriding them in a MUI theme, using the key "RaSingleFieldList".
+**Tip**: You can override these classes for all `<SingleFieldList>` instances by overriding them in a Material UI theme, using the key "RaSingleFieldList".
diff --git a/docs/TabbedForm.md b/docs/TabbedForm.md
index 7a4431feb13..1d75eb859bb 100644
--- a/docs/TabbedForm.md
+++ b/docs/TabbedForm.md
@@ -11,7 +11,7 @@ title: "TabbedForm"
 
 ## Usage
 
-`<TabbedForm>` reads the `record` from the `RecordContext`, uses it to initialize the defaultValues of a `<Form>`, renders its children in a MUI `<Stack>`, and renders a toolbar with a `<SaveButton>` that calls the `save` callback prepared by the edit or the create controller when pressed. 
+`<TabbedForm>` reads the `record` from the `RecordContext`, uses it to initialize the defaultValues of a `<Form>`, renders its children in a Material UI `<Stack>`, and renders a toolbar with a `<SaveButton>` that calls the `save` callback prepared by the edit or the create controller when pressed. 
 
 `<TabbedForm>` is often used as child of `<Create>` or `<Edit>`. It accepts `<TabbedForm.Tab>` elements as children. It relies on [react-hook-form](https://react-hook-form.com/) for form handling. It requires no prop by default.
 
@@ -94,7 +94,7 @@ const formState = useFormState(); // ❌ should deconstruct the formState
 
 ## `component`
 
-`<TabbedForm>` renders a MUI `<CardContent>` by default. You replace it by any component you want as wrapper, just pass it as the `component` prop.
+`<TabbedForm>` renders a Material UI `<CardContent>` by default. You replace it by any component you want as wrapper, just pass it as the `component` prop.
 
 ```jsx
 const PostCreate = () => (
@@ -281,7 +281,7 @@ export const PostEdit = () => (
 
 ## `tabs`
 
-By default, `<TabbedForm>` uses `<TabbedFormTabs>`, an internal react-admin component, to render the tab headers. You can pass a custom component as the `tabs` prop to tweak th UX of these headers. Besides, props from `<TabbedFormTabs>` are passed down to MUI's `<Tabs>` component.
+By default, `<TabbedForm>` uses `<TabbedFormTabs>`, an internal react-admin component, to render the tab headers. You can pass a custom component as the `tabs` prop to tweak th UX of these headers. Besides, props from `<TabbedFormTabs>` are passed down to Material UI's `<Tabs>` component.
 
 The following example shows how to make use of scrollable `<Tabs>`. Pass `variant="scrollable"` and `scrollButtons="auto"` props to `<TabbedFormTabs>` and use it in the `tabs` prop from `<TabbedForm>`.
 
@@ -302,7 +302,7 @@ export const PostEdit = () => (
 );
 ```
 
-**Tip**: MUI only adds the scroll buttons if there isn't enough space to display all the tabs. That can only happen if the Tabs containers have a fixed width.
+**Tip**: Material UI only adds the scroll buttons if there isn't enough space to display all the tabs. That can only happen if the Tabs containers have a fixed width.
 The solution here is to set a max width on one of the following components:
 
 * the `<Edit>` or `<Create>`
@@ -486,7 +486,7 @@ export const TagEdit = () => (
 - `sx`: custom styles to apply to the tab
 - `children`: the content of the tab (usually a list of inputs)
 
-`<TabbedForm.Tab>` renders its children in a MUI `<Stack>` component, i.e. one child per row.
+`<TabbedForm.Tab>` renders its children in a Material UI `<Stack>` component, i.e. one child per row.
 
 The `sx` prop allows to style the content of the tab, e.g. to limit its width:
 
diff --git a/docs/TabbedShowLayout.md b/docs/TabbedShowLayout.md
index 1b8b0a1410b..2a1357118ae 100644
--- a/docs/TabbedShowLayout.md
+++ b/docs/TabbedShowLayout.md
@@ -5,7 +5,7 @@ title: "TabbedShowLayout"
 
 # `<TabbedShowLayout>`
 
-The `<TabbedShowLayout>` pulls the `record` from the `RecordContext`. It renders a set of `<Tabs>`, each of which contains a list of record fields in a single-column layout (via MUI's `<Stack>` component). `<TabbedShowLayout>` delegates the actual rendering of fields to its children, which should be `<TabbedShowLayout.Tab>` elements. `<TabbedShowLayout.Tab>`  wraps each field inside a `<Labeled>` component to add a label.
+The `<TabbedShowLayout>` pulls the `record` from the `RecordContext`. It renders a set of `<Tabs>`, each of which contains a list of record fields in a single-column layout (via Material UI's `<Stack>` component). `<TabbedShowLayout>` delegates the actual rendering of fields to its children, which should be `<TabbedShowLayout.Tab>` elements. `<TabbedShowLayout.Tab>`  wraps each field inside a `<Labeled>` component to add a label.
 
 Switching tabs will update the current url. By default, it uses the tabs indexes and the first tab will be displayed at the root url. You can customize the path by providing a `path` prop to each `<TabbedShowLayout.Tab>` component. If you'd like the first one to act as an index page, just omit the `path` prop.
 
@@ -224,7 +224,7 @@ export const PostShow = () => (
 
 ## Spacing
 
-`<TabbedShowLayout.Tab>` renders a MUI `<Stack>`. You can customize the spacing of each row by passing a `spacing` prop:
+`<TabbedShowLayout.Tab>` renders a Material UI `<Stack>`. You can customize the spacing of each row by passing a `spacing` prop:
 
 ```jsx
 const PostShow = () => (
@@ -260,7 +260,7 @@ const PostShow = () => (
 
 ## Custom Tab Component
 
-By default, `<TabbedShowLayout>` renders its tabs using `<TabbedShowLayoutTabs>`, an internal react-admin component. You can pass a custom component as the `tabs` prop to override that default. Also, props passed to `<TabbedShowLayoutTabs>` are passed to the MUI's `<Tabs>` component inside `<TabbedShowLayoutTabs>`. That means you can create a custom `tabs` component without copying several components from the react-admin source.
+By default, `<TabbedShowLayout>` renders its tabs using `<TabbedShowLayoutTabs>`, an internal react-admin component. You can pass a custom component as the `tabs` prop to override that default. Also, props passed to `<TabbedShowLayoutTabs>` are passed to the Material UI's `<Tabs>` component inside `<TabbedShowLayoutTabs>`. That means you can create a custom `tabs` component without copying several components from the react-admin source.
 
 For instance, to make use of scrollable `<Tabs>`, you can pass `variant="scrollable"` and `scrollButtons="auto"` props to `<TabbedShowLayoutTabs>` and use it in the `tabs` prop from `<TabbedShowLayout>` as follows:
 
@@ -302,13 +302,13 @@ When passed a `record`, `<TabbedShowLayout>` creates a `RecordContext` with the
 
 ## `sx`: CSS API
 
-The `<TabbedShowLayout>` component accepts the usual `className` prop but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most MUI components, see their [documentation about it](https://mui.com/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
+The `<TabbedShowLayout>` component accepts the usual `className` prop but you can override many class names injected to the inner components by React-admin thanks to the `sx` property (as most Material UI components, see their [documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)). This property accepts the following subclasses:
 
 | Rule name                       | Description                                              |
 |---------------------------------| ---------------------------------------------------------|
 | `& .RaTabbedShowLayout-content` | Applied to the content zone (under the tabs)             |
 
-To override the style of all instances of `<TabbedShowLayout>` using the [MUI style overrides](https://mui.com/customization/theme-components/), use the `RaTabbedShowLayout` key.
+To override the style of all instances of `<TabbedShowLayout>` using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaTabbedShowLayout` key.
 
 To style the tabs, the `<TabbedShowLayout.Tab>` component accepts two props:
 
diff --git a/docs/TextField.md b/docs/TextField.md
index e4157a9870b..2aecc57e4fc 100644
--- a/docs/TextField.md
+++ b/docs/TextField.md
@@ -15,7 +15,7 @@ import { TextField } from 'react-admin';
 // <span>John Doe</span>
 ```
 
-`<TextField>` grabs the `record` from the current [`RecordContext`](./useRecordContext.md), extracts the value of the `source` property, and displays it inside a MUI `<Typography>` component.
+`<TextField>` grabs the `record` from the current [`RecordContext`](./useRecordContext.md), extracts the value of the `source` property, and displays it inside a Material UI `<Typography>` component.
 
 ## Usage
 
@@ -44,7 +44,7 @@ export const PostShow = () => (
 
 It also accepts [common field props](./Fields.md#common-field-props) such as the `sx` prop to override its style.
 
-Additional props are passed down to the underlying [MUI `<Typography>` component](https://mui.com/material-ui/react-typography/).
+Additional props are passed down to the underlying [Material UI `<Typography>` component](https://mui.com/material-ui/react-typography/).
 
 ## Displaying Values From More Than One Source
 
diff --git a/docs/TextInput.md b/docs/TextInput.md
index 728fa50711d..2c19c62b7dd 100644
--- a/docs/TextInput.md
+++ b/docs/TextInput.md
@@ -5,7 +5,7 @@ title: "The TextInput Component"
 
 # `<TextInput>`
 
-`<TextInput>` is the most common input. It is used for texts, emails, URL or passwords. In translates into [an MUI `<TextField>`](https://mui.com/material-ui/react-text-field/), and renders as `<input type="text">` in HTML.
+`<TextInput>` is the most common input. It is used for texts, emails, URL or passwords. In translates into [an Material UI `<TextField>`](https://mui.com/material-ui/react-text-field/), and renders as `<input type="text">` in HTML.
 
 ![TextInput](./img/text-input.gif)
 
@@ -34,7 +34,7 @@ export const PostEdit = () => (
 
 `<TextInput>` also accepts the [common input props](./Inputs.md#common-input-props).
 
-Additional props are passed down to the underlying MUI [`<TextField>`](https://mui.com/material-ui/react-text-field/) component.
+Additional props are passed down to the underlying Material UI [`<TextField>`](https://mui.com/material-ui/react-text-field/) component.
 
 ## `multiline`
 
diff --git a/docs/Theming.md b/docs/Theming.md
index e05549c60a5..13bad93dec8 100644
--- a/docs/Theming.md
+++ b/docs/Theming.md
@@ -45,7 +45,7 @@ All react-admin components expose an `sx` property, which allows to customize th
 ```
 {% endraw %}
 
-Check [The MUI documentation on the `sx` prop](https://mui.com/material-ui/customization/how-to-customize/#1-one-off-customization) for more information.
+Check [The Material UI documentation on the `sx` prop](https://mui.com/material-ui/customization/how-to-customize/#1-one-off-customization) for more information.
 
 Here is an example: Customizing the `<EditButton>` inside a `<Datagrid>`, using the `sx` prop:
 
@@ -120,7 +120,7 @@ The react-admin documentation for individual components also lists the classes a
 
 ## Reusable Components
 
-To reuse the same style overrides in different locations across your application, create a reusable component using [the MUI `styled()` utility](https://mui.com/system/styled/). It's a function that creates a new component based on a source component and custom styles. The basic syntax is `styled(Component)(styles) => Component` (where `styles` follows the same syntax as the `sx` prop).
+To reuse the same style overrides in different locations across your application, create a reusable component using [the Material UI `styled()` utility](https://mui.com/system/styled/). It's a function that creates a new component based on a source component and custom styles. The basic syntax is `styled(Component)(styles) => Component` (where `styles` follows the same syntax as the `sx` prop).
 
 For instance, to create a custom `<Datagrid>` component with the header style defined in the previous section:
 
@@ -189,9 +189,9 @@ Again, to guess the name of the subclass to use (like `.RaDatagrid-headerCell` a
 
 ## Global Theme Overrides
 
-If you want to override the style of a component across the entire application, you can use a custom theme, leveraging [the MUI Theming support](https://mui.com/material-ui/customization/theming/).
+If you want to override the style of a component across the entire application, you can use a custom theme, leveraging [the Material UI Theming support](https://mui.com/material-ui/customization/theming/).
 
-React-admin already wraps the app with [a MUI `<ThemeProvider>`](https://mui.com/material-ui/customization/theming/#themeprovider). Pass a custom `theme` to the `<Admin>` component to override the style of the entire application:
+React-admin already wraps the app with [a Material UI `<ThemeProvider>`](https://mui.com/material-ui/customization/theming/#themeprovider). Pass a custom `theme` to the `<Admin>` component to override the style of the entire application:
 
 ```jsx
 const theme = { ... };
@@ -236,7 +236,7 @@ const App = () => (
 
 There are 2 important gotchas here:
 
-- Don't forget to merge your custom style overrides with the ones from react-admin's `defaultTheme`, otherwise the application will have the default MUI theme (most notably, outlined text inputs)
+- Don't forget to merge your custom style overrides with the ones from react-admin's `defaultTheme`, otherwise the application will have the default Material UI theme (most notably, outlined text inputs)
 - Custom style overrides must live under a `root` key. Then, the style override syntax is the same as the one used for the `sx` prop.
 
 Note that you don't need to call `createTheme` yourself. React-admin will do it for you.
@@ -291,7 +291,7 @@ const theme = {
 
 ## Writing a Custom Theme
 
-MUI theming also allows to change the default palette, typography, colors, etc. This is very useful to change the react-admin style to match the branding of your company.
+Material UI theming also allows to change the default palette, typography, colors, etc. This is very useful to change the react-admin style to match the branding of your company.
 
 For instance, here is how to override the default react-admin colors and fonts:
 
@@ -331,7 +331,7 @@ A `theme` object can contain the following keys:
 * `typography`
 * `zIndex`
 
-**Tip**: Check [MUI default theme documentation](https://mui.com/customization/default-theme/) to see the default values and meaning for these keys.
+**Tip**: Check [Material UI default theme documentation](https://mui.com/material-ui/customization/default-theme/) to see the default values and meaning for these keys.
 
 Once your theme is defined, pass it to the `<Admin>` component, in the `theme` prop.
 
@@ -345,7 +345,7 @@ const App = () => (
 
 ## Using A Dark Theme
 
-MUI ships two base themes: light and dark. React-admin uses the light one by default. To use the dark theme, create a custom theme object with a `mode: 'dark'` palette, and pass it as the `<Admin theme>` prop:
+Material UI ships two base themes: light and dark. React-admin uses the light one by default. To use the dark theme, create a custom theme object with a `mode: 'dark'` palette, and pass it as the `<Admin theme>` prop:
 
 ```jsx
 import { defaultTheme } from 'react-admin';
@@ -460,9 +460,9 @@ export const PostList = () => (
 
 ## `useMediaQuery` Hook
 
-To provide an optimized experience on mobile, tablet, and desktop devices, you often need to display different components depending on the screen size. MUI provides a hook dedicated to help such responsive layouts: [useMediaQuery](https://mui.com/components/use-media-query/#usemediaquery).
+To provide an optimized experience on mobile, tablet, and desktop devices, you often need to display different components depending on the screen size. Material UI provides a hook dedicated to help such responsive layouts: [useMediaQuery](https://mui.com/material-ui/react-use-media-query/#usemediaquery-query-options-matches).
 
-It expects a function receiving the MUI theme as a parameter, and returning a media query. Use the theme breakpoints to check for common screen sizes. The hook returns a boolean indicating if the current screen matches the media query or not.
+It expects a function receiving the Material UI theme as a parameter, and returning a media query. Use the theme breakpoints to check for common screen sizes. The hook returns a boolean indicating if the current screen matches the media query or not.
 
 ```jsx
 const isXSmall = useMediaQuery(theme => theme.breakpoints.down('xs'));
@@ -570,13 +570,13 @@ import ListItemText from '@mui/material/ListItemText';
 import SettingsIcon from '@mui/icons-material/Settings';
 import LanguageIcon from '@mui/icons-material/Language';
 
-// It's important to pass the ref to allow MUI to manage the keyboard navigation
+// It's important to pass the ref to allow Material UI to manage the keyboard navigation
 const ConfigurationMenu = React.forwardRef((props, ref) => {
     return (
         <MenuItem
             ref={ref}
             component={Link}
-            // It's important to pass the props to allow MUI to manage the keyboard navigation
+            // It's important to pass the props to allow Material UI to manage the keyboard navigation
             {...props}
             to="/configuration"
         >
@@ -590,7 +590,7 @@ const ConfigurationMenu = React.forwardRef((props, ref) => {
     );
 });
 
-// It's important to pass the ref to allow MUI to manage the keyboard navigation
+// It's important to pass the ref to allow Material UI to manage the keyboard navigation
 const SwitchLanguage = React.forwardRef((props, ref) => {
     const [locale, setLocale] = useLocaleState();
     // We are not using MenuItemLink so we retrieve the onClose function from the UserContext
@@ -599,7 +599,7 @@ const SwitchLanguage = React.forwardRef((props, ref) => {
     return (
         <MenuItem
             ref={ref}
-            // It's important to pass the props to allow MUI to manage the keyboard navigation
+            // It's important to pass the props to allow Material UI to manage the keyboard navigation
             {...props}
             sx={{ color: 'text.secondary' }}
             onClick={event => {
@@ -667,7 +667,7 @@ const MyAppBar = () => <AppBar userMenu={<MyUserMenu />} />;
 
 ### Sidebar Customization
 
-You can specify the `Sidebar` width by setting the `width` and `closedWidth` properties on your custom MUI theme:
+You can specify the `Sidebar` width by setting the `width` and `closedWidth` properties on your custom Material UI theme:
 
 ```jsx
 import { defaultTheme } from 'react-admin';
@@ -858,7 +858,7 @@ const MyAppBar = () => (
 export default MyAppBar;
 ```
 
-Take note that this uses *MUI's `<AppBar>`* instead of *react-admin's `<AppBar>`*. To use this custom `AppBar` component, pass it as prop to a custom `Layout`, as explained in the previous section.
+Take note that this uses *Material UI's `<AppBar>`* instead of *react-admin's `<AppBar>`*. To use this custom `AppBar` component, pass it as prop to a custom `Layout`, as explained in the previous section.
 
 To make it easier to customize, we export some components and hooks used by the `<AppBar>`:
 
diff --git a/docs/TimeInput.md b/docs/TimeInput.md
index 03ddc398b40..694e9743237 100644
--- a/docs/TimeInput.md
+++ b/docs/TimeInput.md
@@ -22,7 +22,7 @@ import { TimeInput } from 'react-admin';
 <TimeInput source="published_at" />
 ```
 
-**Tip**: For a MUI styled `<TimeInput>` component, check out [vascofg/react-admin-date-inputs](https://github.com/vascofg/react-admin-date-inputs).
+**Tip**: For a Material UI styled `<TimeInput>` component, check out [vascofg/react-admin-date-inputs](https://github.com/vascofg/react-admin-date-inputs).
 
 ## Props
 
diff --git a/docs/ToggleThemeButton.md b/docs/ToggleThemeButton.md
index dd88bc16946..c36241c0d10 100644
--- a/docs/ToggleThemeButton.md
+++ b/docs/ToggleThemeButton.md
@@ -56,7 +56,7 @@ const darkTheme = {
 <ToggleThemeButton darkTheme={darkTheme} />
 ```
 
-**Tip**: React-admin calls MUI's `createTheme()` on this object. 
+**Tip**: React-admin calls Material UI's `createTheme()` on this object. 
 
 ## `lightTheme`
 
@@ -83,7 +83,7 @@ const lightTheme = {
 
 React-admin uses the `<Admin theme>` prop as default theme.
 
-**Tip**: React-admin calls MUI's `createTheme()` on this object. 
+**Tip**: React-admin calls Material UI's `createTheme()` on this object. 
 
 ## API
 
diff --git a/docs/Toolbar.md b/docs/Toolbar.md
index ab06d1be94e..57f71eda6bf 100644
--- a/docs/Toolbar.md
+++ b/docs/Toolbar.md
@@ -9,7 +9,7 @@ title: "The Toolbar Component"
 
 ![Toolbar](./img/Toolbar.png)
 
-**Tip**: Use react-admin's `<Toolbar>` component instead of MUI's `<Toolbar>` component. The former builds upon the latter and adds support for an alternative mobile layout (and is therefore responsive).
+**Tip**: Use react-admin's `<Toolbar>` component instead of Material UI's `<Toolbar>` component. The former builds upon the latter and adds support for an alternative mobile layout (and is therefore responsive).
 
 ## Usage
 
@@ -46,7 +46,7 @@ const CommentCreate = () => (
 - `className`
 - [`sx`](#sx-css-api)
 
-Additional props are passed down to [the MUI `<Toolbar>` component](https://mui.com/api/toolbar/).
+Additional props are passed down to [the Material UI `<Toolbar>` component](https://mui.com/material-ui/api/toolbar/).
 
 ## `children`
 
@@ -92,4 +92,4 @@ You can override the style of the toolbar using the `sx` prop. Use the class nam
 | `&.RaToolbar-mobileToolbar`    | Applied to the underlying `MuiToolbar` component for small screens                     |
 | `& .RaToolbar-defaultToolbar`  | Applied to the internal wrapper of the `<Toolbar>` buttons when no children are passed |
 
-To override the style of all instances of `<Toolbar>` components using the [MUI style overrides](https://mui.com/customization/globals/#css), use the `RaToolbar` key.
+To override the style of all instances of `<Toolbar>` components using the [Material UI style overrides](https://mui.com/material-ui/customization/theme-components/#theme-style-overrides), use the `RaToolbar` key.
diff --git a/docs/TranslatableFields.md b/docs/TranslatableFields.md
index 9893e7a4136..42f060488d4 100644
--- a/docs/TranslatableFields.md
+++ b/docs/TranslatableFields.md
@@ -40,7 +40,7 @@ React-admin uses the user locale as the default locale in this field. You can ov
 </TranslatableFields>
 ```
 
-By default, `<TranslatableFields>` will allow users to select the displayed locale using MUI tabs with the locale code as their labels.
+By default, `<TranslatableFields>` will allow users to select the displayed locale using Material UI tabs with the locale code as their labels.
 
 You may override the tabs labels using translation keys following this format: `ra.locales.[locale_code]`. For instance, `ra.locales.en` or `ra.locales.fr`.
 
diff --git a/docs/TranslatableInputs.md b/docs/TranslatableInputs.md
index 5c8cdd5e019..d796cb08f66 100644
--- a/docs/TranslatableInputs.md
+++ b/docs/TranslatableInputs.md
@@ -56,7 +56,7 @@ React-admin uses the user locale as the default locale in this field. You can ov
 </TranslatableInputs>
 ```
 
-By default, `<TranslatableInputs>` will allow users to select the displayed locale using MUI tabs with the locale code as their labels.
+By default, `<TranslatableInputs>` will allow users to select the displayed locale using Material UI tabs with the locale code as their labels.
 
 ## `groupKey`
 
diff --git a/docs/Tutorial.md b/docs/Tutorial.md
index b2d739f6987..f68ccacacb4 100644
--- a/docs/Tutorial.md
+++ b/docs/Tutorial.md
@@ -115,7 +115,7 @@ Lastly, add the `Roboto` font to the `index.html` file:
 </html>
 ```
 
-**Tip:** You can also install the `Roboto` font locally by following the instructions from the [MUI starter guide](https://mui.com/material-ui/getting-started/installation/#roboto-font).
+**Tip:** You can also install the `Roboto` font locally by following the instructions from the [Material UI starter guide](https://mui.com/material-ui/getting-started/installation/#roboto-font).
 
 The `<App>` component renders an `<Admin>` component, which is the root component of a react-admin application. This component expects a `dataProvider` prop - a function capable of fetching data from an API. Since there is no standard for data exchanges between computers, you will probably have to write a custom provider to connect react-admin to your own APIs - but we'll dive into Data Providers later. For now, let's take advantage of the `ra-data-json-server` data provider, which speaks the same REST dialect as JSONPlaceholder.
 
@@ -254,7 +254,7 @@ export const UserList = () => (
 );
 ```
 
-`<SimpleList>` uses [MUI's `<List>` and `<ListItem>` components](https://mui.com/components/lists), and expects functions as `primaryText`, `secondaryText`, and `tertiaryText` props.
+`<SimpleList>` uses [Material UI's `<List>` and `<ListItem>` components](https://mui.com/material-ui/react-list/), and expects functions as `primaryText`, `secondaryText`, and `tertiaryText` props.
 
 Refresh the page, and now the list displays in a different way:
 
@@ -270,7 +270,7 @@ The react-admin layout is already responsive. Try to resize your browser to see
 
 But on desktop, `<SimpleList>` takes too much space for a low information density. So let's modify the `<UserList>` component to use the `<Datagrid>` component on desktop, and the `<SimpleList>` component on mobile. 
 
-To do so, we'll use [the `useMediaQuery` hook](https://mui.com/material-ui/react-use-media-query/#main-content) from MUI:
+To do so, we'll use [the `useMediaQuery` hook](https://mui.com/material-ui/react-use-media-query/) from Material UI:
 
 ```jsx
 // in src/users.tsx
@@ -406,7 +406,7 @@ That means react-admin never blocks you: if one react-admin component doesn't pe
 
 The `<MyUrlField>` component is a perfect opportunity to illustrate how to customize styles.
 
-React-admin relies on [MUI](https://mui.com/), a set of React components modeled after Google's [Material Design UI Guidelines](https://material.io/). All MUI components (and most react-admin components) support a prop called `sx`, which allows custom inline styles. Let's take advantage of the `sx` prop to remove the underline from the link and add an icon:
+React-admin relies on [Material UI](https://mui.com/material-ui/getting-started/overview/), a set of React components modeled after Google's [Material Design Guidelines](https://material.io/). All Material UI components (and most react-admin components) support a prop called `sx`, which allows custom inline styles. Let's take advantage of the `sx` prop to remove the underline from the link and add an icon:
 
 {% raw %}
 ```jsx
@@ -433,9 +433,9 @@ export default MyUrlField;
 
 The `sx` prop is like React's `style` prop, except it supports theming, media queries, shorthand properties, and much more. It's a CSS-in-JS solution, so you'll have to use the JS variants of the CSS property names (e.g. `textDecoration` instead of `text-decoration`). 
 
-**Tip**: There is much more to MUI styles than what this tutorial covers. Read the [MUI documentation](https://mui.com/system/basics/) to learn more about theming, vendor prefixes, responsive utilities, etc.
+**Tip**: There is much more to Material UI styles than what this tutorial covers. Read the [Material UI documentation](https://mui.com/system/basics/) to learn more about theming, vendor prefixes, responsive utilities, etc.
 
-**Tip**: MUI supports other CSS-in-JS solutions, including [Styled components](https://mui.com/system/styled/).
+**Tip**: Material UI supports other CSS-in-JS solutions, including [Styled components](https://mui.com/system/styled/).
 
 ## Handling Relationships
 
diff --git a/docs/Upgrade.md b/docs/Upgrade.md
index 6001febe5b1..3ea441bed50 100644
--- a/docs/Upgrade.md
+++ b/docs/Upgrade.md
@@ -11,11 +11,11 @@ We've done our best to keep the general API of react-admin v4 similar with the v
 
 Depending on the size of your v3 application, the upgrade will take between a few hours to a few days. If you use TypeScript, the migration will be much faster.
 
-## MUI v5
+## Material UI v5
 
-React-admin v4 uses MUI (Material-UI) v5. The MUI team has written an upgrade guide, which you should read to upgrade your material-ui code.
+React-admin v4 uses Material UI (Material-UI) v5. The Material UI team has written an upgrade guide, which you should read to upgrade your material-ui code.
 
-[https://mui.com/guides/migration-v4/](https://mui.com/guides/migration-v4/)
+[https://mui.com/material-ui/migration/migration-v4/](https://mui.com/material-ui/migration/migration-v4/)
 
 ## Redux Is Gone
 
@@ -1716,7 +1716,7 @@ const MyForm = () => (
 
 ### `<SimpleForm>` and `<TabbedForm>` No Longer Accept `margin` and `variant`
 
-Just like MUI, we don't provide a way to specify those props at the form level. Instead, you can either set those props on the inputs or leverage the MUI [component overrides through theme](https://mui.com/customization/theme-components/) if you need to change them globally:
+Just like Material UI, we don't provide a way to specify those props at the form level. Instead, you can either set those props on the inputs or leverage the Material UI [component overrides through theme](https://mui.com/material-ui/customization/theme-components/) if you need to change them globally:
 
 ```diff
 const PostCreate = () => (
@@ -1730,9 +1730,9 @@ const PostCreate = () => (
 )
 ```
 
-You have several options when leveraging the [theme component overrides](https://mui.com/customization/theme-components/):
+You have several options when leveraging the [theme component overrides](https://mui.com/material-ui/customization/theme-components/):
 
-- Provide your own default props for MUI components such as the `TextField`:
+- Provide your own default props for Material UI components such as the `TextField`:
 ```js
 const myTheme = {
     components: {
@@ -2562,12 +2562,12 @@ Inputs and fields used to support an `addLabel` prop that instructed components
 
 If you used the `addLabel` prop to hide inputs label by passing `false`, you can pass `false` to the `label` prop instead.
 
-### `<AutocompleteInput>` and `<AutocompleteArrayInput>` Now Use MUI Autocomplete
+### `<AutocompleteInput>` and `<AutocompleteArrayInput>` Now Use Material UI Autocomplete
 
-We migrated both the `AutocompleteInput` and `AutocompleteArrayInput` components so that they leverage MUI [`<Autocomplete>`](https://mui.com/components/autocomplete/). If you relied on [Downshift](https://www.downshift-js.com/) options, you'll have to update your component.
+We migrated both the `AutocompleteInput` and `AutocompleteArrayInput` components so that they leverage Material UI [`<Autocomplete>`](https://mui.com/material-ui/react-autocomplete/). If you relied on [Downshift](https://www.downshift-js.com/) options, you'll have to update your component.
 
 Besides, some props aren't available anymore:
-- `allowDuplicates`: This is not supported by MUI Autocomplete.
+- `allowDuplicates`: This is not supported by Material UI Autocomplete.
 - `clearAlwaysVisible`: the clear button is now always visible, either while hovering the input or when it has focus. You can hide it using the `<Autocomplete>` `disableClearable` prop though.
 - `resettable`: Removed for the same reason as `clearAlwaysVisible`
 
@@ -2599,9 +2599,9 @@ const AuthorsInput = () => {
 Our old `<RichTextInput>` was based on [Quill](https://quilljs.com/) but:
 - it wasn't accessible (button without labels, etc.)
 - it wasn't translatable (labels in Quill are in the CSS)
-- it wasn't using MUI components for its UI and looked off
+- it wasn't using Material UI components for its UI and looked off
 
-The new `<RichTextInput>` uses [TipTap](https://github.com/ueberdosis/tiptap), a UI less library to build rich text editors. It gives us the freedom to implement the UI how we want with MUI components. That solves all the above issues.
+The new `<RichTextInput>` uses [TipTap](https://github.com/ueberdosis/tiptap), a UI less library to build rich text editors. It gives us the freedom to implement the UI how we want with Material UI components. That solves all the above issues.
 
 If you used the `<RichTextInput>` without passing Quill options such as custom toolbars, you have nothing to do.
 
@@ -2688,7 +2688,7 @@ import { BooleanInput } from 'react-admin';
 
 The `<SelectInput>`, `<SelectArrayInput>`, `<AutocompleteInput>` and `<AutocompleteArrayInput>` components used to accept an `allowEmpty` prop. When set to `true`, a choice was added for setting the input value to an empty value (empty string by default).
 
-However, the underlying MUI components now require that the current input value has a matching choice. Those components now always accept an empty value (an empty string by default). You can safely remove this prop.
+However, the underlying Material UI components now require that the current input value has a matching choice. Those components now always accept an empty value (an empty string by default). You can safely remove this prop.
 
 ```diff
 const choices = [{ id: 1, name: 'value' }, { id: 2, name: 'value 2' }]
@@ -2902,14 +2902,14 @@ import ListItemText from '@mui/material/ListItemText';
 import SettingsIcon from '@mui/icons-material/Settings';
 
 -const ConfigurationMenu = (props) => {
-// It's important to pass the ref to allow MUI to manage the keyboard navigation
+// It's important to pass the ref to allow Material UI to manage the keyboard navigation
 +const ConfigurationMenu = forwardRef((props, ref) => {
 +   const { onClose } = useUserMenu();
     return (
 -       <MenuItemLink
 +       <MenuItem
 +           ref={ref}
-            // It's important to pass the props to allow MUI to manage the keyboard navigation
+            // It's important to pass the props to allow Material UI to manage the keyboard navigation
             {...props}
 +           component={Link}
             to="/configuration"
@@ -2985,7 +2985,7 @@ const MyAdmin = () => (
 )
 ```
 
-### The MUI `<ThemeProvider>` is not set by `<Layout>` anymore
+### The Material UI `<ThemeProvider>` is not set by `<Layout>` anymore
 
 The `<ThemeProvider>` is now set by the `<AdminContext>` component which is rendered by `<Admin>`.
 
diff --git a/docs/UrlField.md b/docs/UrlField.md
index 7b2313fb455..6f0f1c585c5 100644
--- a/docs/UrlField.md
+++ b/docs/UrlField.md
@@ -6,7 +6,7 @@ title: "The UrlField Component"
 # `<UrlField>`
 
 
-`<UrlField>` displays a url in a MUI's `<Link href="" />` component.
+`<UrlField>` displays a url in a Material UI's `<Link href="" />` component.
 
 ```jsx
 import { UrlField } from 'react-admin';
diff --git a/docs/Vite.md b/docs/Vite.md
index b30407d4d1c..cdb117c23f1 100644
--- a/docs/Vite.md
+++ b/docs/Vite.md
@@ -92,7 +92,7 @@ Next, add the `Roboto` font to your `index.html` file:
 </html>
 ```
 
-**Tip:** You can also install the `Roboto` font locally by following the instructions from the [MUI starter guide](https://mui.com/material-ui/getting-started/installation/#roboto-font).
+**Tip:** You can also install the `Roboto` font locally by following the instructions from the [Material UI starter guide](https://mui.com/material-ui/getting-started/installation/#roboto-font).
 
 Now, start the server with `yarn dev`, browse to `http://localhost:5173/`, and you should see the working admin:
 
diff --git a/docs/useInput.md b/docs/useInput.md
index 146de1570bd..f2eb7e63a6e 100644
--- a/docs/useInput.md
+++ b/docs/useInput.md
@@ -54,7 +54,7 @@ const TitleInput = ({ source, label }) => {
 
 Additional props are passed to [react-hook-form's `useController` hook](https://react-hook-form.com/api/usecontroller).
 
-## Usage with MUI `<TextField>`
+## Usage with Material UI `<TextField>`
 
 ```jsx
 // in LatLongInput.js
@@ -107,7 +107,7 @@ const { isDirty } = useFormState(); // ✅
 const formState = useFormState(); // ❌ should deconstruct the formState      
 ```
 
-## Usage with MUI `<Select>`
+## Usage with Material UI `<Select>`
 
 ```jsx
 // in SexInput.js
diff --git a/docs/useLogout.md b/docs/useLogout.md
index 31aca550f4c..4957eaf2111 100644
--- a/docs/useLogout.md
+++ b/docs/useLogout.md
@@ -15,7 +15,7 @@ import { AppBar, Layout, UserMenu, useLogout } from 'react-admin';
 import { MenuItem } from '@mui/material';
 import ExitIcon from '@mui/icons-material/PowerSettingsNew';
 
-// It's important to pass the ref to allow MUI to manage the keyboard navigation
+// It's important to pass the ref to allow Material UI to manage the keyboard navigation
 const MyLogoutButton = forwardRef((props, ref) => {
     const logout = useLogout();
     const handleClick = () => logout();
@@ -23,7 +23,7 @@ const MyLogoutButton = forwardRef((props, ref) => {
         <MenuItem
             onClick={handleClick}
             ref={ref}
-            // It's important to pass the props to allow MUI to manage the keyboard navigation
+            // It's important to pass the props to allow Material UI to manage the keyboard navigation
             {...props}
         >
             <ExitIcon /> Logout
diff --git a/docs/useNotify.md b/docs/useNotify.md
index 7130dcd5ff7..9d71bdf18aa 100644
--- a/docs/useNotify.md
+++ b/docs/useNotify.md
@@ -32,7 +32,7 @@ The hook takes no argument and returns a callback. The callback takes 2 argument
     - `undoable`: Set it to `true` if the notification should contain an "undo" button
     - `autoHideDuration`: Duration (in milliseconds) after which the notification hides. Set it to `0` if the notification should not be dismissible.
     - `multiLine`: Set it to `true` if the notification message should be shown in more than one line.
-    - `anchorOrigin`: The position of the notification. The default is `{ vertical: 'top', horizontal: 'right' }`. See [the MUI documentation](https://mui.com/material-ui/react-snackbar/) for more details.
+    - `anchorOrigin`: The position of the notification. The default is `{ vertical: 'top', horizontal: 'right' }`. See [the Material UI documentation](https://mui.com/material-ui/react-snackbar/) for more details.
 
 Here are more examples of `notify` calls: 
 
@@ -49,7 +49,7 @@ notify('Element updated', { type: 'info', undoable: true });
 
 ## `anchorOrigin`
 
-You can change the default position of the notification by passing an `anchorOrigin` option. The value is passed to [the MUI `<Snackbar anchorOrigin>`](https://mui.com/material-ui/react-snackbar/) prop.
+You can change the default position of the notification by passing an `anchorOrigin` option. The value is passed to [the Material UI `<Snackbar anchorOrigin>`](https://mui.com/material-ui/react-snackbar/) prop.
 
 ```jsx
 notify(
@@ -174,7 +174,7 @@ const PostEdit = () => {
 
 You may want a notification message that contains HTML or other React components. To do so, you can pass a React node as the first argument of the `notify` function.
 
-This allows e.g. using [MUI's `<Alert>` component](https://mui.com/material-ui/react-snackbar/#customization) to display a notification with a custom icon, color, or action.
+This allows e.g. using [Material UI's `<Alert>` component](https://mui.com/material-ui/react-snackbar/#customization) to display a notification with a custom icon, color, or action.
 
 ![useNotify with node](./img/use-notify-node.png)
 
diff --git a/examples/no-code/src/main.tsx b/examples/no-code/src/main.tsx
index c0f35ab4942..35477277ac2 100644
--- a/examples/no-code/src/main.tsx
+++ b/examples/no-code/src/main.tsx
@@ -4,7 +4,7 @@ import { Root } from 'ra-no-code';
 import { defaultTheme } from 'react-admin';
 import { createTheme } from '@mui/material/styles';
 
-// FIXME MUI bug https://github.com/mui-org/material-ui/issues/13394
+// FIXME Material UI bug https://github.com/mui/material-ui/issues/13394
 const theme = createTheme(defaultTheme);
 
 ReactDOM.render(
diff --git a/packages/ra-ui-materialui/README.md b/packages/ra-ui-materialui/README.md
index cc2bbd8691f..38cb3bd810f 100644
--- a/packages/ra-ui-materialui/README.md
+++ b/packages/ra-ui-materialui/README.md
@@ -1,6 +1,6 @@
 # ra-ui-material
 
-UI Components for [react-admin](https://marmelab.com/react-admin/) with [MUI](https://mui.com/).
+UI Components for [react-admin](https://marmelab.com/react-admin/) with [Material UI](https://mui.com/material-ui/getting-started/overview/).
 
 ## License
 
diff --git a/packages/ra-ui-materialui/package.json b/packages/ra-ui-materialui/package.json
index 0efbbe7b623..a1e43c35adc 100644
--- a/packages/ra-ui-materialui/package.json
+++ b/packages/ra-ui-materialui/package.json
@@ -1,7 +1,7 @@
 {
     "name": "ra-ui-materialui",
     "version": "4.9.4",
-    "description": "UI Components for react-admin with MUI",
+    "description": "UI Components for react-admin with Material UI",
     "files": [
         "*.md",
         "dist",
diff --git a/packages/ra-ui-materialui/src/button/Button.stories.tsx b/packages/ra-ui-materialui/src/button/Button.stories.tsx
index 817d5e5b537..551befdc2ae 100644
--- a/packages/ra-ui-materialui/src/button/Button.stories.tsx
+++ b/packages/ra-ui-materialui/src/button/Button.stories.tsx
@@ -94,7 +94,7 @@ declare module '@mui/material/styles' {
 
 /**
  * Adding new theme tokens to the Button
- * https://mui.com/joy-ui/customization/themed-components/#theme-style-overrides
+ * https://mui.com/material-ui/customization/theme-components/#creating-new-component-variants
  */
 declare module '@mui/material/Button' {
     interface ButtonPropsColorOverrides {
diff --git a/packages/ra-ui-materialui/src/button/DeleteButton.tsx b/packages/ra-ui-materialui/src/button/DeleteButton.tsx
index 15e384c37b7..8faf921eb5e 100644
--- a/packages/ra-ui-materialui/src/button/DeleteButton.tsx
+++ b/packages/ra-ui-materialui/src/button/DeleteButton.tsx
@@ -25,8 +25,8 @@ import { DeleteWithConfirmButton } from './DeleteWithConfirmButton';
  * @prop {string} className
  * @prop {string} label Button label. Defaults to 'ra.action.delete, translated.
  * @prop {boolean} disabled Disable the button.
- * @prop {string} variant MUI variant for the button. Defaults to 'contained'.
- * @prop {ReactElement} icon Override the icon. Defaults to the Delete icon from MUI.
+ * @prop {string} variant Material UI variant for the button. Defaults to 'contained'.
+ * @prop {ReactElement} icon Override the icon. Defaults to the Delete icon from Material UI.
  *
  * @param {Props} props
  *
diff --git a/packages/ra-ui-materialui/src/button/SaveButton.tsx b/packages/ra-ui-materialui/src/button/SaveButton.tsx
index 08870b6a3b1..5f9a39b5887 100644
--- a/packages/ra-ui-materialui/src/button/SaveButton.tsx
+++ b/packages/ra-ui-materialui/src/button/SaveButton.tsx
@@ -24,7 +24,7 @@ import {
  * @prop {string} className
  * @prop {string} label Button label. Defaults to 'ra.action.save', translated.
  * @prop {boolean} disabled Disable the button.
- * @prop {string} variant MUI variant for the button. Defaults to 'contained'.
+ * @prop {string} variant Material UI variant for the button. Defaults to 'contained'.
  * @prop {ReactElement} icon
  * @prop {function} mutationOptions Object of options passed to react-query.
  * @prop {function} transform Callback to execute before calling the dataProvider. Receives the data from the form, must return that transformed data. Can be asynchronous (and return a Promise)
diff --git a/packages/ra-ui-materialui/src/detail/SimpleShowLayout.tsx b/packages/ra-ui-materialui/src/detail/SimpleShowLayout.tsx
index de56a8ca0f2..99b511ab34c 100644
--- a/packages/ra-ui-materialui/src/detail/SimpleShowLayout.tsx
+++ b/packages/ra-ui-materialui/src/detail/SimpleShowLayout.tsx
@@ -16,7 +16,7 @@ import { Labeled } from '../Labeled';
  * Layout for a Show view showing fields in one column.
  *
  * It pulls the record from the RecordContext. It renders the record fields in
- * a single-column layout (via MUI's `<Stack>` component).
+ * a single-column layout (via Material UI's `<Stack>` component).
  * `<SimpleShowLayout>` delegates the actual rendering of fields to its children.
  * It wraps each field inside a `<Labeled>` component to add a label.
  *
diff --git a/packages/ra-ui-materialui/src/detail/Tab.tsx b/packages/ra-ui-materialui/src/detail/Tab.tsx
index b767af21f6c..d24ece1ca1e 100644
--- a/packages/ra-ui-materialui/src/detail/Tab.tsx
+++ b/packages/ra-ui-materialui/src/detail/Tab.tsx
@@ -94,7 +94,7 @@ export const Tab = ({
                 value={value}
                 icon={icon}
                 className={clsx('show-tab', className)}
-                {...(syncWithLocation ? propsForLink : {})} // to avoid TypeScript screams, see https://github.com/mui-org/material-ui/issues/9106#issuecomment-451270521
+                {...(syncWithLocation ? propsForLink : {})} // to avoid TypeScript screams, see https://github.com/mui/material-ui/issues/9106#issuecomment-451270521
                 {...rest}
             />
         );
diff --git a/packages/ra-ui-materialui/src/detail/TabbedShowLayout.tsx b/packages/ra-ui-materialui/src/detail/TabbedShowLayout.tsx
index 2cd76603c36..42aac0abe29 100644
--- a/packages/ra-ui-materialui/src/detail/TabbedShowLayout.tsx
+++ b/packages/ra-ui-materialui/src/detail/TabbedShowLayout.tsx
@@ -30,7 +30,7 @@ import { Tab } from './Tab';
  *
  * It pulls the record from the RecordContext. It renders a set of `<Tabs>`,
  * each of which contains a list of record fields in a single-column layout
- * (via MUI's `<Stack>` component).
+ * (via Material UI's `<Stack>` component).
  * `<TabbedShowLayout>` delegates the actual rendering of fields to its children,
  * which should be `<TabbedShowLayout.Tab>` components.
  * `<TabbedShowLayout.Tab>` wraps each field inside a `<Labeled>` component to add a label.
diff --git a/packages/ra-ui-materialui/src/field/TextField.tsx b/packages/ra-ui-materialui/src/field/TextField.tsx
index d615e700d92..518f9752eb4 100644
--- a/packages/ra-ui-materialui/src/field/TextField.tsx
+++ b/packages/ra-ui-materialui/src/field/TextField.tsx
@@ -39,6 +39,6 @@ export interface TextFieldProps
     extends PublicFieldProps,
         InjectedFieldProps,
         Omit<TypographyProps, 'textAlign'> {
-    // TypographyProps do not expose the component props, see https://github.com/mui-org/material-ui/issues/19512
+    // TypographyProps do not expose the component props, see https://github.com/mui/material-ui/issues/19512
     component?: ElementType<any>;
 }
diff --git a/packages/ra-ui-materialui/src/field/TranslatableFields.tsx b/packages/ra-ui-materialui/src/field/TranslatableFields.tsx
index 1fb630b6063..8d15e713e3b 100644
--- a/packages/ra-ui-materialui/src/field/TranslatableFields.tsx
+++ b/packages/ra-ui-materialui/src/field/TranslatableFields.tsx
@@ -63,7 +63,7 @@ import { TranslatableFieldsTabContent } from './TranslatableFieldsTabContent';
  * @param props The component props
  * @param {string} props.defaultLocale The locale selected by default. Default to 'en'.
  * @param {string[]} props.locales An array of the possible locales in the form. For example [{ 'en', 'fr' }].
- * @param {ReactElement} props.selector The element responsible for selecting a locale. Defaults to MUI tabs.
+ * @param {ReactElement} props.selector The element responsible for selecting a locale. Defaults to Material UI tabs.
  */
 export const TranslatableFields = (
     props: TranslatableFieldsProps
diff --git a/packages/ra-ui-materialui/src/form/FormTabHeader.tsx b/packages/ra-ui-materialui/src/form/FormTabHeader.tsx
index 08f4fd2b85b..83a40932c8e 100644
--- a/packages/ra-ui-materialui/src/form/FormTabHeader.tsx
+++ b/packages/ra-ui-materialui/src/form/FormTabHeader.tsx
@@ -50,7 +50,7 @@ export const FormTabHeader = ({
                 error:
                     !formGroup.isValid && (formGroup.isTouched || isSubmitted),
             })}
-            {...(syncWithLocation ? propsForLink : {})} // to avoid TypeScript screams, see https://github.com/mui-org/material-ui/issues/9106#issuecomment-451270521
+            {...(syncWithLocation ? propsForLink : {})} // to avoid TypeScript screams, see https://github.com/mui/material-ui/issues/9106#issuecomment-451270521
             id={`tabheader-${value}`}
             aria-controls={`tabpanel-${value}`}
             onChange={onChange}
diff --git a/packages/ra-ui-materialui/src/input/AutocompleteInput.tsx b/packages/ra-ui-materialui/src/input/AutocompleteInput.tsx
index 7b6e2c73e65..fd891c49ebb 100644
--- a/packages/ra-ui-materialui/src/input/AutocompleteInput.tsx
+++ b/packages/ra-ui-materialui/src/input/AutocompleteInput.tsx
@@ -106,7 +106,7 @@ const defaultFilterOptions = createFilterOptions();
  * @example
  * <AutocompleteInput source="gender" choices={choices} translateChoice={false}/>
  *
- * The object passed as `options` props is passed to the MUI <TextField> component
+ * The object passed as `options` props is passed to the Material UI <TextField> component
  *
  * @example
  * <AutocompleteInput source="author_id" options={{ color: 'secondary', InputLabelProps: { shrink: true } }} />
@@ -489,7 +489,7 @@ If you provided a React element for the optionText prop, you must also provide t
             matchSuggestion || // When using element as optionText (and matchSuggestion), options are filtered by getSuggestions, so they shouldn't be filtered here
             limitChoicesToValue // When limiting choices to values (why? it's legacy!), options are also filtered by getSuggestions, so they shouldn't be filtered here
                 ? options
-                : defaultFilterOptions(options, params); // Otherwise, we let MUI's Autocomplete do the filtering
+                : defaultFilterOptions(options, params); // Otherwise, we let Material UI's Autocomplete do the filtering
 
         // add create option if necessary
         const { inputValue } = params;
diff --git a/packages/ra-ui-materialui/src/input/CheckboxGroupInput.tsx b/packages/ra-ui-materialui/src/input/CheckboxGroupInput.tsx
index ecf38624341..c22c8291330 100644
--- a/packages/ra-ui-materialui/src/input/CheckboxGroupInput.tsx
+++ b/packages/ra-ui-materialui/src/input/CheckboxGroupInput.tsx
@@ -82,7 +82,7 @@ import { LinearProgress } from '../layout';
  * @example
  * <CheckboxGroupInput source="tags" choices={choices} translateChoice={false}/>
  *
- * The object passed as `options` props is passed to the MUI <Checkbox> components
+ * The object passed as `options` props is passed to the Material UI <Checkbox> components
  */
 export const CheckboxGroupInput: FunctionComponent<CheckboxGroupInputProps> = props => {
     const {
diff --git a/packages/ra-ui-materialui/src/input/InputHelperText.tsx b/packages/ra-ui-materialui/src/input/InputHelperText.tsx
index 7e9b394ef8d..ac1ab4517c4 100644
--- a/packages/ra-ui-materialui/src/input/InputHelperText.tsx
+++ b/packages/ra-ui-materialui/src/input/InputHelperText.tsx
@@ -30,11 +30,11 @@ export const InputHelperText = (props: InputHelperTextProps) => {
         return <>{translate(helperText, { _: helperText })}</>;
     }
 
-    // MUI's HelperText cannot reserve space unless we pass a single
+    // Material UI's HelperText cannot reserve space unless we pass a single
     // space as child, which isn't possible when the child is a component.
     // Therefore, we must reserve the space ourselves by passing the same
-    // markup as MUI.
-    // @see https://github.com/mui-org/material-ui/blob/62e439b7022d519ab638d65201e204b59b77f8da/packages/material-ui/src/FormHelperText/FormHelperText.js#L85-L90
+    // markup as Material UI.
+    // @see https://github.com/mui/material-ui/blob/62e439b7022d519ab638d65201e204b59b77f8da/packages/material-ui/src/FormHelperText/FormHelperText.js#L85-L90
     return <span dangerouslySetInnerHTML={defaultInnerHTML} />;
 };
 
diff --git a/packages/ra-ui-materialui/src/input/RadioButtonGroupInput.tsx b/packages/ra-ui-materialui/src/input/RadioButtonGroupInput.tsx
index 42bb459c7c4..c35cd085bc3 100644
--- a/packages/ra-ui-materialui/src/input/RadioButtonGroupInput.tsx
+++ b/packages/ra-ui-materialui/src/input/RadioButtonGroupInput.tsx
@@ -78,7 +78,7 @@ import { LinearProgress } from '../layout';
  * @example
  * <RadioButtonGroupInput source="gender" choices={choices} translateChoice={false}/>
  *
- * The object passed as `options` props is passed to the MUI <RadioButtonGroup> component
+ * The object passed as `options` props is passed to the Material UI <RadioButtonGroup> component
  */
 export const RadioButtonGroupInput = (props: RadioButtonGroupInputProps) => {
     const {
diff --git a/packages/ra-ui-materialui/src/input/ResettableTextField.tsx b/packages/ra-ui-materialui/src/input/ResettableTextField.tsx
index 2a44204a349..0680271da2c 100644
--- a/packages/ra-ui-materialui/src/input/ResettableTextField.tsx
+++ b/packages/ra-ui-materialui/src/input/ResettableTextField.tsx
@@ -13,7 +13,7 @@ import ClearIcon from '@mui/icons-material/Clear';
 import { useTranslate } from 'ra-core';
 
 /**
- * An override of the default MUI TextField which is resettable
+ * An override of the default Material UI TextField which is resettable
  */
 export const ResettableTextField = forwardRef(
     (props: ResettableTextFieldProps, ref) => {
diff --git a/packages/ra-ui-materialui/src/input/SelectInput.tsx b/packages/ra-ui-materialui/src/input/SelectInput.tsx
index fcc474d753a..120fb6eb8c5 100644
--- a/packages/ra-ui-materialui/src/input/SelectInput.tsx
+++ b/packages/ra-ui-materialui/src/input/SelectInput.tsx
@@ -86,7 +86,7 @@ import { LoadingInput } from './LoadingInput';
  * @example
  * <SelectInput source="gender" choices={choices} translateChoice={false}/>
  *
- * The object passed as `options` props is passed to the MUI <Select> component
+ * The object passed as `options` props is passed to the Material UI <Select> component
  *
  * You can disable some choices by providing a `disableValue` field which name is `disabled` by default
  * @example
diff --git a/packages/ra-ui-materialui/src/input/TranslatableInputs.tsx b/packages/ra-ui-materialui/src/input/TranslatableInputs.tsx
index ef4fe3dbb98..da6f3ac5691 100644
--- a/packages/ra-ui-materialui/src/input/TranslatableInputs.tsx
+++ b/packages/ra-ui-materialui/src/input/TranslatableInputs.tsx
@@ -60,7 +60,7 @@ import { TranslatableInputsTabContent } from './TranslatableInputsTabContent';
  * @param props The component props
  * @param {string} props.defaultLocale The locale selected by default. Default to 'en'.
  * @param {string[]} props.locales An array of the possible locales. For example: `['en', 'fr'].
- * @param {ReactElement} props.selector The element responsible for selecting a locale. Defaults to MUI tabs.
+ * @param {ReactElement} props.selector The element responsible for selecting a locale. Defaults to Material UI tabs.
  */
 export const TranslatableInputs = (
     props: TranslatableInputsProps
diff --git a/packages/ra-ui-materialui/src/layout/AppBar.stories.tsx b/packages/ra-ui-materialui/src/layout/AppBar.stories.tsx
index cf049a3fc1b..2c8c9d0bd5c 100644
--- a/packages/ra-ui-materialui/src/layout/AppBar.stories.tsx
+++ b/packages/ra-ui-materialui/src/layout/AppBar.stories.tsx
@@ -198,7 +198,7 @@ export const UserMenuCustom = () => (
     </Wrapper>
 );
 
-// It's important to pass the ref to allow MUI to manage the keyboard navigation
+// It's important to pass the ref to allow Material UI to manage the keyboard navigation
 const SettingsMenuItem: React.FC<MenuItemProps> = React.forwardRef(
     (props, ref) => {
         // We are not using MenuItemLink so we retrieve the onClose function from the UserContext
@@ -207,7 +207,7 @@ const SettingsMenuItem: React.FC<MenuItemProps> = React.forwardRef(
             <MenuItem
                 onClick={onClose}
                 ref={ref}
-                // It's important to pass the props to allow MUI to manage the keyboard navigation
+                // It's important to pass the props to allow Material UI to manage the keyboard navigation
                 {...props}
             >
                 <ListItemIcon>
diff --git a/packages/ra-ui-materialui/src/layout/CardContentInner.tsx b/packages/ra-ui-materialui/src/layout/CardContentInner.tsx
index 6b300d8d35f..77853d50d2c 100644
--- a/packages/ra-ui-materialui/src/layout/CardContentInner.tsx
+++ b/packages/ra-ui-materialui/src/layout/CardContentInner.tsx
@@ -5,7 +5,7 @@ import PropTypes from 'prop-types';
 import CardContent from '@mui/material/CardContent';
 
 /**
- * Overrides MUI CardContent to allow inner content
+ * Overrides Material UI CardContent to allow inner content
  *
  * When using several CardContent inside the same Card, the top and bottom
  * padding double the spacing between each CardContent, leading to too much
diff --git a/packages/ra-ui-materialui/src/layout/MenuItemLink.tsx b/packages/ra-ui-materialui/src/layout/MenuItemLink.tsx
index 22475521d2c..4eddb16e988 100644
--- a/packages/ra-ui-materialui/src/layout/MenuItemLink.tsx
+++ b/packages/ra-ui-materialui/src/layout/MenuItemLink.tsx
@@ -25,7 +25,7 @@ import { useTranslate, useBasename } from 'ra-core';
  * @prop {string|ReactNode} primaryText The menu content, displayed when the menu isn't minimized. |
  * @prop {ReactNode} leftIcon The menu icon
  *
- * Additional props are passed down to the underling MUI <MenuItem> component
+ * Additional props are passed down to the underling Material UI <MenuItem> component
  * @see https://material-ui.com/api/menu-item/#menuitem-api
  *
  * @example // You can create a custom menu component using the <DashboardMenuItem> and <MenuItemLink> components:
diff --git a/packages/ra-ui-materialui/src/layout/Theme/ThemeProvider.tsx b/packages/ra-ui-materialui/src/layout/Theme/ThemeProvider.tsx
index b536dfe2f8e..f4df0c16c1e 100644
--- a/packages/ra-ui-materialui/src/layout/Theme/ThemeProvider.tsx
+++ b/packages/ra-ui-materialui/src/layout/Theme/ThemeProvider.tsx
@@ -9,7 +9,7 @@ import { ThemeOptions } from '@mui/material';
 import { useTheme } from './useTheme';
 
 /**
- * This sets the MUI theme based on the store.
+ * This sets the Material UI theme based on the store.
  *
  * @param props
  * @param props.children The children of the component.
diff --git a/packages/ra-ui-materialui/src/list/SimpleList/SimpleList.tsx b/packages/ra-ui-materialui/src/list/SimpleList/SimpleList.tsx
index a306441d6fb..bf63392ace8 100644
--- a/packages/ra-ui-materialui/src/list/SimpleList/SimpleList.tsx
+++ b/packages/ra-ui-materialui/src/list/SimpleList/SimpleList.tsx
@@ -30,7 +30,7 @@ import { SimpleListLoading } from './SimpleListLoading';
 import { ListNoResults } from '../ListNoResults';
 
 /**
- * The <SimpleList> component renders a list of records as a MUI <List>.
+ * The <SimpleList> component renders a list of records as a Material UI <List>.
  * It is usually used as a child of react-admin's <List> and <ReferenceManyField> components.
  *
  * Also widely used on Mobile.
diff --git a/packages/ra-ui-materialui/src/list/SingleFieldList.tsx b/packages/ra-ui-materialui/src/list/SingleFieldList.tsx
index 18ce142d54e..09f831e0848 100644
--- a/packages/ra-ui-materialui/src/list/SingleFieldList.tsx
+++ b/packages/ra-ui-materialui/src/list/SingleFieldList.tsx
@@ -174,6 +174,6 @@ const Root = styled('div', {
 const stopPropagation = e => e.stopPropagation();
 
 // Our handleClick does nothing as we wrap the children inside a Link but it is
-// required by ChipField, which uses a Chip from MUI.
-// The MUI Chip requires an onClick handler to behave like a clickable element.
+// required by ChipField, which uses a Chip from Material UI.
+// The Material UI Chip requires an onClick handler to behave like a clickable element.
 const handleClick = () => {};
diff --git a/packages/ra-ui-materialui/src/list/datagrid/DatagridBody.tsx b/packages/ra-ui-materialui/src/list/datagrid/DatagridBody.tsx
index bda5295f361..38abf1ac6aa 100644
--- a/packages/ra-ui-materialui/src/list/datagrid/DatagridBody.tsx
+++ b/packages/ra-ui-materialui/src/list/datagrid/DatagridBody.tsx
@@ -116,13 +116,13 @@ export interface DatagridBodyProps extends Omit<TableBodyProps, 'classes'> {
     isRowSelectable?: (record: RaRecord) => boolean;
 }
 
-// trick MUI Table into thinking this is one of the child type it supports
+// trick Material UI Table into thinking this is one of the child type it supports
 // @ts-ignore
 DatagridBody.muiName = 'TableBody';
 
 export const PureDatagridBody = memo(DatagridBody);
 
-// trick MUI Table into thinking this is one of the child type it supports
+// trick Material UI Table into thinking this is one of the child type it supports
 // @ts-ignore
 PureDatagridBody.muiName = 'TableBody';
 // @ts-ignore
diff --git a/packages/ra-ui-materialui/src/list/pagination/Pagination.tsx b/packages/ra-ui-materialui/src/list/pagination/Pagination.tsx
index c8e6637d93c..07bdfeff493 100644
--- a/packages/ra-ui-materialui/src/list/pagination/Pagination.tsx
+++ b/packages/ra-ui-materialui/src/list/pagination/Pagination.tsx
@@ -44,7 +44,7 @@ export const Pagination: FC<PaginationProps> = memo(props => {
     }, [perPage, total]);
 
     /**
-     * Warning: MUI's page is 0-based
+     * Warning: Material UI's page is 0-based
      */
     const handlePageChange = useCallback(
         (event, page) => {
diff --git a/packages/ra-ui-materialui/src/list/pagination/PaginationActions.tsx b/packages/ra-ui-materialui/src/list/pagination/PaginationActions.tsx
index fa0bc956b3b..c6f8d01df93 100644
--- a/packages/ra-ui-materialui/src/list/pagination/PaginationActions.tsx
+++ b/packages/ra-ui-materialui/src/list/pagination/PaginationActions.tsx
@@ -65,9 +65,9 @@ export interface PaginationActionsProps extends PaginationProps {
     onPageChange: (event: MouseEvent, page: number) => void;
 }
 /**
- * PaginationActions propTypes are copied over from MUI’s
+ * PaginationActions propTypes are copied over from Material UI’s
  * TablePaginationActions propTypes. See
- * https://github.com/mui-org/material-ui/blob/869692ecf3812bc4577ed4dde81a9911c5949695/packages/material-ui/src/TablePaginationActions/TablePaginationActions.js#L53-L85
+ * https://github.com/mui/material-ui/blob/869692ecf3812bc4577ed4dde81a9911c5949695/packages/material-ui/src/TablePaginationActions/TablePaginationActions.js#L53-L85
  * for reference.
  */
 PaginationActions.propTypes = {
diff --git a/packages/react-admin/README.md b/packages/react-admin/README.md
index 32776cdfc40..c62f140c507 100644
--- a/packages/react-admin/README.md
+++ b/packages/react-admin/README.md
@@ -9,7 +9,7 @@ A frontend Framework for building data-driven applications running in the browse
 ## Features
 
 * Adapts to any backend (REST, GraphQL, SOAP, etc.)
-* Powered by [material-ui](https://mui.com/), [react-query](https://react-query-v3.tanstack.com/), [react-hook-form](https://react-hook-form.com), [react-router](https://reacttraining.com/react-router/) and a few more
+* Powered by [Material UI](https://mui.com/material-ui/getting-started/overview/), [react-query](https://react-query-v3.tanstack.com/), [react-hook-form](https://react-hook-form.com), [react-router](https://reacttraining.com/react-router/) and a few more
 * Super-fast UI thanks to optimistic rendering (renders before the server returns)
 * Undo updates and deletes for a few seconds
 * Relationships (many to one, one to many)
@@ -67,7 +67,7 @@ render(
 );
 ```
 
-The `<Resource>` component is a configuration component that allows to define sub components for each of the admin view: `list`, `edit`, and `create`. These components use MUI and custom components from react-admin:
+The `<Resource>` component is a configuration component that allows to define sub components for each of the admin view: `list`, `edit`, and `create`. These components use Material UI and custom components from react-admin:
 
 ```jsx
 // in posts.js
@@ -133,7 +133,7 @@ See the [Data Providers documentation](https://marmelab.com/react-admin/DataProv
 
 ## Batteries Included But Removable
 
-React-admin is designed as a library of loosely coupled React components built on top of [material-ui](https://mui.com/), in addition to custom react hooks exposing reusable controller logic. It is very easy to replace one part of react-admin with your own, e.g. to use a custom datagrid, GraphQL instead of REST, or Bootstrap instead of Material Design.
+React-admin is designed as a library of loosely coupled React components built on top of [Material UI](https://mui.com/material-ui/getting-started/overview/), in addition to custom react hooks exposing reusable controller logic. It is very easy to replace one part of react-admin with your own, e.g. to use a custom datagrid, GraphQL instead of REST, or Bootstrap instead of Material Design.
 
 ## Examples
 

From 7f5e045e7306a852e6f757c9c281e71bd6951f4e Mon Sep 17 00:00:00 2001
From: Olivier Tassinari <olivier.tassinari@gmail.com>
Date: Mon, 24 Apr 2023 23:20:37 +0200
Subject: [PATCH 2/2] fix name

---
 docs/AppBar.md             | 2 +-
 docs/Breadcrumb.md         | 2 +-
 docs/IconMenu.md           | 4 ++--
 docs/Layout.md             | 2 +-
 docs/Menu.md               | 2 +-
 docs/MultiLevelMenu.md     | 4 ++--
 docs/SimpleFormIterator.md | 2 +-
 7 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/docs/AppBar.md b/docs/AppBar.md
index b6e50dbb99e..2608eb8596a 100644
--- a/docs/AppBar.md
+++ b/docs/AppBar.md
@@ -67,7 +67,7 @@ const App = () => (
 | `alwaysOn`          | Optional | `boolean`      | -        | When true, the app bar is always visible            |
 | `children`          | Optional | `ReactElement` | -        | What to display in the central part of the app bar  |
 | `color`             | Optional | `string`       | -        | The background color of the app bar                 |
-| `sx`                | Optional | `SxProps`      | -        | Style overrides, powered by Material UI System              |
+| `sx`                | Optional | `SxProps`      | -        | Style overrides, powered by MUI System              |
 | `toolbar`           | Optional | `ReactElement` | -        | The content of the toolbar                          |
 | `userMenu`          | Optional | `ReactElement` | -        | The content of the dropdown user menu               |
 
diff --git a/docs/Breadcrumb.md b/docs/Breadcrumb.md
index 08da73256ac..e30d3dd2a26 100644
--- a/docs/Breadcrumb.md
+++ b/docs/Breadcrumb.md
@@ -138,7 +138,7 @@ Check [the ra-navigation documentation](https://marmelab.com/ra-enterprise/modul
 | ----------- | -------- | ------------------- | -------- | -------------------------------------- |
 | `children`  | required | `ReactNode`         | -        | The Breadcrumb Items to be rendered.   |
 | `separator` | Optional | `string | function` | '/'      | The character user as separator        |
-| `sx`        | Optional | `SxProps`           | -        | Style overrides, powered by Material UI System |
+| `sx`        | Optional | `SxProps`           | -        | Style overrides, powered by MUI System |
 
 Additional props are passed down to the root `<nav>` component.
 
diff --git a/docs/IconMenu.md b/docs/IconMenu.md
index cb807e4c89e..3c3e14e7852 100644
--- a/docs/IconMenu.md
+++ b/docs/IconMenu.md
@@ -75,7 +75,7 @@ const App = () => (
 | Prop        | Required | Type        | Default  | Description                            |
 | ----------- | -------- | ----------- | -------- | -------------------------------------- |
 | `children`  | Optional | `ReactNode` | -        | The Menu Item Links to be rendered.    |
-| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by Material UI System |
+| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by MUI System |
 
 Additional props are passed down to the root `<div>` component.
 
@@ -141,7 +141,7 @@ It requires the following props:
 It accepts optional props:
 
 - `children`: Content of a sliding panel displayed when the menu is clicked (see [Adding sub menus](#adding-sub-menus) below)
-- `sx`: Style overrides, powered by Material UI System
+- `sx`: Style overrides, powered by MUI System
 
 Additional props are passed down to [the underling Material UI `<listItem>` component](https://mui.com/material-ui/api/list-item/).
 
diff --git a/docs/Layout.md b/docs/Layout.md
index a2053869739..f2807fcfe17 100644
--- a/docs/Layout.md
+++ b/docs/Layout.md
@@ -52,7 +52,7 @@ const App = () => (
 | `error`     | Optional | `Component` | -        | A React component rendered in the content area in case of error       |
 | `menu`      | Optional | `Component` | -        | A React component rendered at the side of the screen                  |
 | `sidebar`   | Optional | `Component` | -        | A React component responsible for rendering the menu (e.g. in a drawer) |
-| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by Material UI System                                |
+| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by MUI System                                |
 
 React-admin injects more props at runtime based on the `<Admin>` props:
 
diff --git a/docs/Menu.md b/docs/Menu.md
index e6087c1dddb..651847968a6 100644
--- a/docs/Menu.md
+++ b/docs/Menu.md
@@ -60,7 +60,7 @@ const App = () => (
 | Prop        | Required | Type        | Default  | Description                                                                          |
 | ----------- | -------- | ----------- | -------- | ------------------------------------------------------------------------------------ |
 | `children`  | Optional | `ReactNode` | -        | The Menu Item Links to be rendered. If not provided, defaults to the Resource names. |
-| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by Material UI System                                               |
+| `sx`        | Optional | `SxProps`   | -        | Style overrides, powered by MUI System                                               |
 
 Additional props are passed down to the root component (the Material UI [`<MenuList>`](https://mui.com/material-ui/api/menu-list/) component)
 
diff --git a/docs/MultiLevelMenu.md b/docs/MultiLevelMenu.md
index 3c06074892b..a008375574a 100644
--- a/docs/MultiLevelMenu.md
+++ b/docs/MultiLevelMenu.md
@@ -111,7 +111,7 @@ const App = () => (
 | ------------- | -------- | ----------- | -------- | -------------------------------------- |
 | `children`    | Optional | `ReactNode` | -        | The Menu Items  to be rendered.        |
 | `initialOpen` | Optional | `boolean`   | `false`  | Whether the menu is initially open.    |
-| `sx`          | Optional | `SxProps`   | -        | Style overrides, powered by Material UI System |
+| `sx`          | Optional | `SxProps`   | -        | Style overrides, powered by MUI System |
 
 Additional props are passed down to the root `<div>` component.
 
@@ -189,7 +189,7 @@ It accepts optional props:
 
 - `icon`: the icon to display.
 - `children`: Other `<MultiLevelMenu.Item>` children.
-- `sx`: Style overrides, powered by Material UI System
+- `sx`: Style overrides, powered by MUI System
 
 Additional props are passed down to [the underling Material UI `<listItem>` component](https://mui.com/api/list-item/#listitem-api).
 
diff --git a/docs/SimpleFormIterator.md b/docs/SimpleFormIterator.md
index d654db8730c..3c8630431e5 100644
--- a/docs/SimpleFormIterator.md
+++ b/docs/SimpleFormIterator.md
@@ -349,7 +349,7 @@ const OrderEdit = () => (
 
 ## `sx`
 
-You can override the style of the root element (a `<div>` element) as well as those of the inner components thanks to the `sx` property. It relies on Material UI System and supports CSS and shorthand properties (see [their documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)).
+You can override the style of the root element (a `<div>` element) as well as those of the inner components thanks to the `sx` property. It relies on MUI System and supports CSS and shorthand properties (see [their documentation about it](https://mui.com/material-ui/customization/how-to-customize/#overriding-nested-component-styles)).
 
 This property accepts the following subclasses: