From 056611ac1cdf7732a63bb0e42f75bf9d5b4f8158 Mon Sep 17 00:00:00 2001
From: Felix Pherry <71205609+felixpherry@users.noreply.github.com>
Date: Wed, 5 Jun 2024 16:59:04 +0700
Subject: [PATCH] Fix: typos (#84)

Co-authored-by: Felix Pherry <182051.FELIX@klgroup.local>
---
 book/src/05_ticket_v2/09_error_trait.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/book/src/05_ticket_v2/09_error_trait.md b/book/src/05_ticket_v2/09_error_trait.md
index 9eca502..afe7e72 100644
--- a/book/src/05_ticket_v2/09_error_trait.md
+++ b/book/src/05_ticket_v2/09_error_trait.md
@@ -7,7 +7,7 @@ pass it to the `panic!` macro.\
 This is a (rudimentary) example of **error reporting**: transforming an error type into a representation that can be
 shown to a user, a service operator, or a developer.
 
-It's not practical for each Rust developer to come up with their own error reporting strategy: it'd a waste of time
+It's not practical for each Rust developer to come up with their own error reporting strategy: it'd be a waste of time
 and it wouldn't compose well across projects.
 That's why Rust provides the `std::error::Error` trait.