Fix existing messages in stderrs

tests/rustdoc-ui/ice-bug-report-url.stderr

@@ -9,7 +9,7 @@ LL | fn wrong()
 aborting due to `-Z treat-err-as-bug=1`
 stack backtrace:
 
-error: the compiler unexpectedly panicked. this is a bug.
+error: the compiler unexpectedly panicked. This is a bug
 
 note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-rustdoc&template=ice.md
 

tests/ui/consts/const-eval/field-access-after-const-eval-fail-in-ty.stderr

@@ -5,7 +5,7 @@ LL |     [(); loop {}].field;
    |          ^^^^^^^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/field-access-after-const-eval-fail-in-ty.rs:4:10
    |

tests/ui/consts/const-eval/infinite_loop.eval_limit.stderr

@@ -8,7 +8,7 @@ LL | |         }
    | |_________^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/infinite_loop.rs:13:18
    |

tests/ui/consts/const-eval/infinite_loop.no_ice.stderr

@@ -8,7 +8,7 @@ LL | |         }
    | |_________^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/infinite_loop.rs:13:18
    |

tests/ui/consts/const-eval/issue-52475.stderr

@@ -9,7 +9,7 @@ LL | |         }
    | |_________^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/issue-52475.rs:2:18
    |

tests/ui/consts/const-eval/issue-70723.stderr

@@ -5,7 +5,7 @@ LL | static _X: () = loop {};
    |                 ^^^^^^^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/issue-70723.rs:1:1
    |

tests/ui/consts/const-eval/stable-metric/ctfe-fn-call.stderr

@@ -5,7 +5,7 @@ LL |     foo();
    |     ^^^^^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/ctfe-fn-call.rs:32:1
    |

tests/ui/consts/const-eval/stable-metric/ctfe-labelled-loop.stderr

@@ -11,7 +11,7 @@ LL | |     }
    | |_____^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/ctfe-labelled-loop.rs:16:1
    |

tests/ui/consts/const-eval/stable-metric/ctfe-recursion.stderr

@@ -5,7 +5,7 @@ LL |         recurse(n - 1)
    |         ^^^^^^^^^^^^^^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/ctfe-recursion.rs:13:1
    |

tests/ui/consts/const-eval/stable-metric/ctfe-simple-loop.warn.stderr

@@ -7,7 +7,7 @@ LL | |     }
    | |_____^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/ctfe-simple-loop.rs:19:1
    |
@@ -28,7 +28,7 @@ LL | |     }
    | |_____^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/ctfe-simple-loop.rs:20:1
    |

tests/ui/consts/do-not-ice-long-constant-evaluation-in-for-loop.stderr

@@ -5,7 +5,7 @@ LL |         [(); loop {}];
    |              ^^^^^^^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/do-not-ice-long-constant-evaluation-in-for-loop.rs:10:14
    |

tests/ui/consts/do-not-ice-on-field-access-of-err-type.stderr

@@ -5,7 +5,7 @@ LL |     let array = [(); { loop {} }];
    |                        ^^^^^^^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/do-not-ice-on-field-access-of-err-type.rs:5:22
    |

tests/ui/consts/timeout.stderr

@@ -7,7 +7,7 @@ error: constant evaluation is taking a long time
    = note: in this macro invocation
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/timeout.rs:7:1
    |

tests/ui/error-codes/E0010-teach.stderr

@@ -4,7 +4,7 @@ error[E0010]: allocations are not allowed in constants
 LL | const CON: Vec<i32> = vec![1, 2, 3];
    |                       ^^^^^^^^^^^^^ allocation not allowed in constants
    |
-   = note: The runtime heap is not yet available at compile-time, so no runtime heap allocations can be created.
+   = note: the runtime heap is not yet available at compile-time, so no runtime heap allocations can be created
 
 error[E0015]: cannot call non-const method `slice::<impl [i32]>::into_vec::<std::alloc::Global>` in constants
   --> $DIR/E0010-teach.rs:5:23

tests/ui/error-codes/E0030-teach.stderr

@@ -4,7 +4,7 @@ error[E0030]: lower bound for range pattern must be less than or equal to upper
 LL |         1000 ..= 5 => {}
    |         ^^^^^^^^^^ lower bound larger than upper bound
    |
-   = note: When matching against a range, the compiler verifies that the range is non-empty. Range patterns include both end-points, so this is equivalent to requiring the start of the range to be less than or equal to the end of the range.
+   = note: when matching against a range, the compiler verifies that the range is non-empty. Range patterns include both end-points, so this is equivalent to requiring the start of the range to be less than or equal to the end of the range
 
 error: aborting due to 1 previous error
 

tests/ui/explicit-tail-calls/infinite-recursion-in-ctfe.stderr

@@ -5,7 +5,7 @@ LL |     become f();
    |     ^^^^^^^^^^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/infinite-recursion-in-ctfe.rs:4:1
    |

tests/ui/layout/valid_range_oob.stderr

@@ -1,6 +1,6 @@
 
 257 > 255
-error: the compiler unexpectedly panicked. this is a bug.
+error: the compiler unexpectedly panicked. This is a bug
 
 query stack during panic:
 #0 [layout_of] computing layout of `Foo`

tests/ui/mir/lint/storage-live.stderr

@@ -13,7 +13,7 @@ LL |             StorageLive(a);
 
 
 aborting due to `-Z treat-err-as-bug=1`
-error: the compiler unexpectedly panicked. this is a bug.
+error: the compiler unexpectedly panicked. This is a bug
 
 query stack during panic:
 end of query stack

tests/ui/panics/default-backtrace-ice.stderr

@@ -13,7 +13,7 @@ stack backtrace:
 (end_short_backtrace)
 (begin_short_backtrace)
 
-error: the compiler unexpectedly panicked. this is a bug.
+error: the compiler unexpectedly panicked. This is a bug
 
 
 

tests/ui/privacy/no-ice-on-inference-failure.stderr

@@ -8,7 +8,7 @@ LL | |         }
    | |_________^
    |
    = note: this lint makes sure the compiler doesn't get stuck due to infinite loops in const eval.
-           If your compilation actually takes a long time, you can safely allow the lint.
+           If your compilation actually takes a long time, you can safely allow the lint
 help: the constant being evaluated
   --> $DIR/no-ice-on-inference-failure.rs:2:22
    |

tests/ui/sanitizer/kcfi-arity-requires-llvm-21-0-0.rs

@@ -5,7 +5,7 @@
 //@ build-fail
 //@ max-llvm-major-version: 20
 
-//~? ERROR `-Zsanitizer-kcfi-arity` requires LLVM 21.0.0 or later.
+//~? ERROR `-Zsanitizer-kcfi-arity` requires LLVM 21.0.0 or later
 #![feature(no_core)]
 #![no_core]
 #![no_main]

tests/ui/sanitizer/kcfi-arity-requires-llvm-21-0-0.stderr

@@ -1,4 +1,4 @@
-error: `-Zsanitizer-kcfi-arity` requires LLVM 21.0.0 or later.
+error: `-Zsanitizer-kcfi-arity` requires LLVM 21.0.0 or later
 
 error: aborting due to 1 previous error
 

tests/ui/treat-err-as-bug/err.stderr

@@ -5,7 +5,7 @@ LL | pub static C: u32 = 0 - 1;
    |                     ^^^^^ evaluation of `C` failed here
 
 
-error: the compiler unexpectedly panicked. this is a bug.
+error: the compiler unexpectedly panicked. This is a bug
 
 query stack during panic:
 #0 [eval_static_initializer] evaluating initializer of static `C`

tests/ui/treat-err-as-bug/span_delayed_bug.stderr

@@ -5,7 +5,7 @@ LL | fn main() {}
    | ^^^^^^^^^
 
 
-error: the compiler unexpectedly panicked. this is a bug.
+error: the compiler unexpectedly panicked. This is a bug
 
 query stack during panic:
 #0 [trigger_delayed_bug] triggering a delayed bug for testing incremental