diff --git a/editors/vscode/README.md b/editors/vscode/README.md
index 6f0cce4ca5d9..ba0ae8641210 100644
--- a/editors/vscode/README.md
+++ b/editors/vscode/README.md
@@ -96,17 +96,3 @@ Enables Rome to handle renames in the workspace (experimental).
 
 Disables formatting, linting, and syntax errors for projects without a `rome.json` file. Requires Rome 12 or newer.
 Enabled by default.
-
-## Known limitations
-
-### Configuration per sub-directory
-
-Rome doesn’t yet support loading the `rome.json` file from a directory other than the workspace root ([issue 3576](https://github.com/rome/tools/issues/3576), [issue 3289](https://github.com/rome/tools/issues/3289)). That means it is currently impossible to enable Rome only for a specific sub-folder or to use different configurations for different folders.
-
-### Configuration resolution for multi-root workspaces
-
-Rome isn't yet able to pick up the `rome.json` configuration in [multi-root workspaces](https://code.visualstudio.com/docs/editor/multi-root-workspaces) if the configuration isn't in the first root folder ([issue 3538](https://github.com/rome/tools/issues/3538)). You can work around this limitation by making the folder with the configuration the first root folder of the workspace (drag it to the top).
-
-### Disable Rome for workspaces without a `rome.json` configuration
-
-You can set Rome's [`rome.requireConfiguration`](#romerequireconfiguration) setting to `true` to disable Rome's formatter, linter, and syntax errors for projects without a `rome.json` file.
diff --git a/website/src/pages/configuration.mdx b/website/src/pages/configuration.mdx
index d37ee2ba32a3..1aa9b6291fc2 100644
--- a/website/src/pages/configuration.mdx
+++ b/website/src/pages/configuration.mdx
@@ -37,6 +37,33 @@ Here's an example:
 
 This configuration file enables the formatter and sets the preferred indent style and width. The linter is disabled.
 
+## Configuration file resolution
+
+Rome uses auto discovery to find the nearest `rome.json` file. It starts looking for `rome.json` in the current
+working directory, and then it starts looking in the parent directories until:
+- it finds a `rome.json` file;
+- it applies Rome's defaults if **no `rome.json` is found**;
+
+Here's an example:
+
+```
+└── app
+    ├── backend
+    │   ├── package.json
+    │   └── rome.json
+    └── frontend
+        ├── legacy
+        │   └── package.json
+        ├── new
+        │   └── package.json
+        └── rome.json
+
+```
+
+- rome commands that run in `app/backend/package.json` will use the configuration file `app/backend/rome.json`;
+- rome commands that run in `app/frontend/legacy/package.json` and `app/frontend/new/package.json`
+will use the configuration file `app/frontend/rome.json`;
+
 ## `$schema`
 
 Allows to pass a path to a JSON schema file.