From cae02fff6a36b19d65c4bb2ff993e373dad16032 Mon Sep 17 00:00:00 2001 From: Jonathan Price Date: Mon, 27 Jun 2016 16:34:35 -0500 Subject: [PATCH] fixed backquotes and awkward borrowing clause --- src/doc/book/ownership.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/doc/book/ownership.md b/src/doc/book/ownership.md index f445bed015c0..73775956b6cc 100644 --- a/src/doc/book/ownership.md +++ b/src/doc/book/ownership.md @@ -212,7 +212,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. @@ -288,6 +288,6 @@ let (v1, v2, answer) = foo(v1, v2); Ugh! The return type, return line, and calling the function gets way more complicated. -Luckily, Rust offers a feature, borrowing, which helps us solve this problem. -It’s the topic of the next section! +Luckily, Rust offers a feature which helps us solve this problem. +It’s called borrowing and is the topic of the next section!