---

yaml
---
r: 14763
b: refs/heads/try
c: 57af1e9
h: refs/heads/master
i:
  14761: 86743e9
  14759: 193e97c
v: v3

Author: brson

[refs]

@@ -2,5 +2,5 @@
 refs/heads/master: 61b1875c16de39c166b0f4d54bba19f9c6777d1a
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: 4a81779abd786ff22d71434c6d9a5917ea4cdfff
-refs/heads/try: 91b988ea45c68e2cf9d20163fb496160855aa5d8
+refs/heads/try: 57af1e9f67082e41e62aa977754f2df5f78e403c
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105

branches/try/doc/tutorial.md

@@ -2385,8 +2385,7 @@ The argument to `task::spawn()` is a [unique
 closure](#unique-closures) of type `fn~()`, meaning that it takes no
 arguments and generates no return value. The effect of `task::spawn()`
 is to fire up a child task that will execute the closure in parallel
-with the creator. The result is a task id, here stored into the
-variable `child_task`.
+with the creator.
 
 ## Ports and channels
 
@@ -2402,10 +2401,10 @@ in parallel.  We might write something like:
 # fn some_other_expensive_computation() {}
 let port = comm::port::<int>();
 let chan = comm::chan::<int>(port);
-let child_task = task::spawn {||
+task::spawn {||
     let result = some_expensive_computation();
     comm::send(chan, result);
-};
+}
 some_other_expensive_computation();
 let result = comm::recv(port);
 ~~~~
@@ -2433,10 +2432,10 @@ The next statement actually spawns the child:
 # fn some_expensive_computation() -> int { 42 }
 # let port = comm::port::<int>();
 # let chan = comm::chan::<int>(port);
-let child_task = task::spawn {||
+task::spawn {||
     let result = some_expensive_computation();
     comm::send(chan, result);
-};
+}
 ~~~~
 
 This child will perform the expensive computation send the result