Skip to content

Commit cae02ff

Browse files
authored
fixed backquotes and awkward borrowing clause
1 parent 126af08 commit cae02ff

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/doc/book/ownership.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -212,7 +212,7 @@ But, unlike a move, we can still use `v` afterward. This is because an `i32`
212212
has no pointers to data somewhere else, copying it is a full copy.
213213

214214
All primitive types implement the `Copy` trait and their ownership is
215-
therefore not moved like one would assume, following the ´ownership rules´.
215+
therefore not moved like one would assume, following the 'ownership rules'.
216216
To give an example, the two following snippets of code only compile because the
217217
`i32` and `bool` types implement the `Copy` trait.
218218

@@ -288,6 +288,6 @@ let (v1, v2, answer) = foo(v1, v2);
288288
Ugh! The return type, return line, and calling the function gets way more
289289
complicated.
290290

291-
Luckily, Rust offers a feature, borrowing, which helps us solve this problem.
292-
It’s the topic of the next section!
291+
Luckily, Rust offers a feature which helps us solve this problem.
292+
It’s called borrowing and is the topic of the next section!
293293

0 commit comments

Comments
 (0)