---

yaml
---
r: 34396
b: refs/heads/snap-stage3
c: 62c7ca6
h: refs/heads/master
v: v3

Author: brson

[refs]

@@ -1,7 +1,7 @@
 ---
 refs/heads/master: cd6f24f9d14ac90d167386a56e7a6ac1f0318195
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
-refs/heads/snap-stage3: 89acd1f57f6c0df96a2ebf652561eb786f28664d
+refs/heads/snap-stage3: 62c7ca64f0aa7947250b5cd95b63f47cea60f525
 refs/heads/try: d324a424d8f84b1eb049b12cf34182bda91b0024
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b

branches/snap-stage3/doc/tutorial.md

@@ -228,7 +228,7 @@ let monster_size: int = 50;
 Local variables may shadow earlier declarations, as in the previous example:
 `monster_size` was first declared as a `float`, and then a second
 `monster_size` was declared as an `int`. If you were to actually compile this
-example, though, the compiler would determine that the second `monster_size` is
+example, though, the compiler would determine that the first `monster_size` is
 unused and issue a warning (because this situation is likely to indicate a
 programmer error). For occasions where unused variables are intentional, their
 names may be prefixed with an underscore to silence the warning, like `let