Merge branch 'master' into issue-15055

docs/data/data-grid/export/export.md

@@ -358,7 +358,7 @@ apiRef.current.exportDataAsExcel({
 ```
 
 :::info
-If you are using Next.js or Webpack 5, use the following syntax instead.
+If you are using Next.js or webpack 5, use the following syntax instead.
 Make sure to pass the **relative path**, considering the current file, to the worker script.
 
 ```tsx
@@ -375,7 +375,7 @@ apiRef.current.exportDataAsExcel({
 });
 ```
 
-It is not necessary to make the script public because [Webpack](https://webpack.js.org/guides/web-workers/) will handle that automatically for you.
+It is not necessary to make the script public because [webpack](https://webpack.js.org/guides/web-workers/) will handle that automatically for you.
 :::
 
 Since the main thread is not locked while the data is exported, it is important to give feedback for users that something is in progress.

docs/data/introduction/licensing/licensing.md

@@ -281,7 +281,7 @@ Most bundlers set this environment variable automatically when building for prod
 
 Note that `NODE_ENV=production` is not MUI X-specific and is a common practice in the JavaScript ecosystem.
 It allows bundlers and libraries to optimize the output for production and eliminate dead code, so it's worth checking if it's set correctly in your project.
-See related documentation for [Webpack](https://webpack.js.org/guides/production/#specify-the-mode), [Node.js](https://nodejs.org/en/learn/getting-started/nodejs-the-difference-between-development-and-production) and [Next.js](https://nextjs.org/docs/messages/non-standard-node-env) for more information.
+See related documentation for [webpack](https://webpack.js.org/guides/production/#specify-the-mode), [Node.js](https://nodejs.org/en/learn/getting-started/nodejs-the-difference-between-development-and-production) and [Next.js](https://nextjs.org/docs/messages/non-standard-node-env) for more information.
 :::
 
 ### 4. License key plan mismatch

docs/data/migration/migration-charts-v6/migration-charts-v6.md

@@ -41,13 +41,13 @@ The `legacy` bundle that used to support old browsers like IE 11 is no longer i
 If you need support for IE 11, you will need to keep using the latest version of the `v6` release.
 :::
 
-### Drop Webpack 4 support
+### Drop webpack 4 support
 
 Dropping old browsers support also means that we no longer transpile some features that are natively supported by modern browsers – like [Nullish Coalescing](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing) and [Optional Chaining](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining).
 
-These features are not supported by Webpack 4, so if you are using Webpack 4, you will need to transpile these features yourself or upgrade to Webpack 5.
+These features are not supported by webpack 4, so if you are using webpack 4, you will need to transpile these features yourself or upgrade to webpack 5.
 
-Here is an example of how you can transpile these features on Webpack 4 using the `@babel/preset-env` preset:
+Here is an example of how you can transpile these features on webpack 4 using the `@babel/preset-env` preset:
 
 ```diff
  // webpack.config.js

docs/data/migration/migration-data-grid-v6/migration-data-grid-v6.md

@@ -108,13 +108,13 @@ The `legacy` bundle that used to support old browsers like IE 11 is no longer i
 If you need support for IE 11, you will need to keep using the latest version of the `v6` release.
 :::
 
-### Drop Webpack 4 support
+### Drop webpack 4 support
 
 Dropping old browsers support also means that we no longer transpile some features that are natively supported by modern browsers – like [Nullish Coalescing](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing) and [Optional Chaining](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining).
 
-These features are not supported by Webpack 4, so if you are using Webpack 4, you will need to transpile these features yourself or upgrade to Webpack 5.
+These features are not supported by webpack 4, so if you are using webpack 4, you will need to transpile these features yourself or upgrade to webpack 5.
 
-Here is an example of how you can transpile these features on Webpack 4 using the `@babel/preset-env` preset:
+Here is an example of how you can transpile these features on webpack 4 using the `@babel/preset-env` preset:
 
 ```diff
  // webpack.config.js

docs/data/migration/migration-pickers-v6/migration-pickers-v6.md

@@ -101,13 +101,13 @@ The `legacy` bundle that used to support old browsers like IE 11 is no longer i
 If you need support for IE 11, you will need to keep using the latest version of the `v6` release.
 :::
 
-### Drop Webpack 4 support
+### Drop webpack 4 support
 
 Dropping old browsers support also means that we no longer transpile some features that are natively supported by modern browsers – like [Nullish Coalescing](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing) and [Optional Chaining](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining).
 
-These features are not supported by Webpack 4, so if you are using Webpack 4, you will need to transpile these features yourself or upgrade to Webpack 5.
+These features are not supported by webpack 4, so if you are using webpack 4, you will need to transpile these features yourself or upgrade to webpack 5.
 
-Here is an example of how you can transpile these features on Webpack 4 using the `@babel/preset-env` preset:
+Here is an example of how you can transpile these features on webpack 4 using the `@babel/preset-env` preset:
 
 ```diff
  // webpack.config.js

docs/data/migration/migration-tree-view-v6/migration-tree-view-v6.md

@@ -81,13 +81,13 @@ The `legacy` bundle that used to support old browsers like IE 11 is no longer i
 If you need support for IE 11, you will need to keep using the latest version of the `v6` release.
 :::
 
-### Drop Webpack 4 support
+### Drop webpack 4 support
 
 Dropping old browsers support also means that we no longer transpile some features that are natively supported by modern browsers – like [Nullish Coalescing](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing) and [Optional Chaining](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining).
 
-These features are not supported by Webpack 4, so if you are using Webpack 4, you will need to transpile these features yourself or upgrade to Webpack 5.
+These features are not supported by webpack 4, so if you are using webpack 4, you will need to transpile these features yourself or upgrade to webpack 5.
 
-Here is an example of how you can transpile these features on Webpack 4 using the `@babel/preset-env` preset:
+Here is an example of how you can transpile these features on webpack 4 using the `@babel/preset-env` preset:
 
 ```diff
  // webpack.config.js