_content: replace usages of "stutter"
Replace the use of "stutter" with a word which
more clearly conveys the meaning.
Change-Id: I1411e721f033a9600c023691e31e150b94c64b6d
Reviewed-on: https://go-review.googlesource.com/c/website/+/322671
Trust: Katie Hockman <katie@golang.org>
Run-TryBot: Katie Hockman <katie@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Russ Cox <rsc@golang.org>
diff --git a/_content/doc/effective_go.html b/_content/doc/effective_go.html
index 7620402..3db4d1b 100644
--- a/_content/doc/effective_go.html
+++ b/_content/doc/effective_go.html
@@ -354,7 +354,7 @@
<p>
The importer of a package will use the name to refer to its contents,
so exported names in the package can use that fact
-to avoid stutter.
+to avoid repetition.
(Don't use the <code>import .</code> notation, which can simplify
tests that must run outside the package they are testing, but should otherwise be avoided.)
For instance, the buffered reader type in the <code>bufio</code> package is called <code>Reader</code>,
diff --git a/_content/doc/go_faq.html b/_content/doc/go_faq.html
index 4439fdc..45b6110 100644
--- a/_content/doc/go_faq.html
+++ b/_content/doc/go_faq.html
@@ -208,7 +208,7 @@
complexity. There are no forward declarations and no header files;
everything is declared exactly once. Initialization is expressive,
automatic, and easy to use. Syntax is clean and light on keywords.
-Stuttering (<code>foo.Foo* myFoo = new(foo.Foo)</code>) is reduced by
+Repetition (<code>foo.Foo* myFoo = new(foo.Foo)</code>) is reduced by
simple type derivation using the <code>:=</code>
declare-and-initialize construct. And perhaps most radically, there
is no type hierarchy: types just <i>are</i>, they don't have to
