diff --git a/src/doc/rustc-dev-guide/src/building/new-target.md b/src/doc/rustc-dev-guide/src/building/new-target.md
index 1be83e4a5a58..73174aaa0adf 100644
--- a/src/doc/rustc-dev-guide/src/building/new-target.md
+++ b/src/doc/rustc-dev-guide/src/building/new-target.md
@@ -72,8 +72,7 @@ somewhat successfully, you can copy the specification into the compiler itself.
 
 You will need to add a line to the big table inside of the
 `supported_targets` macro in the `rustc_target::spec` module.
-You will then add a corresponding file for your new target containing a
-`target` function.
+You will then add a corresponding file for your new target containing a `target` function.
 
 Look for existing targets to use as examples.
 
diff --git a/src/doc/rustc-dev-guide/src/building/optimized-build.md b/src/doc/rustc-dev-guide/src/building/optimized-build.md
index 4953e2004a4c..0a6b82eba46a 100644
--- a/src/doc/rustc-dev-guide/src/building/optimized-build.md
+++ b/src/doc/rustc-dev-guide/src/building/optimized-build.md
@@ -55,9 +55,8 @@ rust.codegen-units-std = 1
 
 By default, `rustc` is compiled for a generic (and conservative) instruction set architecture
 (depending on the selected target), to make it support as many CPUs as possible.
-If you want to
-compile `rustc` for a specific instruction set architecture, you can set the `target_cpu` compiler
-option in `RUSTFLAGS`:
+If you want to compile `rustc` for a specific instruction set architecture,
+you can set the `target_cpu` compiler option in `RUSTFLAGS`:
 
 ```bash
 RUSTFLAGS="-C target_cpu=x86-64-v3" ./x build ...
diff --git a/src/doc/rustc-dev-guide/src/building/suggested.md b/src/doc/rustc-dev-guide/src/building/suggested.md
index af4dc0ab699c..3ed4f129d144 100644
--- a/src/doc/rustc-dev-guide/src/building/suggested.md
+++ b/src/doc/rustc-dev-guide/src/building/suggested.md
@@ -118,8 +118,7 @@ requires extra disk space.
 
 Selecting `vscode` in `./x setup editor` will prompt you to create a
 `.vscode/settings.json` file which will configure Visual Studio code.
-The recommended `rust-analyzer` settings live at
-[`src/etc/rust_analyzer_settings.json`].
+The recommended `rust-analyzer` settings live at [`src/etc/rust_analyzer_settings.json`].
 
 If running `./x check` on save is inconvenient, in VS Code you can use a [Build Task] instead:
 
@@ -253,8 +252,7 @@ It can be configured through `.zed/settings.json`, as described
 [here](https://zed.dev/docs/configuring-languages).
 Selecting `zed` in `./x setup editor` will prompt you to create a `.zed/settings.json`
 file which will configure Zed with the recommended configuration.
-The recommended `rust-analyzer` settings live
-at [`src/etc/rust_analyzer_zed.json`].
+The recommended `rust-analyzer` settings live at [`src/etc/rust_analyzer_zed.json`].
 
 ## Check, check, and check again