New upstream version 1.44.1+dfsg1

[rustc.git] / src / doc / book / src / ch16-02-message-passing.md

diff --git a/src/doc/book/src/ch16-02-message-passing.md b/src/doc/book/src/ch16-02-message-passing.md
index 7fdbccc69df4f6f3de8dccadb1136f79795a9648..14084653bbe049ab5e9a6c00811f3d2656603a9e 100644 (file)
--- a/src/doc/book/src/ch16-02-message-passing.md
+++ b/src/doc/book/src/ch16-02-message-passing.md
@@ -3,8 +3,8 @@
 One increasingly popular approach to ensuring safe concurrency is *message
 passing*, where threads or actors communicate by sending each other messages
 containing data. Here’s the idea in a slogan from [the Go language
-documentation](http://golang.org/doc/effective_go.html): “Do not communicate by
-sharing memory; instead, share memory by communicating.”
+documentation](https://golang.org/doc/effective_go.html#concurrency): 
+“Do not communicate by sharing memory; instead, share memory by communicating.”
 
 One major tool Rust has for accomplishing message-sending concurrency is the
 *channel*, a programming concept that Rust’s standard library provides an