---

yaml
---
r: 33181
b: refs/heads/snap-stage3
c: 6da09c3
h: refs/heads/master
i:
  33179: 2e47259
v: v3

Author: pcwalton

[refs]

@@ -1,7 +1,7 @@
 ---
 refs/heads/master: cd6f24f9d14ac90d167386a56e7a6ac1f0318195
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
-refs/heads/snap-stage3: f016fd43f868cffa8759f18c4772a1423e48ccd1
+refs/heads/snap-stage3: 6da09c3b437dad240218b91ea06c301982764152
 refs/heads/try: d324a424d8f84b1eb049b12cf34182bda91b0024
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b

branches/snap-stage3/doc/tutorial.md

@@ -1054,7 +1054,7 @@ copied, not just a pointer.
 For small structs like `Point`, this is usually more efficient than
 allocating memory and going through a pointer. But for big structs, or
 those with mutable fields, it can be useful to have a single copy on
-the heap, and refer to that through a pointer.
+the stack or on the heap, and refer to that through a pointer.
 
 Rust supports several types of pointers. The safe pointer types are
 `@T` for managed boxes allocated on the local heap, `~T`, for
@@ -1087,8 +1087,7 @@ let y = x; // Copy of a pointer to the same box
 ~~~~
 
 Any type that contains managed boxes or other managed types is
-considered _managed_. Managed types are the only types that can
-construct cyclic data structures in Rust, such as doubly-linked lists.
+considered _managed_.
 
 ~~~
 // A linked list node