fix: fix typo in several places

Author: rami3l

src/dist/mod.rs

@@ -91,7 +91,7 @@ fn components_missing_msg(cs: &[Component], manifest: &ManifestV2, toolchain: &s
                 .join(", ");
             let _ = write!(
                 buf,
-                "some components unavailable for download for channel '{toolchain}': {cs_str}"
+                "some components are unavailable for download for channel '{toolchain}': {cs_str}"
             );
 
             if toolchain.starts_with("nightly") {

src/errors.rs

@@ -141,7 +141,7 @@ fn suggest_message(suggestion: &Option<String>) -> String {
 
 /// Returns a error message indicating that certain [`Component`]s are unavailable.
 ///
-/// See also [`component_missing_msg`](../dist/dist/fn.components_missing_msg.html)
+/// See also [`components_missing_msg`](../dist/dist/fn.components_missing_msg.html)
 /// which generates error messages for component unavailability toolchain-wide operations.
 ///
 /// # Panics
@@ -185,7 +185,7 @@ fn component_unavailable_msg(cs: &[Component], manifest: &Manifest, toolchain: &
 
             let _ = write!(
                 buf,
-                "some components unavailable for download for channel '{toolchain}': {cs_str}"
+                "some components are unavailable for download for channel '{toolchain}': {cs_str}"
             );
 
             if toolchain.starts_with("nightly") {

src/test/mock/clitools.rs

@@ -94,7 +94,7 @@ pub enum Scenario {
     Unavailable,
     /// Two dates, v2 manifests, RLS unavailable in first date, restored on second.
     UnavailableRls,
-    /// Three dates, v2 manifests, RLS available in first and last, not middle
+    /// Three dates, v2 manifests, RLS available in first and second, not last
     MissingComponent,
     /// Three dates, v2 manifests, RLS available in first, middle missing nightly
     MissingNightly,