Formatter

book/src/03_ticket_v1/00_intro.md

@@ -16,4 +16,3 @@ To move forward you'll have to pick up several new Rust concepts, such as:
 - Memory management: stack, heap, pointers, data layout, destructors
 - Modules and visibility
 - Strings
-

book/src/03_ticket_v1/01_struct.md

@@ -136,4 +136,3 @@ let is_open = Ticket::is_open(ticket);
 
 The function call syntax makes it quite clear that `ticket` is being used as `self`, the first parameter of the method,
 but it's definitely more verbose. Prefer the method call syntax when possible.
-

book/src/03_ticket_v1/03_modules.md

@@ -112,4 +112,3 @@ where each name comes from and potentially introducing name conflicts.\
 Nonetheless, it can be useful in some cases, like when writing unit tests. You might have noticed
 that most of our test modules start with a `use super::*;` statement to bring all the items from the parent module
 (the one being tested) into scope.
-

book/src/03_ticket_v1/04_visibility.md

@@ -43,4 +43,3 @@ pub struct Configuration {
 
 `Configuration` is public, but you can only access the `version` field from within the same crate.
 The `active` field, instead, is private and can only be accessed from within the same module or one of its submodules.
-

book/src/03_ticket_v1/07_setters.md

@@ -106,4 +106,3 @@ ticket.set_title("New title".into());
 ticket.set_description("New description".into());
 ticket.set_status("In Progress".into());
 ```
-

book/src/03_ticket_v1/12_outro.md

@@ -3,4 +3,3 @@
 We've covered a lot of foundational Rust concepts in this chapter.\
 Before moving on, let's go through one last exercise to consolidate what we've learned.
 You'll have minimal guidance this time—just the exercise description and the tests to guide you.
-