diff --git a/Cargo.lock b/Cargo.lock
index 0316036f..19de411a 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -2076,9 +2076,9 @@ dependencies = [
 
 [[package]]
 name = "serde_yaml"
-version = "0.9.28"
+version = "0.9.29"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "9269cfafc7e0257ee4a42f3f68a307f458c63d9e7c8ba4b58c5d15f1b7d7e8d3"
+checksum = "a15e0ef66bf939a7c890a0bf6d5a733c70202225f9888a89ed5c62298b019129"
 dependencies = [
  "indexmap",
  "itoa",
diff --git a/src/slices-and-lifetimes/lifetime-elision.md b/src/slices-and-lifetimes/lifetime-elision.md
index 1eec1005..9a55ee3e 100644
--- a/src/slices-and-lifetimes/lifetime-elision.md
+++ b/src/slices-and-lifetimes/lifetime-elision.md
@@ -69,9 +69,9 @@ by the compiler. Note that this is not the case for raw pointers (unsafe), and
 this is a common source of errors with unsafe Rust.
 
 Students may ask when to use lifetimes. Rust borrows _always_ have lifetimes.
-Most of the time, elision and type inference mean these don't need to be
-written out. In more complicated cases, lifetime annotations can help resolve
-ambiguity. Often, especially when prototyping, it's easier to just work with
-owned data by cloning values where necessary.
+Most of the time, elision and type inference mean these don't need to be written
+out. In more complicated cases, lifetime annotations can help resolve ambiguity.
+Often, especially when prototyping, it's easier to just work with owned data by
+cloning values where necessary.
 
 </details>