Rust version policy: remove spurious newline

Signed-off-by: Miguel Ojeda <[email protected]>

Author: ojeda

src/Rust-version-policy.md

@@ -8,8 +8,7 @@ For the moment, we cannot guarantee newer Rust versions will always work due to
 
 To ameliorate that, the kernel is now being built-tested by Rust's pre-merge CI. That is, every change that is attempting to land into the Rust compiler is tested against the kernel, and it is merged only if it passes. Similarly, the `bindgen` tool is also building the kernel in their pre-merge CI too.
 
-Thus, with the pre-merge CI in place, those projects hope to avoid unintentional changes to Rust that break the kernel. This means that, in general, apart from intentional changes on their side (that we will need to workaround conditionally on our side), the upcoming Rust
-compiler versions should generally work. This applies to beta and nightly versions of Rust as well.
+Thus, with the pre-merge CI in place, those projects hope to avoid unintentional changes to Rust that break the kernel. This means that, in general, apart from intentional changes on their side (that we will need to workaround conditionally on our side), the upcoming Rust compiler versions should generally work. This applies to beta and nightly versions of Rust as well.
 
 In addition, the Rust project has proposed getting the kernel into stable Rust (at least solving the main blockers) as one of its three [flagship goals for 2024H2](https://rust-lang.github.io/rust-project-goals/2024h2/index.html#flagship-goals).