it-self → itself, build-system → build system, type-alias → type alias

Author: tbu-

compiler/rustc_session/src/config/cfg.rs

@@ -9,7 +9,7 @@
 //!
 //! ## Adding a new cfg
 //!
-//! Adding a new feature requires two new symbols one for the cfg it-self
+//! Adding a new feature requires two new symbols one for the cfg itself
 //! and the second one for the unstable feature gate, those are defined in
 //! `rustc_span::symbol`.
 //!

src/doc/rustc/src/check-cfg.md

@@ -135,7 +135,7 @@ As of `2025-01-02T`, the list of known names is as follows:
  - `windows`
 
 > Starting with 1.85.0, the `test` cfg is consider to be a "userspace" config
-> despite being also set by `rustc` and should be managed by the build-system it-self.
+> despite being also set by `rustc` and should be managed by the build system itself.
 
 Like with `values(any())`, well known names checking can be disabled by passing `cfg(any())`
 as argument to `--check-cfg`.

src/doc/rustc/src/platform-support/unknown-uefi.md

@@ -116,7 +116,7 @@ There are 3 common ways to compile native C code for UEFI targets:
 - Use the official SDK by Intel:
   [Tianocore/EDK2](https://github.com/tianocore/edk2). This supports a
   multitude of platforms, comes with the full specification transposed into C,
-  lots of examples and build-system integrations. This is also the only
+  lots of examples and build system integrations. This is also the only
   officially supported platform by Intel, and is used by many major firmware
   implementations. Any code compiled via the SDK is compatible to rust binaries
   compiled for the UEFI targets. You can link them directly into your rust

src/librustdoc/passes/strip_aliased_non_local.rs

@@ -26,7 +26,7 @@ impl DocFolder for AliasedNonLocalStripper<'_> {
         Some(match i.kind {
             clean::TypeAliasItem(..) => {
                 let mut stripper = NonLocalStripper { tcx: self.tcx };
-                // don't call `fold_item` as that could strip the type-alias it-self
+                // don't call `fold_item` as that could strip the type alias itself
                 // which we don't want to strip out
                 stripper.fold_item_recur(i)
             }