Fix some typos

Author: proski

doc/user-guide/src/basics.md

@@ -33,7 +33,7 @@ info: downloading self-update
 If your `rustup` was built with the [no-self-update feature](https://github.com/rust-lang/rustup/blob/master/Cargo.toml#L25), it can not update
 itself. This is not the default, and only versions of `rustup` built with
 `--no-default-features`, or obtained from a third-party distributor who has
-disabled it (such as Nixos).
+disabled it (such as NixOS).
 
 Otherwise Rustup can update itself. It is possible to control Rustup's automatic
 self update mechanism with the `auto-self-update` configuration variable. This
@@ -55,7 +55,7 @@ info: downloading self-update
 
 ### Disabling self updates on a per-invocation basis
 > Self updates can also be suppressed on individual invocations of `rustup` by
-> passing the argurment `--no-self-update`  when running `rustup update` or
+> passing the argument `--no-self-update`  when running `rustup update` or
 > `rustup toolchain install`.
 
 ## Help system

doc/user-guide/src/concepts/proxies.md

@@ -16,7 +16,7 @@ The list of proxies is currently static in `rustup` and is as follows:
 
 - `rust-lldb`, `rust-gdb`, and `rust-gdbgui` are simple wrappers around the `lldb`, `gdb`, and `gdbgui` debuggers respectively. The wrappers enable some pretty-printing of Rust values and add some convenience features to the debuggers by means of their scripting interfaces.
 
-- `rust-analyzer` is part of the Rust IDE integration tooling. It implements the language-server protocol to permit IDEs and editors such as Visual Studio Code, ViM, or Emacs, access to the semantics of the Rust code you are editing. It comes from the `rust-analyzer` component.
+- `rust-analyzer` is part of the Rust IDE integration tooling. It implements the language-server protocol to permit IDEs and editors such as Visual Studio Code, Vim, or Emacs, access to the semantics of the Rust code you are editing. It comes from the `rust-analyzer` component.
 
 - `cargo-clippy` and `clippy-driver` are related to the `clippy` linting tool which provides extra checks for common mistakes and stylistic choices and it comes from the `clippy` component.
 

src/currentprocess/filesource.rs

@@ -205,7 +205,7 @@ pub(super) struct TestWriter(TestWriterInner);
 #[cfg(feature = "test")]
 impl TestWriter {
     pub(super) fn lock(&self) -> TestWriterLock<'_> {
-        // The stream can be locked even if a test thread paniced: its state
+        // The stream can be locked even if a test thread panicked: its state
         // will be ok
         TestWriterLock {
             inner: self.0.lock().unwrap_or_else(|e| e.into_inner()),

src/dist/manifestation/tests.rs

@@ -1484,7 +1484,7 @@ fn add_extensions_does_not_remove_other_components() {
     });
 }
 
-// Asking to remove extensions on initial install is nonsese.
+// Asking to remove extensions on initial install is nonsense.
 #[test]
 #[should_panic]
 fn remove_extensions_for_initial_install() {