diff --git a/docs/data/material/getting-started/supported-platforms/supported-platforms.md b/docs/data/material/getting-started/supported-platforms/supported-platforms.md
index 6559c6fa26cc73..bf076b05c4c51c 100644
--- a/docs/data/material/getting-started/supported-platforms/supported-platforms.md
+++ b/docs/data/material/getting-started/supported-platforms/supported-platforms.md
@@ -42,17 +42,6 @@ v6 will completely remove the support of IE 11.
 Material UI supports [Node.js](https://github.com/nodejs/node) starting with version 12.0 for server-side rendering.
 The objective is to support Node.js down to the [last version in maintenance mode](https://github.com/nodejs/Release#release-schedule).
 
-### CSS prefixing
-
-Be aware that some CSS features [require](https://github.com/cssinjs/jss/issues/279) an additional postprocessing step
-that adds vendor-specific prefixes.
-These prefixes are automatically added to the client thanks to [`jss-plugin-vendor-prefixer`](https://www.npmjs.com/package/jss-plugin-vendor-prefixer).
-
-The CSS served on this documentation is processed with [`autoprefixer`](https://www.npmjs.com/package/autoprefixer).
-You can use [the documentation implementation](https://github.com/mui/material-ui/blob/47aa5aeaec1d4ac2c08fd0e84277d6b91e497557/pages/_document.js#L123) as inspiration.
-Be aware that it has an implication with the performance of the page.
-It's a must-do for static pages, but it needs to be put in balance with not doing anything when rendering dynamic pages.
-
 ## React
 
 <!-- #react-peer-version -->
diff --git a/docs/data/styles/advanced/advanced.md b/docs/data/styles/advanced/advanced.md
index 65db91794e0b1d..bb86bcac14e9bf 100644
--- a/docs/data/styles/advanced/advanced.md
+++ b/docs/data/styles/advanced/advanced.md
@@ -393,6 +393,17 @@ function render() {
 
 You can [follow the server side guide](/material-ui/guides/server-rendering/) for a more detailed example, or read the [`ServerStyleSheets` API documentation](/system/styles/api/#serverstylesheets).
 
+### CSS prefixing
+
+Be aware that some CSS features [require](https://github.com/cssinjs/jss/issues/279) an additional postprocessing step
+that adds vendor-specific prefixes.
+These prefixes are automatically added to the client thanks to [`jss-plugin-vendor-prefixer`](https://www.npmjs.com/package/jss-plugin-vendor-prefixer).
+
+The CSS served on this documentation is processed with [`autoprefixer`](https://www.npmjs.com/package/autoprefixer).
+You can use [the documentation implementation](https://github.com/mui/material-ui/blob/47aa5aeaec1d4ac2c08fd0e84277d6b91e497557/pages/_document.js#L123) as inspiration.
+Be aware that it has an implication with the performance of the page.
+It's a must-do for static pages, but it needs to be put in balance with not doing anything when rendering dynamic pages.
+
 ### Gatsby
 
 There is [an official Gatsby plugin](https://github.com/hupe1980/gatsby-plugin-material-ui) that enables server-side rendering for `@mui/styles`.