tokio-rs/axum
1
0
Fork 0
mirror of https://github.com/tokio-rs/axum.git synced 2026-09-06 00:00:17 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix some typos in the docs

Browse Source
This commit is contained in:
David Pedersen
2023-07-03 09:23:37 +02:00
parent f4accdc95d
commit cc9629fe88
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
axum/src/docs/error_handling.md
+1 -1
View File
@@ -39,7 +39,7 @@ It doesn't matter whether you return `Err(StatusCode::NOT_FOUND)` or
axum. axum.
Instead of a direct `StatusCode`, it makes sense to use intermediate error type Instead of a direct `StatusCode`, it makes sense to use intermediate error type
that can ultimately be converted to `Reponse`. This allows using `?` operator that can ultimately be converted to `Response`. This allows using `?` operator
in handlers. See those examples: in handlers. See those examples:
* [`anyhow-error-response`][anyhow] for generic boxed errors * [`anyhow-error-response`][anyhow] for generic boxed errors
axum/src/handler/mod.rs
+1 -1
View File
@@ -33,7 +33,7 @@
//! ``` //! ```
//! //!
//! Instead of a direct `StatusCode`, it makes sense to use intermediate error type //! Instead of a direct `StatusCode`, it makes sense to use intermediate error type
//! that can ultimately be converted to `Reponse`. This allows using `?` operator //! that can ultimately be converted to `Response`. This allows using `?` operator
//! in handlers. See those examples: //! in handlers. See those examples:
//! //!
//! * [`anyhow-error-response`][anyhow] for generic boxed errors //! * [`anyhow-error-response`][anyhow] for generic boxed errors