Fix some comment typos in tests

Author: teor2345

tests/coverage/assert.coverage

@@ -27,7 +27,7 @@
    LL|       |//   3. Notably, the `assert` macros *do not* generate `TerminatorKind::Assert`. The macros produce
    LL|       |//      conditional expressions, `TerminatorKind::SwitchInt` branches, and a possible call to
    LL|       |//      `begin_panic_fmt()` (that begins a panic unwind, if the assertion test fails).
-   LL|       |//   4. `TerminatoKind::Assert` is, however, also present in the MIR generated for this test
+   LL|       |//   4. `TerminatorKind::Assert` is, however, also present in the MIR generated for this test
    LL|       |//      (and in many other coverage tests). The `Assert` terminator is typically generated by the
    LL|       |//      Rust compiler to check for runtime failures, such as numeric overflows.
 

tests/coverage/assert.rs

@@ -27,6 +27,6 @@ fn main() -> Result<(), u8> {
 //   3. Notably, the `assert` macros *do not* generate `TerminatorKind::Assert`. The macros produce
 //      conditional expressions, `TerminatorKind::SwitchInt` branches, and a possible call to
 //      `begin_panic_fmt()` (that begins a panic unwind, if the assertion test fails).
-//   4. `TerminatoKind::Assert` is, however, also present in the MIR generated for this test
+//   4. `TerminatorKind::Assert` is, however, also present in the MIR generated for this test
 //      (and in many other coverage tests). The `Assert` terminator is typically generated by the
 //      Rust compiler to check for runtime failures, such as numeric overflows.

tests/ui/argument-suggestions/exotic-calls.rs

@@ -1,4 +1,4 @@
-//! Checks variations of E0057, which is the incorrect number of agruments passed into a closure
+//! Checks variations of E0057, which is the incorrect number of arguments passed into a closure
 
 //@ check-fail