---

yaml
---
r: 229010
b: refs/heads/try
c: bdc62e0
h: refs/heads/master
v: v3

Author: Gankra

[refs]

@@ -1,7 +1,7 @@
 ---
 refs/heads/master: aca2057ed5fb7af3f8905b2bc01f72fa001c35c8
 refs/heads/snap-stage3: 1af31d4974e33027a68126fa5a5a3c2c6491824f
-refs/heads/try: d66c67be784a4d0678f60158adb9e76c6b58d9c3
+refs/heads/try: bdc62e009cc5b62fcf356e7977c6397296b2077d
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/try/references.md

@@ -138,7 +138,7 @@ This has no semantic consequences, but is probably a more useful notion when
 verifying the soundness of a construct.)
 
 That's it. Super simple right? Except for the fact that it took us two pages
-to define all of the terms in that defintion. You know: Super. Simple.
+to define all of the terms in that definition. You know: Super. Simple.
 
 Actually it's a bit more complicated than that. In addition to references,
 Rust has *raw pointers*: `*const T` and `*mut T`. Raw pointers have no inherent

branches/try/working-with-unsafe.md

@@ -44,7 +44,7 @@ Trickier than that is when we get into actual statefulness. Consider a simple
 implementation of `Vec`:
 
 ```rust
-// Note this defintion is insufficient. See the section on lifetimes.
+// Note this definition is insufficient. See the section on lifetimes.
 pub struct Vec<T> {
     ptr: *mut T,
     len: usize,