Merge pull request #42 from zdyxry/master

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

diff --git a/src/part13.rs b/src/part13.rs
index 31f629bb32e88660b9e49a4ffbb5f1df6d8ca4d2..ac7698c04470ff71dffe6e89fe4c0533b26aa277 100644 (file)
--- a/src/part13.rs
+++ b/src/part13.rs
@@ -198,7 +198,7 @@ pub fn main() {
 //@ functions provided by `Send`. What the trait says is that types which are `Send` can be safely
 //@ sent to another thread without causing trouble.
 //@ Of course, all the primitive data-types are `Send`. So is `Arc`, which is why Rust accepted our
 //@ functions provided by `Send`. What the trait says is that types which are `Send` can be safely
 //@ sent to another thread without causing trouble.
 //@ Of course, all the primitive data-types are `Send`. So is `Arc`, which is why Rust accepted our

-//@ code. But `Rc` is not `Send`, and for a good reason! If had two `Rc` to the same data, and sent
+//@ code. But `Rc` is not `Send`, and for a good reason! If we had two `Rc`s to the same data, and sent

 //@ one of them to another thread, things could go havoc due to the lack of synchronization.
 //@ 
 //@ Now, `Send` as a trait is fairly special. It has a so-called *default implementation*. This
 //@ one of them to another thread, things could go havoc due to the lack of synchronization.
 //@ 
 //@ Now, `Send` as a trait is fairly special. It has a so-called *default implementation*. This