Use "typos-cli" to fix a bunch of typos.

CHANGELOG.md

@@ -779,7 +779,7 @@ a library (unless they want to).  We have an early version of this
 protocol implemented, but it does not yet expose any useful
 functionality.
 
-Arti 1.1.4 also increases our MSRV (Minumum Supported Rust Version)
+Arti 1.1.4 also increases our MSRV (Minimum Supported Rust Version)
 to Rust 1.65, in accordance with our [MSRV Policy], and renames a
 few other inconsistently-named APIs.
 
@@ -1261,7 +1261,7 @@ our process below.
 
 - When logging an error at severity `info` or higher, we now (sometimes)
   include a full report of the error's sources. Previously we only
-  logged the higest-level error, which often lacked enough detail to
+  logged the highest-level error, which often lacked enough detail to
   make a full diagnosis. This work will be completed in a subsequent
   release.([!936])
 - When asked via SOCKS to resolve an address that is already an IP

crates/arti-client/src/config.rs

@@ -415,7 +415,7 @@ fn validate_pt_config(bridges: &BridgesConfigBuilder) -> Result<(), ConfigBuildE
 
     Err(ConfigBuildError::Inconsistent {
         fields: ["bridges.bridges", "bridges.transports"].map(Into::into).into_iter().collect(),
-        problem: "Bridges configured, but all bridges unuseable due to lack of corresponding pluggable transport in `[bridges.transports]`".into(),
+        problem: "Bridges configured, but all bridges unusable due to lack of corresponding pluggable transport in `[bridges.transports]`".into(),
     })
 }
 

crates/tor-hsservice/src/svc.rs

@@ -113,7 +113,7 @@ struct DescUploadHistory {
     //
     // Note that is possible that multiple descriptors will need to be uploaded
     // to the same HsDir.  When this happens, we MUST use separate circuits to
-    // uplaod them.
+    // upload them.
     target_status: HashMap<HsBlindIdKey, HashMap<RelayIds, RetryState>>,
 }
 

crates/tor-hsservice/src/svc/publish.rs

@@ -10,7 +10,7 @@ use tor_rtcompat::Runtime;
 /// A handle for the Hsdir Publisher for an onion service.
 ///
 /// This handle represents a set of tasks that identify the hsdirs for each
-/// releavant time period, construct descriptors, publish them, and keep them
+/// relevant time period, construct descriptors, publish them, and keep them
 /// up-to-date.
 pub(crate) struct Publisher {
     // TODO HSS: Write the contents here.

crates/tor-proto/src/circuit.rs

@@ -1121,7 +1121,7 @@ impl StreamTarget {
     /// accordingly.
     ///
     /// Normally, you shouldn't need to call this function, as streams are implicitly closed by the
-    /// reactor when their corresponding `StreamTarget` is droppped. The only valid use of this
+    /// reactor when their corresponding `StreamTarget` is dropped. The only valid use of this
     /// function is for closing pending incoming streams (a stream is said to be pending if we have
     /// received the message initiating the stream but have not responded to it yet).
     ///

doc/dev/hs-overview.md

@@ -155,7 +155,7 @@ logic as the service.
     between them. 
 
 Now, at last, the client has received the service's handshake over the expected
-circuit. The client complets the handshake, to get a set of shared encryption
+circuit. The client completes the handshake, to get a set of shared encryption
 keys with the service.  Now the client and service have a pair of joined
 circuits, and a set of encryption material to use to communicate.
 

doc/dev/notes/key-management.md

@@ -52,7 +52,7 @@ In the future we plan to also support HSM-based key stores.
 ### Hidden service with on-disk keys
 
 The user makes a minimal configuration:
-they specify the nickname of the hidden serivce in the Arti configuration,
+they specify the nickname of the hidden service in the Arti configuration,
 and where to forward http(s) requests.
 
 The default Arti keystore is instantiated, and is initially empty.
@@ -153,7 +153,7 @@ the private one (which exists only on the offline host),
 and the shared one (which exists on both).
 The private keystore contains `K_hs_id`
 (and the key is generated there if there isn't one already).
-The shared keystore contains the subsidary keys.
+The shared keystore contains the subsidiary keys.
 
 The offline tool generates a specified number of
 `K_hs_desc_sign` for future time periods,