From 3c19ca0150a4b01412c79b80b04facbbc14351ee Mon Sep 17 00:00:00 2001
From: LukeMathWalker <20745048+LukeMathWalker@users.noreply.github.com>
Date: Tue, 8 Jul 2025 10:33:03 +0200
Subject: [PATCH] Formatting

---
 src/idiomatic/leveraging-the-type-system.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/idiomatic/leveraging-the-type-system.md b/src/idiomatic/leveraging-the-type-system.md
index 0f7adc6a..d7a871b4 100644
--- a/src/idiomatic/leveraging-the-type-system.md
+++ b/src/idiomatic/leveraging-the-type-system.md
@@ -35,8 +35,8 @@ Additional items speaker may mention:
   types in Rust.
 
   Evaluate, on a case-by-case basis, whether a more imperative approach may be
-  easier to implement. Consider using in-place mutation, relying on Rust's borrow-checker and type system to
-  control what can be mutated, and where.
+  easier to implement. Consider using in-place mutation, relying on Rust's
+  borrow-checker and type system to control what can be mutated, and where.
 
 - The same caution should be applied to object-oriented design patterns. Rust
   doesn't support inheritance, and object decomposition should take into account