doc: change "threads" to "goroutines"

R=golang-dev, minux.ma, rsc
CC=golang-dev
https://golang.org/cl/40510049

diff --git a/doc/go_faq.html b/doc/go_faq.html
index f65dff7964dee2cf9afa144909d05bc94c1995d6..e292bc879c2403ee1f7beaf6df5435bc74f5b55b 100644 (file)
--- a/doc/go_faq.html
+++ b/doc/go_faq.html
@@ -446,7 +446,7 @@ Why are map operations not defined to be atomic?</h3>
 
 <p>
 After long discussion it was decided that the typical use of maps did not require
-safe access from multiple threads, and in those cases where it did, the map was
+safe access from multiple goroutines, and in those cases where it did, the map was
 probably part of some larger data structure or computation that was already
 synchronized.  Therefore requiring that all map operations grab a mutex would slow
 down most programs and add safety to few.  This was not an easy decision,