Merge pull request #1960 from tonky/fix_go_memory_by_communicating

steveklabnik · web-flow · commit bf7f9a924b58 · 2019-09-15T11:38:11.000-05:00
Add more words to the quote from the actual Go documentation
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?
