Fix nested lists in CONTRIBUTING.md (#5721)

## Summary

We have a lot of two-space-indented stuff, but apparently it needs to be
four-space indented to render as expected in MkDocs.

docs/configuration.md

@@ -106,13 +106,13 @@ formats. Ruff will automatically disable any conflicting rules when `ALL` is ena
 If you're wondering how to configure Ruff, here are some **recommended guidelines**:
 
 - Prefer `select` and `ignore` over `extend-select` and `extend-ignore`, to make your rule set
-  explicit.
+    explicit.
 - Use `ALL` with discretion. Enabling `ALL` will implicitly enable new rules whenever you upgrade.
 - Start with a small set of rules (`select = ["E", "F"]`) and add a category at-a-time. For example,
-  you might consider expanding to `select = ["E", "F", "B"]` to enable the popular flake8-bugbear
-  extension.
+    you might consider expanding to `select = ["E", "F", "B"]` to enable the popular flake8-bugbear
+    extension.
 - By default, Ruff's autofix is aggressive. If you find that it's too aggressive for your liking,
-  consider turning off autofix for specific rules or categories (see [_FAQ_](faq.md#ruff-tried-to-fix-something--but-it-broke-my-code)).
+    consider turning off autofix for specific rules or categories (see [_FAQ_](faq.md#ruff-tried-to-fix-something--but-it-broke-my-code)).
 
 ## Using `ruff.toml`
 
@@ -284,17 +284,17 @@ directory hierarchy is used for every individual file, with all paths in the `py
 There are a few exceptions to these rules:
 
 1. In locating the "closest" `pyproject.toml` file for a given path, Ruff ignores any
-   `pyproject.toml` files that lack a `[tool.ruff]` section.
+    `pyproject.toml` files that lack a `[tool.ruff]` section.
 1. If a configuration file is passed directly via `--config`, those settings are used for across
-   files. Any relative paths in that configuration file (like `exclude` globs or `src` paths) are
-   resolved relative to the _current working directory_.
+    files. Any relative paths in that configuration file (like `exclude` globs or `src` paths) are
+    resolved relative to the _current working directory_.
 1. If no `pyproject.toml` file is found in the filesystem hierarchy, Ruff will fall back to using
-   a default configuration. If a user-specific configuration file exists
-   at `${config_dir}/ruff/pyproject.toml`, that file will be used instead of the default
-   configuration, with `${config_dir}` being determined via the [`dirs`](https://docs.rs/dirs/4.0.0/dirs/fn.config_dir.html)
-   crate, and all relative paths being again resolved relative to the _current working directory_.
+    a default configuration. If a user-specific configuration file exists
+    at `${config_dir}/ruff/pyproject.toml`, that file will be used instead of the default
+    configuration, with `${config_dir}` being determined via the [`dirs`](https://docs.rs/dirs/4.0.0/dirs/fn.config_dir.html)
+    crate, and all relative paths being again resolved relative to the _current working directory_.
 1. Any `pyproject.toml`-supported settings that are provided on the command-line (e.g., via
-   `--select`) will override the settings in _every_ resolved configuration file.
+    `--select`) will override the settings in _every_ resolved configuration file.
 
 Unlike [ESLint](https://eslint.org/docs/latest/user-guide/configuring/configuration-files#cascading-and-hierarchy),
 Ruff does not merge settings across configuration files; instead, the "closest" configuration file
@@ -462,18 +462,18 @@ By default, Ruff exits with the following status codes:
 - `0` if no violations were found, or if all present violations were fixed automatically.
 - `1` if violations were found.
 - `2` if Ruff terminates abnormally due to invalid configuration, invalid CLI options, or an
-  internal error.
+    internal error.
 
 This convention mirrors that of tools like ESLint, Prettier, and RuboCop.
 
 Ruff supports two command-line flags that alter its exit code behavior:
 
 - `--exit-zero` will cause Ruff to exit with a status code of `0` even if violations were found.
-  Note that Ruff will still exit with a status code of `2` if it terminates abnormally.
+    Note that Ruff will still exit with a status code of `2` if it terminates abnormally.
 - `--exit-non-zero-on-fix` will cause Ruff to exit with a status code of `1` if violations were
-  found, _even if_ all such violations were fixed automatically. Note that the use of
-  `--exit-non-zero-on-fix` can result in a non-zero exit code even if no violations remain after
-  autofixing.
+    found, _even if_ all such violations were fixed automatically. Note that the use of
+    `--exit-non-zero-on-fix` can result in a non-zero exit code even if no violations remain after
+    autofixing.
 
 ## Autocompletion
 

docs/faq.md

@@ -94,8 +94,8 @@ There are a few other minor incompatibilities between Ruff and the originating F
 
 - Ruff doesn't implement all the "opinionated" lint rules from flake8-bugbear.
 - Depending on your project structure, Ruff and isort can differ in their detection of first-party
-  code. (This is often solved by modifying the `src` property, e.g., to `src = ["src"]`, if your
-  code is nested in a `src` directory.)
+    code. (This is often solved by modifying the `src` property, e.g., to `src = ["src"]`, if your
+    code is nested in a `src` directory.)
 
 ## How does Ruff compare to Pylint?