---

yaml
---
r: 212671
b: refs/heads/tmp
c: 5efdcf2
h: refs/heads/master
i:
  212669: f52ad5a
  212667: ef409fc
  212663: 50639dd
  212655: 2b9d42d
  212639: dd5e9cc
  212607: f14ae37
v: v3

Author: azerupi

[refs]

@@ -32,7 +32,7 @@ refs/heads/building: 126db549b038c84269a1e4fe46f051b2c15d6970
 refs/heads/beta: 4efc4ec178f6ddf3c8cd268b011f3a04056f9d16
 refs/heads/windistfix: 7608dbad651f02e837ed05eef3d74a6662a6e928
 refs/tags/1.0.0-alpha: e42bd6d93a1d3433c486200587f8f9e12590a4d7
-refs/heads/tmp: 5d8e085369eabb6766b9ec9423716266719b1e34
+refs/heads/tmp: 5efdcf268aed5139b8ec9de52db094edaf866822
 refs/tags/1.0.0-alpha.2: 4c705f6bc559886632d3871b04f58aab093bfa2f
 refs/tags/homu-tmp: bea1c4a78e5233ea6f85a2028a26e08c26635fca
 refs/heads/gate: 97c84447b65164731087ea82685580cc81424412

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

@@ -157,7 +157,7 @@ But, unlike a move, we can still use `v` afterward. This is because an `i32`
 has no pointers to data somewhere else, copying it is a full copy.
 
 All primitive types implement the `Copy` trait and their ownership is
-therefore not moved like one would assume, following the **ownership rules**.
+therefore not moved like one would assume, following the ´ownership rules´.
 To give an example, the two following snippets of code only compile because the 
 `i32` and `bool` types implement the `Copy` trait. 
 
@@ -196,9 +196,6 @@ println!("{}", a);
                ^
 ```
 
-This is quite important to understand, because it is an exception to the most 
-fundamental rule in the Rust language.
-
 We will discuss how to make your own types `Copy` in the [traits][traits]
 section.