From: Ralf Jung <post@ralfj.de>
Date: Tue, 17 May 2016 11:35:25 +0000 (+0200)
Subject: Merge pull request #9 from rwz/patch-1
X-Git-Url: https://git.ralfj.de/rust-101.git/commitdiff_plain/8d47c63ac79f7dee6c96f37902ab98c7d1464ff3?hp=76e70189b58f06dc3beaf8714fb5fdd998b1c8a0

Merge pull request #9 from rwz/patch-1

Fix snipped -> snippet typo
---

diff --git a/src/part04.rs b/src/part04.rs
index dc116ee..31e8056 100644
--- a/src/part04.rs
+++ b/src/part04.rs
@@ -126,7 +126,7 @@ fn mutable_ref_demo() {
 //@ than one mutable reference - we only ever borrow `v` once at a time. However, we can *not* create a shared reference that spans a call to `vec_inc`. Just try
 //@ enabling the commented-out lines, and watch Rust complain. This is because `vec_inc` could mutate
 //@ the vector structurally (i.e., it could add or remove elements), and hence the reference `first`
-//@ could become invalid. In other words, Rust keeps us safe from bugs like the one in the C++ snipped above.
+//@ could become invalid. In other words, Rust keeps us safe from bugs like the one in the C++ snippet above.
 //@ 
 //@ Above, I said that having a mutable reference excludes aliasing. But if you look at the code above carefully,
 //@ you may say: "Wait! Don't the `v` in `mutable_ref_demo` and the `v` in `vec_inc` alias?" And you are right,