GO docs update

user/environment-variables.md

@@ -180,7 +180,7 @@ to tag the build, or to run post-build deployments.
   + set to `true` if the job is allowed to fail.
   + set to `false` if the job is not allowed to fail.
 - `TRAVIS_APP_HOST`: The name of the server compiling the build script. This server serves certain helper files
-  (such as `gimme`, `nvm`, `sbt`) from `/files` to avoid external network calls; e.g., `curl -O $TRAVIS_APP_HOST/files/gimme`
+  (such as `nvm` or `sbt`) from `/files` to avoid external network calls
 - `TRAVIS_BRANCH`:
   + for push builds, or builds not triggered by a pull request, this is the name of the branch.
   + for builds triggered by a pull request this is the name of the branch targeted by the pull

user/languages/go.md

@@ -25,8 +25,8 @@ language: go
 ```
 {: data-file=".travis.yml"}
 
-Note that, in order to choose Go 1.10, you must use `go: "1.10"` (a string), not
-`go: 1.10` (a float).  Using a float results in the use of Go 1.1.
+Note that, in order to choose e.g Go 1.18, you must use `go: "1.18.0"` (full version, not
+`go: 1.18` (shorter one)).  Using a shorter one results in a missing GO package.
 </aside>
 
 {{ site.data.snippets.linux_windows_note }}
@@ -37,20 +37,16 @@ configuration](/user/customizing-the-build/) guides first.
 
 ## Specify a Go version
 
-You can use any tagged version of Go, a version with `x` in place of the minor
-or patch level to use the latest for a given major or minor version, or use
-`master` to get the latest version from source. All go version management is
-handled by [gimme](https://github.com/travis-ci/gimme).
+You can use any tagged version of Go from https://go.dev/dl/ - you need to specify 
+the version you want precisely, like "1.23.2" and similar.
 
 
 ```yaml
 language: go
 
 go:
-- 1.x
-- "1.10"
-- 1.11.x
-- master
+- "1.22.4"
+- "1.18.1"
 ```
 {: data-file=".travis.yml"}