---

yaml
---
r: 187566
b: refs/heads/tmp
c: 9f2b067
h: refs/heads/master
v: v3

Author: jxcl

[refs]

@@ -34,5 +34,5 @@ refs/heads/building: 126db549b038c84269a1e4fe46f051b2c15d6970
 refs/heads/beta: 522d09dfecbeca1595f25ac58c6d0178bbd21d7d
 refs/heads/windistfix: 7608dbad651f02e837ed05eef3d74a6662a6e928
 refs/tags/1.0.0-alpha: e42bd6d93a1d3433c486200587f8f9e12590a4d7
-refs/heads/tmp: 72eaf2c30e846b3d14c520c0c7638b2b16bf8c73
+refs/heads/tmp: 9f2b0671f88b2cc6bb73575db47d265dbb246e34
 refs/tags/1.0.0-alpha.2: 4c705f6bc559886632d3871b04f58aab093bfa2f

branches/tmp/src/doc/trpl/iterators.md

@@ -91,11 +91,11 @@ for num in &nums {
 ```
 
 Now we're explicitly dereferencing `num`. Why does `&nums` give us
-references?  Because we asked it to with `&`. If we had not had the
-`&`, `nums` would have been moved into the `for` loop and consumed,
-and we we would no longer be able to access `nums` afterward.  With
-references, we're just borrowing a reference to the data, and so it's
-just passing a reference, without needing to do the move.
+references?  Firstly, because we explicitly asked it to with
+`&`. Secondly, if it gave us the data itself, we would have to be its
+owner, which would involve making a copy of the data and giving us the
+copy. With references, we're just borrowing a reference to the data,
+and so it's just passing a reference, without needing to do the move.
 
 So, now that we've established that ranges are often not what you want, let's
 talk about what you do want instead.
@@ -242,9 +242,6 @@ for num in nums.iter() {
 }
 ```
 
-Sometimes you need this functionality, but since for loops operate on the
-`IntoIterator` trait, calling `.iter()` is rarely necessary.
-
 These two basic iterators should serve you well. There are some more
 advanced iterators, including ones that are infinite. Like `count`: