---

yaml
---
r: 39673
b: refs/heads/incoming
c: 62c7ca6
h: refs/heads/master
i:
  39671: 2f5cb18
v: v3

Author: brson

[refs]

@@ -6,7 +6,7 @@ refs/heads/try: 3d5418789064fdb463e872a4e651af1c628a3650
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: a810c03263670238bccd64cabb12a23a46e3a278
-refs/heads/incoming: 89acd1f57f6c0df96a2ebf652561eb786f28664d
+refs/heads/incoming: 62c7ca64f0aa7947250b5cd95b63f47cea60f525
 refs/heads/dist-snap: 22efa39382d41b084fde1719df7ae8ce5697d8c9
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/incoming/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