---

Michael Tiller · Michael Tiller · commit a945a09fa569 · 2016-04-19T12:38:39.000-04:00
yaml --- r: 275983 b: refs/heads/master c: 864eba8 h: refs/heads/master i: 275981: 697cd93 275979: 3090f49 275975: ef424d3 275967: 88cb670
diff --git a/[refs] b/[refs]
@@ -1,5 +1,5 @@
 ---
-refs/heads/master: f252cfa2d4709c44bf7e9dd02e522e8e372482bc
+refs/heads/master: 864eba884d860d7d0bfceb89af1a4bc690f21ea0
 refs/heads/snap-stage3: 235d77457d80b549dad3ac36d94f235208a1eafb
 refs/heads/try: 49312a405e14a449b98fe0056b12a40ac128be4a
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
diff --git a/trunk/src/doc/book/references-and-borrowing.md b/trunk/src/doc/book/references-and-borrowing.md
@@ -1,7 +1,7 @@
 % References and Borrowing
 
-This guide is two of three presenting Rust’s ownership system. This is one of
-Rust’s most unique and compelling features, with which Rust developers should
+This is the second of three sections presenting Rust’s ownership system. This is one of
+Rust’s most distinct and compelling features, with which Rust developers should
 become quite acquainted. Ownership is how Rust achieves its largest goal,
 memory safety. There are a few distinct concepts, each with its own
 chapter:
