diff --git a/doc/effective_go.html b/doc/effective_go.html index 939d05a7d7b..b9e62b6db48 100644 --- a/doc/effective_go.html +++ b/doc/effective_go.html @@ -31,7 +31,7 @@ will be easy for other Go programmers to understand.
This document gives tips for writing clear, idiomatic Go code. -It augments the language specification, +It augments the language specification, the Tour of Go, and How to Write Go Code, all of which you diff --git a/doc/effective_go.tmpl b/doc/effective_go.tmpl index d9539893162..9a0333dbaf6 100644 --- a/doc/effective_go.tmpl +++ b/doc/effective_go.tmpl @@ -27,7 +27,7 @@ will be easy for other Go programmers to understand.
This document gives tips for writing clear, idiomatic Go code. -It augments the language specification, +It augments the language specification, the Tour of Go, and How to Write Go Code, all of which you diff --git a/doc/go_faq.html b/doc/go_faq.html index eff75342630..d95da0f6faa 100644 --- a/doc/go_faq.html +++ b/doc/go_faq.html @@ -1060,7 +1060,7 @@ What operations are atomic? What about mutexes?
We haven't fully defined it all yet, but some details about atomicity are -available in the Go Memory Model specification. +available in the Go Memory Model specification.
@@ -1113,7 +1113,7 @@ will experience performance degradation when using
multiple OS threads.
This is because sending data between threads involves switching
contexts, which has significant cost.
-For instance, the prime sieve example
+For instance, the prime sieve example
from the Go specification has no significant parallelism although it launches many
goroutines; increasing GOMAXPROCS is more likely to slow it down than
to speed it up.
@@ -1131,7 +1131,7 @@ should recognize such cases and optimize its use of OS threads. For now,
Why do T and *T have different method sets?
-From the Go Spec: +From the Go Spec:
diff --git a/doc/go_mem.html b/doc/go_mem.html index 2e341771fb4..a0032415811 100644 --- a/doc/go_mem.html +++ b/doc/go_mem.html @@ -1,6 +1,7 @@