Fix typos found by typos-cli (#113)

examples/sse.rs

@@ -24,7 +24,7 @@ async fn main() {
                 .handle_error(|error: std::io::Error| {
                     Ok::<_, std::convert::Infallible>((
                         StatusCode::INTERNAL_SERVER_ERROR,
-                        format!("Unhandled interal error: {}", error),
+                        format!("Unhandled internal error: {}", error),
                     ))
                 }),
         ),

examples/static_file_server.rs

@@ -18,7 +18,7 @@ async fn main() {
         axum::service::get(ServeDir::new(".").handle_error(|error: std::io::Error| {
             Ok::<_, std::convert::Infallible>((
                 StatusCode::INTERNAL_SERVER_ERROR,
-                format!("Unhandled interal error: {}", error),
+                format!("Unhandled internal error: {}", error),
             ))
         })),
     )

examples/websocket.rs

@@ -33,7 +33,7 @@ async fn main() {
                 .handle_error(|error: std::io::Error| {
                     Ok::<_, std::convert::Infallible>((
                         StatusCode::INTERNAL_SERVER_ERROR,
-                        format!("Unhandled interal error: {}", error),
+                        format!("Unhandled internal error: {}", error),
                     ))
                 }),
         ),

src/extract/extension.rs

@@ -32,7 +32,7 @@ use std::ops::Deref;
 /// # };
 /// ```
 ///
-/// If the extension is missing it will reject the request with a `500 Interal
+/// If the extension is missing it will reject the request with a `500 Internal
 /// Server Error` response.
 #[derive(Debug, Clone, Copy)]
 pub struct Extension<T>(pub T);

src/handler/mod.rs

@@ -204,7 +204,7 @@ pub trait Handler<B, In>: Sized {
     /// This can be used to add additional processing to a request for a single
     /// handler.
     ///
-    /// Note this differes from [`routing::Layered`](crate::routing::Layered)
+    /// Note this differs from [`routing::Layered`](crate::routing::Layered)
     /// which adds a middleware to a group of routes.
     ///
     /// # Example

src/lib.rs

@@ -450,7 +450,7 @@
 //! However when applying middleware, or embedding other tower services, errors
 //! might happen. For example [`Timeout`] will return an error if the timeout
 //! elapses. By default these errors will be propagated all the way up to hyper
-//! where the connection will be closed. If that isn't desireable you can call
+//! where the connection will be closed. If that isn't desirable you can call
 //! [`handle_error`](handler::Layered::handle_error) to handle errors from
 //! adding a middleware to a handler:
 //!
@@ -497,7 +497,7 @@
 //! return `Result<T, E>` where `T` implements
 //! [`IntoResponse`](response::IntoResponse).
 //!
-//! See [`routing::Layered::handle_error`] fo more details.
+//! See [`routing::Layered::handle_error`] for more details.
 //!
 //! ## Applying multiple middleware
 //!
@@ -646,7 +646,7 @@
 //! # Examples
 //!
 //! The axum repo contains [a number of examples][examples] that show how to put all the
-//! pieces togehter.
+//! pieces together.
 //!
 //! # Feature flags
 //!
@@ -656,7 +656,7 @@
 //! The following optional features are available:
 //!
 //! - `ws`: Enables WebSockets support.
-//! - `headers`: Enables extracing typed headers via [`extract::TypedHeader`].
+//! - `headers`: Enables extracting typed headers via [`extract::TypedHeader`].
 //! - `multipart`: Enables parsing `multipart/form-data` requests with [`extract::Multipart`].
 //!
 //! [`tower`]: https://crates.io/crates/tower

src/routing.rs

@@ -182,7 +182,7 @@ pub trait RoutingDsl: crate::sealed::Sealed + Sized {
     /// This can be used to add additional processing to a request for a group
     /// of routes.
     ///
-    /// Note this differes from [`handler::Layered`](crate::handler::Layered)
+    /// Note this differs from [`handler::Layered`](crate::handler::Layered)
     /// which adds a middleware to a single handler.
     ///
     /// # Example