---

yaml
---
r: 107583
b: refs/heads/dist-snap
c: fce7922
h: refs/heads/master
i:
  107581: 8281bad
  107579: b3887a6
  107575: 2a33ce8
  107567: 9c5af2e
  107551: dfe2b5f
  107519: 2d9a72c
v: v3

Author: bstrie

[refs]

@@ -6,7 +6,7 @@ refs/heads/try: f64fdf524a434f0e5cd0bc91d09c144723f3c90d
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: 147ecfdd8221e4a4d4e090486829a06da1e0ca3c
-refs/heads/dist-snap: aedf567a950a22acd183da6b1dd7a7fef92e8351
+refs/heads/dist-snap: fce792249e72a181f2ad52413b25b1db643c371f
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503
 refs/heads/try3: 9387340aab40a73e8424c48fd42f0c521a4875c0

branches/dist-snap/doc/tutorial.md

@@ -3071,7 +3071,8 @@ The effect it has on your module hierarchy mirrors aspects of both `mod` and `us
   The linkage information the binary needs to use the library `foo`.
 
 - But like `use`, all `extern mod` statements that refer to the same library are interchangeable,
-  as each one really just presents an alias to an external module (the crate root of the library your linking against).
+  as each one really just presents an alias to an external module (the crate root of the library
+  you're linking against).
 
 Remember how `use`-statements have to go before local declarations because the latter shadows the former?
 Well, `extern mod` statements also have their own rules in that regard: