summaryrefslogtreecommitdiff
path: root/doc/go_faq.html
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2018-01-09 15:26:21 -0500
committerRuss Cox <rsc@golang.org>2018-01-09 21:47:03 +0000
commitb6c871a2af7c916f3c862e38816713aa8bf824a0 (patch)
tree8ed9612371d4bd8aa4627313c95662bf12c98c4e /doc/go_faq.html
parentdd806b8be4447f064e93ad9302bc8befde37f952 (diff)
downloadgo-git-b6c871a2af7c916f3c862e38816713aa8bf824a0.tar.gz
doc: s/tool chain/toolchain/
We were not being consistent. Standardize on toolchain. Change-Id: Id0e756b5214ce4a1341f733634ed95263f03a61c Reviewed-on: https://go-review.googlesource.com/87017 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
Diffstat (limited to 'doc/go_faq.html')
-rw-r--r--doc/go_faq.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/go_faq.html b/doc/go_faq.html
index a3cb8731fa..c038bc46bd 100644
--- a/doc/go_faq.html
+++ b/doc/go_faq.html
@@ -1842,7 +1842,7 @@ supported by recent modifications to the gold linker.
Why is my trivial program such a large binary?</h3>
<p>
-The linker in the <code>gc</code> tool chain
+The linker in the <code>gc</code> toolchain
creates statically-linked binaries by default. All Go binaries therefore include the Go
run-time, along with the run-time type information necessary to support dynamic
type checks, reflection, and even panic-time stack traces.