Merge pull request #3499 from rustaceanclub/master

Fix some typos

Author: djc

ci/run.bash

@@ -58,7 +58,7 @@ download_pkg_test() {
 
 # Machines have 7GB of RAM, and our target/ contents is large enough that
 # thrashing will occur if we build-run-build-run rather than
-# build-build-build-run-run-run. Since this is used soley for non-release
+# build-build-build-run-run-run. Since this is used solely for non-release
 # artifacts, we try to keep features consistent across the builds, whether for
 # docs/test/runs etc.
 build_test() {

doc/dev-guide/src/tracing.md

@@ -74,8 +74,8 @@ Some good general heuristics:
 
 ## Caveats
 
-Cross-thread propogation isn't connected yet. This will cause instrumentation in
+Cross-thread propagation isn't connected yet. This will cause instrumentation in
 a thread to make a new root span until it is fixed. If any Tokio runtime-related
 code gets added in those threads this will also cause a panic. We have a couple
 of threadpools in use today; if you need to instrument within that context, use
-a thunk to propogate the tokio runtime into those threads.
+a thunk to propagate the tokio runtime into those threads.

src/cli/common.rs

@@ -490,7 +490,7 @@ fn print_toolchain_path(
 }
 
 pub(crate) fn list_toolchains(cfg: &Cfg, verbose: bool) -> Result<utils::ExitCode> {
-    // Work with LocalToolchainName to accomdate path based overrides
+    // Work with LocalToolchainName to accommodate path based overrides
     let toolchains = cfg
         .list_toolchains()?
         .iter()