From 6a638568d53608c31071362b6781acf226bab5c8 Mon Sep 17 00:00:00 2001 From: taine Date: Tue, 9 Jun 2026 11:21:55 +0200 Subject: [PATCH] Fixed ToC chapter titles --- book/src/06_ticket_management/00_intro.md | 2 +- book/src/07_threads/00_intro.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/book/src/06_ticket_management/00_intro.md b/book/src/06_ticket_management/00_intro.md index 7af5556..eca75c9 100644 --- a/book/src/06_ticket_management/00_intro.md +++ b/book/src/06_ticket_management/00_intro.md @@ -1,4 +1,4 @@ -# Intro +# Ticket Management 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. diff --git a/book/src/07_threads/00_intro.md b/book/src/07_threads/00_intro.md index f3c4b1e..d526a74 100644 --- a/book/src/07_threads/00_intro.md +++ b/book/src/07_threads/00_intro.md @@ -1,4 +1,4 @@ -# Intro +# Threads One of Rust's big promises is _fearless concurrency_: making it easier to write safe, concurrent programs. We haven't seen much of that yet. All the work we've done so far has been single-threaded.