From 5efdcf268aed5139b8ec9de52db094edaf866822 Mon Sep 17 00:00:00 2001 From: Mathieu David Date: Mon, 8 Jun 2015 18:01:40 +0200 Subject: [PATCH] Updated with requested changes --- src/doc/trpl/ownership.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/doc/trpl/ownership.md b/src/doc/trpl/ownership.md index e94fe0334074..46af311acf31 100644 --- a/src/doc/trpl/ownership.md +++ b/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.