X-Git-Url: https://git.ralfj.de/rust-101.git/blobdiff_plain/27a99e3d92e3ce48ed4aeee9527c4adc6d4b68f7..0c5e5d86510258f57cf2c1f23479b675e14c50d3:/src/part04.rs

diff --git a/src/part04.rs b/src/part04.rs
index 31e8056..83eb87d 100644
--- a/src/part04.rs
+++ b/src/part04.rs
@@ -49,7 +49,7 @@ fn ownership_demo() {
 //@ vector. Hence, when `vec_min` finishes, the entire vector is deleted. That's of course not what
 //@ we wanted! Can't we somehow give `vec_min` access to the vector, while retaining ownership of it?
 //@ 
-//@ Rust calls this *a reference* the vector, and it considers references as *borrowing* ownership. This
+//@ Rust calls this *a reference* to the vector, and it considers references as *borrowing* ownership. This
 //@ works a bit like borrowing does in the real world: If your friend borrows a book from you, your friend
 //@ can have it and work on it (and you can't!) as long as the book is still borrowed. Your friend could
 //@ even lend the book to someone else. Eventually however, your friend has to give the book back to you,
@@ -143,4 +143,4 @@ fn mutable_ref_demo() {
 // As it turns out, combined with the abstraction facilities of Rust, this is a very powerful mechanism
 // to tackle many problems beyond basic memory safety. You will see some examples for this soon.
 
-//@ [index](main.html) | [previous](part03.html) | [raw source](https://www.ralfj.de/git/rust-101.git/blob_plain/HEAD:/workspace/src/part04.rs) | [next](part05.html)
+//@ [index](main.html) | [previous](part03.html) | [raw source](workspace/src/part04.rs) | [next](part05.html)