fix clippy::doc_overindented_list_items

Author: BenjaminBrienen

crates/project-model/src/project_json.rs

@@ -85,8 +85,7 @@ impl ProjectJson {
     ///
     /// * `manifest` - The path to the `rust-project.json`.
     /// * `base` - The path to the workspace root (i.e. the folder containing `rust-project.json`)
-    /// * `data` - The parsed contents of `rust-project.json`, or project json that's passed via
-    ///   configuration.
+    /// * `data` - The parsed contents of `rust-project.json`, or project json that's passed via configuration.
     pub fn new(
         manifest: Option<ManifestPath>,
         base: &AbsPath,

crates/toolchain/src/lib.rs

@@ -27,14 +27,14 @@ impl Tool {
     ///
     /// The current implementation checks three places for an executable to use:
     /// 1) `$CARGO_HOME/bin/<executable_name>`
-    ///      where $CARGO_HOME defaults to ~/.cargo (see <https://doc.rust-lang.org/cargo/guide/cargo-home.html>)
-    ///      example: for cargo, this tries $CARGO_HOME/bin/cargo, or ~/.cargo/bin/cargo if $CARGO_HOME is unset.
-    ///      It seems that this is a reasonable place to try for cargo, rustc, and rustup
+    ///    where $CARGO_HOME defaults to ~/.cargo (see <https://doc.rust-lang.org/cargo/guide/cargo-home.html>)
+    ///    example: for cargo, this tries $CARGO_HOME/bin/cargo, or ~/.cargo/bin/cargo if $CARGO_HOME is unset.
+    ///    It seems that this is a reasonable place to try for cargo, rustc, and rustup
     /// 2) Appropriate environment variable (erroring if this is set but not a usable executable)
-    ///      example: for cargo, this checks $CARGO environment variable; for rustc, $RUSTC; etc
+    ///    example: for cargo, this checks $CARGO environment variable; for rustc, $RUSTC; etc
     /// 3) $PATH/`<executable_name>`
-    ///      example: for cargo, this tries all paths in $PATH with appended `cargo`, returning the
-    ///      first that exists
+    ///    example: for cargo, this tries all paths in $PATH with appended `cargo`, returning the
+    ///    first that exists
     /// 4) If all else fails, we just try to use the executable name directly
     pub fn prefer_proxy(self) -> Utf8PathBuf {
         invoke(&[cargo_proxy, lookup_as_env_var, lookup_in_path], self.name())
@@ -44,14 +44,14 @@ impl Tool {
     ///
     /// The current implementation checks three places for an executable to use:
     /// 1) Appropriate environment variable (erroring if this is set but not a usable executable)
-    ///      example: for cargo, this checks $CARGO environment variable; for rustc, $RUSTC; etc
+    ///    example: for cargo, this checks $CARGO environment variable; for rustc, $RUSTC; etc
     /// 2) $PATH/`<executable_name>`
-    ///      example: for cargo, this tries all paths in $PATH with appended `cargo`, returning the
-    ///      first that exists
+    ///    example: for cargo, this tries all paths in $PATH with appended `cargo`, returning the
+    ///    first that exists
     /// 3) `$CARGO_HOME/bin/<executable_name>`
-    ///      where $CARGO_HOME defaults to ~/.cargo (see <https://doc.rust-lang.org/cargo/guide/cargo-home.html>)
-    ///      example: for cargo, this tries $CARGO_HOME/bin/cargo, or ~/.cargo/bin/cargo if $CARGO_HOME is unset.
-    ///      It seems that this is a reasonable place to try for cargo, rustc, and rustup
+    ///    where $CARGO_HOME defaults to ~/.cargo (see <https://doc.rust-lang.org/cargo/guide/cargo-home.html>)
+    ///    example: for cargo, this tries $CARGO_HOME/bin/cargo, or ~/.cargo/bin/cargo if $CARGO_HOME is unset.
+    ///    It seems that this is a reasonable place to try for cargo, rustc, and rustup
     /// 4) If all else fails, we just try to use the executable name directly
     pub fn path(self) -> Utf8PathBuf {
         invoke(&[lookup_as_env_var, lookup_in_path, cargo_proxy], self.name())