---

yaml
---
r: 212348
b: refs/heads/master
c: 5efdcf2
h: refs/heads/master
v: v3

Author: azerupi

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: 5d8e085369eabb6766b9ec9423716266719b1e34
+refs/heads/master: 5efdcf268aed5139b8ec9de52db094edaf866822
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: ba0e1cd8147d452c356aacb29fb87568ca26f111
 refs/heads/try: 1864973ae17213c5a58c4dd3f9af6d1b6c7d2e05

trunk/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.