Merge pull request #1960 from tonky/fix_go_memory_by_communicating

Add more words to the quote from the actual Go documentation
rust-lang · Sep 15, 2019 · bf7f9a9 · bf7f9a9
2 parents 1e59c6d + 9f71ed2
commit bf7f9a9
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/src/ch16-03-shared-state.md b/src/ch16-03-shared-state.md
@@ -2,7 +2,7 @@
 
 Message passing is a fine way of handling concurrency, but it’s not the only
 one. Consider this part of the slogan from the Go language documentation again:
-“communicate by sharing memory.”
+“do not communicate by sharing memory.”
 
 What would communicating by sharing memory look like? In addition, why would
 message-passing enthusiasts not use it and do the opposite instead?