Skip to content

Commit

Permalink
fixed backquotes and awkward borrowing clause
Browse files Browse the repository at this point in the history
  • Loading branch information
jonmarkprice committed Jun 27, 2016
1 parent 126af08 commit cae02ff
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions src/doc/book/ownership.md
Expand Up @@ -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.

Expand Down Expand Up @@ -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!

0 comments on commit cae02ff

Please sign in to comment.