From 615c63504df464d454d6335e40bba8beb9c7a03c Mon Sep 17 00:00:00 2001 From: Donghyun Kim Date: Fri, 25 Oct 2024 23:50:08 +0900 Subject: [PATCH] Fix a sentence --- documentation/docs/error-handling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/docs/error-handling.md b/documentation/docs/error-handling.md index a47e16a3..0743ce52 100644 --- a/documentation/docs/error-handling.md +++ b/documentation/docs/error-handling.md @@ -16,7 +16,7 @@ We recommend that you _not_ write panicking code at all, since Rust has the idio To manage Rust errors effectively, using a flexible error type is beneficial. -Developing an app differs from creating a library, as an app may encounter a wide range of error situations. Declaring a distinct error type for hundreds of potential errors can be overwhelming. Therefore, it is advisable to utilize a single, flexible error type. +Developing an app differs from creating a library, as an app may encounter a wide range of error situations. Declaring distinct error types for hundreds of potential errors can be overwhelming. Therefore, it is advisable to utilize a single, flexible error type. You can define your own custom error type or simply use one from `crates.io`: