_content/ref/mod: explain what 'go install' does for non-main packages
Change-Id: Ic4cf4566172af543cf58abc6c701a0c24f1866fe
Reviewed-on: https://go-review.googlesource.com/c/website/+/338349
Trust: Jay Conrod <jayconrod@google.com>
Run-TryBot: Jay Conrod <jayconrod@google.com>
Reviewed-by: Russ Cox <rsc@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
diff --git a/_content/ref/mod.md b/_content/ref/mod.md
index 0679430..aa89613 100644
--- a/_content/ref/mod.md
+++ b/_content/ref/mod.md
@@ -1487,7 +1487,7 @@
directory named by the `GOBIN` environment variable, which defaults to
`$GOPATH/bin` or `$HOME/go/bin` if the `GOPATH` environment variable is not set.
Executables in `$GOROOT` are installed in `$GOROOT/bin` or `$GOTOOLDIR` instead
-of `$GOBIN`.
+of `$GOBIN`. Non-executable packages are built and cached but not installed.
Since Go 1.16, if the arguments have version suffixes (like `@latest` or
`@v1.0.0`), `go install` builds packages in module-aware mode, ignoring the
