reflow

src/doc/rustc-dev-guide/src/compiler-debugging.md

@@ -55,8 +55,7 @@ If this is not desirable, you can prevent the ICE file from being created with `
 
 When you have an ICE (panic in the compiler), you can set
 `RUST_BACKTRACE=1` to get the stack trace of the `panic!` like in normal Rust programs.
-IIRC backtraces **don't work** on MinGW,
-sorry.
+IIRC backtraces **don't work** on MinGW, sorry.
 If you have trouble or the backtraces are full of `unknown`,
 you might want to find some way to use Linux, Mac, or MSVC on Windows.
 

src/doc/rustc-dev-guide/src/tests/compiletest.md

@@ -277,8 +277,7 @@ the debugger currently being used:
   gdb is in a range (inclusive)
 - `min-lldb-version: 310` — ignores the test if the version of lldb is below the given version
 - `rust-lldb` — ignores the test if lldb is not contain the Rust plugin.
-  NOTE: The "Rust" version of LLDB doesn't exist anymore, so this will always be
-  ignored.
+  NOTE: The "Rust" version of LLDB doesn't exist anymore, so this will always be ignored.
   This should probably be removed.
 
 By passing the `--debugger` option to compiletest, you can specify a single debugger to run tests with.

src/doc/rustc-dev-guide/src/tracing.md

@@ -74,8 +74,7 @@ RUSTC_LOG=[typeck]
 The query arguments are included as a tracing field which means that you can
 filter on the debug display of the arguments.
 For example, the `typeck` query has an argument `key: LocalDefId` of what is being checked.
-You can use a regex to match on that `LocalDefId` to log type checking for a specific
-function:
+You can use a regex to match on that `LocalDefId` to log type checking for a specific function:
 
 ```
 RUSTC_LOG=[typeck{key=.*name_of_item.*}]