From 7202cfeecd13ad6bbecd537d9799244313600db5 Mon Sep 17 00:00:00 2001 From: Dirk Stolle Date: Wed, 24 Jul 2024 01:54:14 +0200 Subject: [PATCH] chore: fix a few typos (#780) --- tower/src/builder/mod.rs | 2 +- tower/src/load/mod.rs | 2 +- tower/src/ready_cache/cache.rs | 2 +- tower/src/util/call_all/common.rs | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/tower/src/builder/mod.rs b/tower/src/builder/mod.rs index a990dbfd0..8f081d234 100644 --- a/tower/src/builder/mod.rs +++ b/tower/src/builder/mod.rs @@ -325,7 +325,7 @@ impl ServiceBuilder { /// // ...but we want to call that service with a `usize`. What do we do? /// /// let usize_svc = ServiceBuilder::new() - /// // Add a middlware that converts the request type to a `String`: + /// // Add a middleware that converts the request type to a `String`: /// .map_request(|request: usize| format!("{}", request)) /// // ...and wrap the string service with that middleware: /// .service(string_svc); diff --git a/tower/src/load/mod.rs b/tower/src/load/mod.rs index 2f9a37371..e47558b48 100644 --- a/tower/src/load/mod.rs +++ b/tower/src/load/mod.rs @@ -26,7 +26,7 @@ //! [`TrackCompletion`] trait, with [`CompleteOnResponse`] as the default type. The behavior of //! [`CompleteOnResponse`] is what you would normally expect for a request-response cycle: when the //! response is produced, the request is considered "finished", and load goes down. This can be -//! overriden by your own user-defined type to track more complex request completion semantics. See +//! overridden by your own user-defined type to track more complex request completion semantics. See //! the documentation for [`completion`] for more details. //! //! # Examples diff --git a/tower/src/ready_cache/cache.rs b/tower/src/ready_cache/cache.rs index b3aec3781..a62990339 100644 --- a/tower/src/ready_cache/cache.rs +++ b/tower/src/ready_cache/cache.rs @@ -42,7 +42,7 @@ use tracing::{debug, trace}; /// the _pending_ set to be driven to readiness again. /// /// When `ReadyCache::check_ready*` returns `false`, it indicates that the -/// specified service is _not_ ready. If an error is returned, this indicats that +/// specified service is _not_ ready. If an error is returned, this indicates that /// the server failed and has been removed from the cache entirely. /// /// [`ReadyCache::evict`] can be used to remove a service from the cache (by key), diff --git a/tower/src/util/call_all/common.rs b/tower/src/util/call_all/common.rs index 3b3f8938c..9f2490b6d 100644 --- a/tower/src/util/call_all/common.rs +++ b/tower/src/util/call_all/common.rs @@ -126,7 +126,7 @@ where let svc = this .service .as_mut() - .expect("Using CallAll after extracing inner Service"); + .expect("Using CallAll after extracting inner Service"); if let Err(e) = ready!(svc.poll_ready(cx)) { // Set eof to prevent the service from being called again after a `poll_ready` error