Use indent size of 4 for documentation

.editorconfig

@@ -18,3 +18,4 @@ trim_trailing_whitespace = false
 
 [*.md]
 max_line_length = 100
+indent_size = 4

.github/workflows/ci.yml

@@ -59,7 +59,7 @@ jobs:
       - name: "Prettier"
         run: |
           npx prettier --check "**/*.{json5,yaml,yml}"
-          npx prettier --prose-wrap always --check "**/*.md"
+          npx prettier --prose-wrap always --tab-width 4 --check "**/*.md"
 
       - name: "README check"
         run: python scripts/transform_readme.py --target pypi

BENCHMARKS.md

@@ -3,17 +3,18 @@
 All benchmarks were computed on macOS using Python 3.12.0 (for non-uv tools), and come with a few
 important caveats:
 
-- Benchmark performance may vary dramatically across different operating systems and filesystems. In
-  particular, uv uses different installation strategies based on the underlying filesystem's
-  capabilities. (For example, uv uses reflinking on macOS, and hardlinking on Linux.)
-- Benchmark performance may vary dramatically depending on the set of packages being installed. For
-  example, a resolution that requires building a single intensive source distribution may appear
-  very similar across tools, since the bottleneck is tool-agnostic.
-- Unlike Poetry, both uv and pip-tools do _not_ generate platform-independent lockfiles. As such,
-  Poetry is (by design) doing significantly more work than other tools in the resolution benchmarks.
-  Poetry is included for completeness, as many projects may not _need_ a platform-independent
-  lockfile. However, it's critical to understand that benchmarking uv's resolution time against
-  Poetry is an unfair comparison. (Benchmarking installation, however, _is_ a fair comparison.)
+-   Benchmark performance may vary dramatically across different operating systems and filesystems.
+    In particular, uv uses different installation strategies based on the underlying filesystem's
+    capabilities. (For example, uv uses reflinking on macOS, and hardlinking on Linux.)
+-   Benchmark performance may vary dramatically depending on the set of packages being installed.
+    For example, a resolution that requires building a single intensive source distribution may
+    appear very similar across tools, since the bottleneck is tool-agnostic.
+-   Unlike Poetry, both uv and pip-tools do _not_ generate platform-independent lockfiles. As such,
+    Poetry is (by design) doing significantly more work than other tools in the resolution
+    benchmarks. Poetry is included for completeness, as many projects may not _need_ a
+    platform-independent lockfile. However, it's critical to understand that benchmarking uv's
+    resolution time against Poetry is an unfair comparison. (Benchmarking installation, however,
+    _is_ a fair comparison.)
 
 This document benchmarks against Trio's `docs-requirements.in`, as a representative example of a
 real-world project.
@@ -60,10 +61,10 @@ of other tools.
 
 The benchmark script itself has a several requirements:
 
-- A local uv release build (`cargo build --release`).
-- An installation of the production `uv` binary in your path.
-- The [`hyperfine`](https://github.com/sharkdp/hyperfine) command-line tool installed on your
-  system.
+-   A local uv release build (`cargo build --release`).
+-   An installation of the production `uv` binary in your path.
+-   The [`hyperfine`](https://github.com/sharkdp/hyperfine) command-line tool installed on your
+    system.
 
 To benchmark resolution against pip-compile, Poetry, and PDM:
 

CONTRIBUTING.md

@@ -141,13 +141,13 @@ To preview any changes to the documentation locally:
 
 1. Run the development server with:
 
-   ```shell
-   # For contributors.
-   uvx --with-requirements docs/requirements.txt -- mkdocs serve -f mkdocs.public.yml
+    ```shell
+    # For contributors.
+    uvx --with-requirements docs/requirements.txt -- mkdocs serve -f mkdocs.public.yml
 
-   # For members of the Astral org, which has access to MkDocs Insiders via sponsorship.
-   uvx --with-requirements docs/requirements-insiders.txt -- mkdocs serve -f mkdocs.insiders.yml
-   ```
+    # For members of the Astral org, which has access to MkDocs Insiders via sponsorship.
+    uvx --with-requirements docs/requirements-insiders.txt -- mkdocs serve -f mkdocs.insiders.yml
+    ```
 
 The documentation should then be available locally at
 [http://127.0.0.1:8000/uv/](http://127.0.0.1:8000/uv/).
@@ -167,7 +167,7 @@ Cloudflare Pages.
 After making changes to the documentation, format the markdown files with:
 
 ```shell
-npx prettier --prose-wrap always --write "**/*.md"
+npx prettier --prose-wrap always --tab-width 4 --write "**/*.md"
 ```
 
 ## Releases

PIP_COMPATIBILITY.md

@@ -97,11 +97,11 @@ the specifier, since it was provided as a direct dependency.
 
 As compared to pip, the main differences in observed behavior are as follows:
 
-- In general, local versions must be provided as direct dependencies. Resolution may succeed for
-  transitive dependencies that request a non-local version, but this is not guaranteed.
-- If _only_ local versions exist for a package `foo` at a given version (e.g., `1.2.3+local` exists,
-  but `1.2.3` does not), `uv pip install foo==1.2.3` will fail, while `pip install foo==1.2.3` will
-  resolve to an arbitrary local version.
+-   In general, local versions must be provided as direct dependencies. Resolution may succeed for
+    transitive dependencies that request a non-local version, but this is not guaranteed.
+-   If _only_ local versions exist for a package `foo` at a given version (e.g., `1.2.3+local`
+    exists, but `1.2.3` does not), `uv pip install foo==1.2.3` will fail, while
+    `pip install foo==1.2.3` will resolve to an arbitrary local version.
 
 ## Packages that exist on multiple indexes
 
@@ -137,13 +137,13 @@ As of v0.1.39, users can opt in to `pip`-style behavior for multiple indexes via
 `--index-strategy` command-line option, or the `UV_INDEX_STRATEGY` environment variable, which
 supports the following values:
 
-- `first-match` (default): Search for each package across all indexes, limiting the candidate
-  versions to those present in the first index that contains the package, prioritizing the
-  `--extra-index-url` indexes over the default index URL.
-- `unsafe-first-match`: Search for each package across all indexes, but prefer the first index with
-  a compatible version, even if newer versions are available on other indexes.
-- `unsafe-best-match`: Search for each package across all indexes, and select the best version from
-  the combined set of candidate versions.
+-   `first-match` (default): Search for each package across all indexes, limiting the candidate
+    versions to those present in the first index that contains the package, prioritizing the
+    `--extra-index-url` indexes over the default index URL.
+-   `unsafe-first-match`: Search for each package across all indexes, but prefer the first index
+    with a compatible version, even if newer versions are available on other indexes.
+-   `unsafe-best-match`: Search for each package across all indexes, and select the best version
+    from the combined set of candidate versions.
 
 While `unsafe-best-match` is the closest to `pip`'s behavior, it exposes users to the risk of
 "dependency confusion" attacks.
@@ -298,12 +298,12 @@ too loose, and that the user should consider tightening them. For example, in th
 
 At present, `uv pip check` will surface the following diagnostics:
 
-- A package has no `METADATA` file, or the `METADATA` file can't be parsed.
-- A package has a `Requires-Python` that doesn't match the Python version of the running
-  interpreter.
-- A package has a dependency on a package that isn't installed.
-- A package has a dependency on a package that's installed, but at an incompatible version.
-- Multiple versions of a package are installed in the virtual environment.
+-   A package has no `METADATA` file, or the `METADATA` file can't be parsed.
+-   A package has a `Requires-Python` that doesn't match the Python version of the running
+    interpreter.
+-   A package has a dependency on a package that isn't installed.
+-   A package has a dependency on a package that's installed, but at an incompatible version.
+-   Multiple versions of a package are installed in the virtual environment.
 
 In some cases, `uv pip check` will surface diagnostics that `pip check` does not, and vice versa.
 For example, unlike `uv pip check`, `pip check` will _not_ warn when multiple versions of a package
@@ -364,8 +364,8 @@ does support a large subset.
 Missing options and subcommands are prioritized based on user demand and the complexity of the
 implementation, and tend to be tracked in individual issues. For example:
 
-- [`--trusted-host`](https://github.com/astral-sh/uv/issues/1339)
-- [`--user`](https://github.com/astral-sh/uv/issues/2077)
+-   [`--trusted-host`](https://github.com/astral-sh/uv/issues/1339)
+-   [`--user`](https://github.com/astral-sh/uv/issues/2077)
 
 If you encounter a missing option or subcommand, please search the issue tracker to see if it has
 already been reported, and if not, consider opening a new issue. Feel free to upvote any existing