Merge pull request #2795 from rust-lang/tshepang/sembr

sembr a few files

Author: tshepang

src/backend/updating-llvm.md

@@ -7,9 +7,11 @@ Rust supports building against multiple LLVM versions:
   PRs for such fixes are tagged with `llvm-main`.
 * The latest released major version is always supported.
 * The one or two preceding major versions are usually supported in the sense that they are expected
-  to build successfully and pass most tests. However, fixes for miscompilations often do not get
+  to build successfully and pass most tests.
+  However, fixes for miscompilations often do not get
   backported to past LLVM versions, so using rustc with older versions of LLVM comes with an
-  increased risk of soundness bugs. We strongly recommend using the latest version of LLVM.
+  increased risk of soundness bugs.
+  We strongly recommend using the latest version of LLVM.
 
 By default, Rust uses its own fork in the [rust-lang/llvm-project repository].
 This fork is based on a `release/$N.x` branch of the upstream project, where

src/diagnostics/translation.md

@@ -31,8 +31,7 @@ There are two ways of writing translatable diagnostics:
    ("Simple" diagnostics being those that don't require a lot of logic in
    deciding to emit subdiagnostics and can therefore be represented as diagnostic structs).
    See [the diagnostic and subdiagnostic structs documentation](./diagnostic-structs.md).
-2. Using typed identifiers with `Diag` APIs (in
-   `Diagnostic` or `Subdiagnostic` implementations).
+2. Using typed identifiers with `Diag` APIs (in `Diagnostic` or `Subdiagnostic` implementations).
 
 When adding or changing a translatable diagnostic,
 you don't need to worry about the translations.

src/git.md

@@ -383,7 +383,9 @@ Both the upside and downside of this is that it simplifies the history.
 On the one hand, you lose track of the steps in which changes were made, but
 the history becomes easier to work with.
 
-The easiest way to squash your commits in a PR on the `rust-lang/rust` repository is to use the `@bors squash` command in a comment on the PR. By default, [bors] combines all commit messages of the PR into the squashed commit message. To customize the commit message, use `@bors squash msg=<commit message>`.
+The easiest way to squash your commits in a PR on the `rust-lang/rust` repository is to use the `@bors squash` command in a comment on the PR.
+By default, [bors] combines all commit messages of the PR into the squashed commit message.
+To customize the commit message, use `@bors squash msg=<commit message>`.
 
 
 If you want to squash commits using local git operations, read on below.

src/tracing.md

@@ -14,8 +14,8 @@ of `tracing-subscriber`](https://docs.rs/tracing-subscriber/0.2.24/tracing_subsc
 
 ## Environment variables
 
-This is an overview of the environment variables rustc accepts to customize
-its tracing output. The definition of these can mostly be found in `compiler/rustc_log/src/lib.rs`.
+This is an overview of the environment variables rustc accepts to customize its tracing output.
+The definition of these can mostly be found in `compiler/rustc_log/src/lib.rs`.
 
 |  Name                     | Usage                                                                                                                   |
 | ------------------------- | ----------------------------------------------------------------------------------------------------------------------- |