look for python in the PATH

[rust-101.git] / src / part04.rs

diff --git a/src/part04.rs b/src/part04.rs
index 0ecfe76e53f1eaaa837d5f60fe9b130d9e9dc927..e4c6a59e00140e7489feb5718b1ae9ae2c8700ba 100644 (file)
--- a/src/part04.rs
+++ b/src/part04.rs
@@ -129,7 +129,8 @@ fn mutable_borrow_demo() {
 // they do. However, the `v` in `mutable_borrow_demo` is not actually usable, it is not *active*: As long as there is an
 // outstanding borrow, Rust will not allow you to do anything with `v`.
 
 // they do. However, the `v` in `mutable_borrow_demo` is not actually usable, it is not *active*: As long as there is an
 // outstanding borrow, Rust will not allow you to do anything with `v`.
 

-// So, to summarize - the ownership and borrowing system of Rust enforces the following three rules:
+// ## Summary
+// The ownership and borrowing system of Rust enforces the following three rules:

 // 
 // * There is always exactly one owner of a piece of data
 // * If there is an active mutable borrow, then nobody else can have active access to the data
 // 
 // * There is always exactly one owner of a piece of data
 // * If there is an active mutable borrow, then nobody else can have active access to the data