diff options
| author | ydah <13041216+ydah@users.noreply.github.com> | 2022-05-20 10:39:10 +0900 |
|---|---|---|
| committer | ydah <13041216+ydah@users.noreply.github.com> | 2022-05-20 10:39:10 +0900 |
| commit | 36ad596ef3006f67f2533cd4ac540c20c5e1f1d3 (patch) | |
| tree | fd59d67a4ad721e5ffb0fb09b2dc098f25c19323 | |
| parent | c0672870491e84362f76ddecd50fa229f9b06dff (diff) | |
| download | rust-36ad596ef3006f67f2533cd4ac540c20c5e1f1d3.tar.gz rust-36ad596ef3006f67f2533cd4ac540c20c5e1f1d3.zip | |
Fix typo
This PR is fixes typo "avaiable" to "available".
3 files changed, 4 insertions, 4 deletions
diff --git a/src/doc/rustc/src/platform-support/pc-windows-gnullvm.md b/src/doc/rustc/src/platform-support/pc-windows-gnullvm.md index 96ae065b31b..721c234c6e6 100644 --- a/src/doc/rustc/src/platform-support/pc-windows-gnullvm.md +++ b/src/doc/rustc/src/platform-support/pc-windows-gnullvm.md @@ -4,7 +4,7 @@ Windows targets similar to `*-pc-windows-gnu` but using UCRT as the runtime and various LLVM tools/libraries instead of GCC/Binutils. -Target triples avaiable so far: +Target triples available so far: - `aarch64-pc-windows-gnullvm` - `x86_64-pc-windows-gnullvm` @@ -26,7 +26,7 @@ Like with any other Windows target created binaries are in PE format. ## Building the target For cross-compilation I recommend using [llvm-mingw](https://github.com/mstorsjo/llvm-mingw) toolchain, one change that seems necessary beside configuring corss compilers is disabling experimental `m86k` target. Otherwise LLVM build fails with `multiple definition ...` errors. -Native bootstrapping builds require rather fragile hacks until host artifacts are avaiable so I won't describe them here. +Native bootstrapping builds require rather fragile hacks until host artifacts are available so I won't describe them here. ## Building Rust programs diff --git a/src/tools/rustfmt/tests/source/cfg_if/detect/arch/x86.rs b/src/tools/rustfmt/tests/source/cfg_if/detect/arch/x86.rs index 4c71a2c6ab9..d26f4ee894f 100644 --- a/src/tools/rustfmt/tests/source/cfg_if/detect/arch/x86.rs +++ b/src/tools/rustfmt/tests/source/cfg_if/detect/arch/x86.rs @@ -3,7 +3,7 @@ //! The features are detected using the `detect_features` function below. //! This function uses the CPUID instruction to read the feature flags from the //! CPU and encodes them in a `usize` where each bit position represents -//! whether a feature is available (bit is set) or unavaiable (bit is cleared). +//! whether a feature is available (bit is set) or unavailable (bit is cleared). //! //! The enum `Feature` is used to map bit positions to feature names, and the //! the `__crate::detect::check_for!` macro is used to map string literals (e.g., diff --git a/src/tools/rustfmt/tests/target/cfg_if/detect/arch/x86.rs b/src/tools/rustfmt/tests/target/cfg_if/detect/arch/x86.rs index b985dd8caa1..02d5eed1c29 100644 --- a/src/tools/rustfmt/tests/target/cfg_if/detect/arch/x86.rs +++ b/src/tools/rustfmt/tests/target/cfg_if/detect/arch/x86.rs @@ -3,7 +3,7 @@ //! The features are detected using the `detect_features` function below. //! This function uses the CPUID instruction to read the feature flags from the //! CPU and encodes them in a `usize` where each bit position represents -//! whether a feature is available (bit is set) or unavaiable (bit is cleared). +//! whether a feature is available (bit is set) or unavailable (bit is cleared). //! //! The enum `Feature` is used to map bit positions to feature names, and the //! the `__crate::detect::check_for!` macro is used to map string literals (e.g., |
