commit a7a6fd0f14457ddc62cb391803d00a1f558824c8
author Russ Cox <rsc@golang.org> Thu Nov 10 11:14:13 2022 -0500
committer Gopher Robot <gobot@golang.org> Thu Nov 10 18:44:29 2022 +0000
tree 7fd1511b2eccba865f3bfcea96ae662a07ef98c9
parent ff904cce944011b0bc12f552567cfe4c9d7d7cfc

_content/doc/contribute: say GOROOT instead of GODIR

There's not much point to having a second name for this concept.
Everything else in the Go world calls it GOROOT.
This text can too.

Change-Id: Idb6082fbb6b9f6b133af8caeb4d0c071cba41fbc
Reviewed-on: https://go-review.googlesource.com/c/website/+/449455
TryBot-Result: Gopher Robot <gobot@golang.org>
Run-TryBot: Russ Cox <rsc@golang.org>
Auto-Submit: Russ Cox <rsc@golang.org>
Reviewed-by: Ian Lance Taylor <iant@google.com>

_content/doc/contribute.html

diff --git a/_content/doc/contribute.html b/_content/doc/contribute.html
index 4cae5af..a39fc69 100644
--- a/_content/doc/contribute.html
+++ b/_content/doc/contribute.html
@@ -1103,9 +1103,9 @@
 </li>
 
 <li>
-In this section, we'll call the directory into which you cloned the Go repository <code>$GODIR</code>.
-The <code>go</code> tool built by <code>$GODIR/src/make.bash</code> will be installed
-in <code>$GODIR/bin/go</code> and you
+In this section, we'll call the directory into which you cloned the Go repository <code>$GOROOT</code>.
+The <code>go</code> tool built by <code>$GOROOT/src/make.bash</code> will be installed
+in <code>$GOROOT/bin/go</code> and you
 can invoke it to test your code.
 For instance, if you
 have modified the compiler and you want to test how it affects the
@@ -1114,7 +1114,7 @@
 
 <pre>
 $ cd &lt;MYPROJECTDIR&gt;
-$ $GODIR/bin/go test
+$ $GOROOT/bin/go test
 </pre>
 </li>
 
@@ -1127,9 +1127,9 @@
 might require a newer version than the stable one you have installed).
 
 <pre>
-$ cd $GODIR/src/crypto/sha1
+$ cd $GOROOT/src/crypto/sha1
 $ [make changes...]
-$ $GODIR/bin/go test .
+$ $GOROOT/bin/go test .
 </pre>
 </li>
 
@@ -1140,12 +1140,12 @@
 After that, you will want to test it by compiling or running something.
 
 <pre>
-$ cd $GODIR/src
+$ cd $GOROOT/src
 $ [make changes...]
-$ $GODIR/bin/go install cmd/compile
-$ $GODIR/bin/go build [something...]   # test the new compiler
-$ $GODIR/bin/go run [something...]     # test the new compiler
-$ $GODIR/bin/go test [something...]    # test the new compiler
+$ $GOROOT/bin/go install cmd/compile
+$ $GOROOT/bin/go build [something...]   # test the new compiler
+$ $GOROOT/bin/go run [something...]     # test the new compiler
+$ $GOROOT/bin/go test [something...]    # test the new compiler
 </pre>
 
 The same applies to other internal tools of the Go tool chain,
@@ -1157,14 +1157,14 @@
 
 <li>
 In addition to the standard per-package tests, there is a top-level
-test suite in <code>$GODIR/test</code> that contains
+test suite in <code>$GOROOT/test</code> that contains
 several black-box and regression tests.
 The test suite is run
 by <code>all.bash</code> but you can also run it manually:
 
 <pre>
-$ cd $GODIR/test
-$ $GODIR/bin/go run run.go
+$ cd $GOROOT/test
+$ $GOROOT/bin/go run run.go
 </pre>
 </ul>