correct description of fallback for user-level settings

Co-authored-by: Micha Reiser <micha@reiser.io>

Author: dylwil3

docs/configuration.md

@@ -280,7 +280,7 @@ The rules for this behavior are as follows:
 
 1. If a configuration file is passed directly, Ruff does not attempt to infer a missing `target-version`.
 1. If a configuration file is found in the filesystem hierarchy, Ruff will infer a missing `target-version` from the `requires-python` field in a `pyproject.toml` file in the same directory as the found configuration.
-1. If we are using a user-level configuration from `${config_dir}/ruff/pyproject.toml`, Ruff will infer a missing `target-version` from the `requires-python` field in the first `pyproject.toml` file found in an ancestor of the current working directory.
+1. If we are using a user-level configuration from `${config_dir}/ruff/pyproject.toml`, the `requires-python` field in the first `pyproject.toml` file found in an ancestor of the current working directory takes precedence over the `target-version` in the user-level configuration.
 1. If no configuration files are found, Ruff will infer the `target-version` from the `requires-python` field in the first `pyproject.toml` file found in an ancestor of the current working directory.
 
 Note that in these last two cases, the behavior of Ruff may differ depending on the working directory from which it is invoked.