---

yaml
---
r: 35675
b: refs/heads/master
c: d098faa
h: refs/heads/master
i:
  35673: e06e163
  35671: 24c4cd0
v: v3

Author: brson

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: 21c9d0858b1ee0c6fe508a9eb1d229713a2649e4
+refs/heads/master: d098faa8555d48a9bc1de34542fc6d1dd5a2ab9c
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: eb8fd119c65c67f3b1b8268cc7341c22d39b7b61
 refs/heads/try: d324a424d8f84b1eb049b12cf34182bda91b0024

trunk/doc/tutorial.md

@@ -2127,15 +2127,15 @@ This usage of traits is similar to Java interfaces.
 
 We can write a trait declaration that _inherits_ from other traits, called _supertraits_.
 Types that implement a trait must also implement its supertraits.
-
-For example, we can define a `Circle` trait that only types that also have the `Shape` trait can have:
+For example,
+we can define a `Circle` trait that inherits from `Shape`.
 
 ~~~~
 trait Shape { fn area(&self) -> float; }
 trait Circle : Shape { fn radius(&self) -> float; }
 ~~~~
 
-Now, implementations of `Circle` methods can call `Shape` methods:
+Now, we can implement `Circle` on a type only if we also implement `Shape`.
 
 ~~~~
 # trait Shape { fn area(&self) -> float; }
@@ -2153,6 +2153,8 @@ impl CircleStruct: Shape {
 }   
 ~~~~
 
+Notice that methods of `Circle` can call methods on `Shape`, as our
+`radius` implementation calls the `area` method.
 This is a silly way to compute the radius of a circle
 (since we could just return the `circle` field), but you get the idea.