Add latest changes from gitlab-org/gitlab@master

2 files changed, 8 insertions, 8 deletions

diff --git a/doc/development/go_guide/go_upgrade.md b/doc/development/go_guide/go_upgrade.md
index cde2ee39e3c..889849799bc 100644
--- a/doc/development/go_guide/go_upgrade.md
+++ b/doc/development/go_guide/go_upgrade.md
@@ -32,7 +32,7 @@ Individual Golang projects need to support multiple Go versions because:
 - We must support the [official Omnibus GitLab Go version](#updating-go-version), which may be behind the latest minor release.
 - When Omnibus switches Go version, we still may need to support the old one for security backports.
 
-These 3 requirements may easily be satisfied by keeping support for the [3 latest minor versions of Go](https://golang.org/dl/).
+These 3 requirements may easily be satisfied by keeping support for the [3 latest minor versions of Go](https://go.dev/dl/).
 
 It is ok to drop support for the oldest Go version and support only the 2 latest releases,
 if this is enough to support backports to the last 3 minor GitLab releases.
@@ -52,12 +52,12 @@ in case of a critical security release.
 We should always:
 
 - Use the same Go version for Omnibus GitLab and Cloud Native GitLab.
-- Use a [supported version](https://golang.org/doc/devel/release#policy).
+- Use a [supported version](https://go.dev/doc/devel/release#policy).
 - Use the most recent patch-level for that version to keep up with security fixes.
 
 Changing the version affects every project being compiled, so it's important to
 ensure that all projects have been updated to test against the new Go version
-before changing the package builders to use it. Despite [Go's compatibility promise](https://golang.org/doc/go1compat),
+before changing the package builders to use it. Despite [Go's compatibility promise](https://go.dev/doc/go1compat),
 changes between minor versions can expose bugs or cause problems in our projects.
 
 ### Upgrade process
diff --git a/doc/development/go_guide/index.md b/doc/development/go_guide/index.md
index 184605170b8..a5661a77da3 100644
--- a/doc/development/go_guide/index.md
+++ b/doc/development/go_guide/index.md
@@ -7,7 +7,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 # Go standards and style guidelines
 
 This document describes various guidelines and best practices for GitLab
-projects using the [Go language](https://golang.org).
+projects using the [Go language](https://go.dev/).
 
 ## Overview
 
@@ -103,7 +103,7 @@ projects:
 - Use `goimports` before committing.
   [`goimports`](https://pkg.go.dev/golang.org/x/tools/cmd/goimports)
   is a tool that automatically formats Go source code using
-  [`Gofmt`](https://golang.org/cmd/gofmt/), in addition to formatting import lines,
+  [`Gofmt`](https://pkg.go.dev/cmd/gofmt), in addition to formatting import lines,
   adding missing ones and removing unreferenced ones.
 
   Most editors/IDEs allow you to run commands before/after saving a file, you can set it
@@ -196,7 +196,7 @@ deploy a new pod, migrating the data automatically.
 ### Testing frameworks
 
 We should not use any specific library or framework for testing, as the
-[standard library](https://golang.org/pkg/) provides already everything to get
+[standard library](https://pkg.go.dev/std) provides already everything to get
 started. If there is a need for more sophisticated testing tools, the following
 external dependencies might be worth considering in case we decide to use a specific
 library or framework:
@@ -279,7 +279,7 @@ to make the test output easily readable.
 ### Benchmarks
 
 Programs handling a lot of IO or complex operations should always include
-[benchmarks](https://golang.org/pkg/testing/#hdr-Benchmarks), to ensure
+[benchmarks](https://pkg.go.dev/testing#hdr-Benchmarks), to ensure
 performance consistency over time.
 
 ## Error handling
@@ -435,7 +435,7 @@ The following are some style guidelines that are specific to the Secure Team.
 Use `goimports -local gitlab.com/gitlab-org` before committing.
 [`goimports`](https://pkg.go.dev/golang.org/x/tools/cmd/goimports)
 is a tool that automatically formats Go source code using
-[`Gofmt`](https://golang.org/cmd/gofmt/), in addition to formatting import lines,
+[`Gofmt`](https://pkg.go.dev/cmd/gofmt), in addition to formatting import lines,
 adding missing ones and removing unreferenced ones.
 By using the `-local gitlab.com/gitlab-org` option, `goimports` groups locally referenced
 packages separately from external ones. See