From 6d707bb32d5d702b7081e3f2b8d9b80b75c10904 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?On=C3=A8?= <43485962+c-git@users.noreply.github.com>
Date: Fri, 24 May 2024 06:58:07 -0400
Subject: [PATCH] add system to sentence (#48)

---
 book/src/06_ticket_management/00_intro.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/book/src/06_ticket_management/00_intro.md b/book/src/06_ticket_management/00_intro.md
index 164419576..054a90779 100644
--- a/book/src/06_ticket_management/00_intro.md
+++ b/book/src/06_ticket_management/00_intro.md
@@ -2,7 +2,7 @@
 
 In the previous chapter we modelled `Ticket` in a vacuum: we defined its fields and their constraints, we learned
 how to best represent them in Rust, but we didn't consider how `Ticket` fits into a larger system.
-We'll use this chapter to build a simple workflow around `Ticket`, introducing a (rudimentary) management to
+We'll use this chapter to build a simple workflow around `Ticket`, introducing a (rudimentary) management system to
 store and retrieve tickets.
 
 The task will give us an opportunity to explore new Rust concepts, such as: