---

yaml
---
r: 22096
b: refs/heads/snap-stage3
c: 3232e75
h: refs/heads/master
v: v3

Author: brson

[refs]

@@ -1,7 +1,7 @@
 ---
 refs/heads/master: e430a699f2c60890d9b86069fd0c68a70ece7120
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
-refs/heads/snap-stage3: 8f0e9ff02914459a98d1727f5bf0c26bba604bb9
+refs/heads/snap-stage3: 3232e7599566e896c9bfee4e4eba71e6963e3ce8
 refs/heads/try: ffbe0e0e00374358b789b0037bcb3a577cd218be
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b

branches/snap-stage3/doc/tutorial.md

@@ -995,15 +995,6 @@ _owned boxes_. All tasks may allocate objects on the exchange heap,
 then transfer ownership of those objects to other tasks, avoiding
 expensive copies.
 
-## What to be aware of
-
-Rust has three "realms" in which objects can be allocated: the stack,
-the local heap, and the exchange heap. These realms have corresponding
-pointer types: the borrowed pointer (`&T`), the managed box (`@T`),
-and the owned box (`~T`). These three sigils will appear
-repeatedly as we explore the language. Learning the appropriate role
-of each is key to using Rust effectively.
-
 # Boxes and pointers
 
 In contrast to a lot of modern languages, aggregate types like structs