_content: rewrite links to https://go.dev/foo to /foo

We use /foo consistently so that people browsing on
golang.google.cn are not redirected to go.dev.

This CL is completely mechanical, replacing

	href="https://go.dev/ -> href="/

in HTML and replacing

	](https://go.dev/ -> ](/

in Markdown.


Change-Id: I8ac732d672075600c8e53c46787205454b196850
Reviewed-on: https://go-review.googlesource.com/c/website/+/548058
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Auto-Submit: Russ Cox <rsc@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>

14 files changed, 57 insertions, 57 deletions

diff --git a/_content/doc/gc-guide.html b/_content/doc/gc-guide.html
index cc081c6d..4a62c49f 100644
--- a/_content/doc/gc-guide.html
+++ b/_content/doc/gc-guide.html
@@ -112,7 +112,7 @@ be managed by the GC.
 For instance, non-pointer Go values stored in local variables will likely not be
 managed by the Go GC at all, and Go will instead arrange for memory to be
 allocated that's tied to the
-<a href="https://go.dev/ref/spec#Declarations_and_scope">lexical scope</a> in
+<a href="/ref/spec#Declarations_and_scope">lexical scope</a> in
 which it's created.
 In general, this is more efficient than relying on the GC, because the Go
 compiler is able to predetermine when that memory may be freed and emit
@@ -1038,11 +1038,11 @@ For more information, see the following additional resources.
 			document for the C/C++ memory allocator TCMalloc, which the Go memory allocator is based on.
 	</li>
 	<li>
-		<a href="https://go.dev/blog/go15gc">Go 1.5 GC announcement</a>&mdash;The
+		<a href="/blog/go15gc">Go 1.5 GC announcement</a>&mdash;The
 			blog post announcing the Go 1.5 concurrent GC, which describes the algorithm in more detail.
 	</li>
 	<li>
-		<a href="https://go.dev/blog/ismmkeynote">Getting to Go</a>&mdash;An
+		<a href="/blog/ismmkeynote">Getting to Go</a>&mdash;An
 			in-depth presentation about the evolution of Go's GC design up to 2018.
 	</li>
 	<li>
diff --git a/_content/doc/go1.18.md b/_content/doc/go1.18.md
index dbf74094..5d745cb1 100644
--- a/_content/doc/go1.18.md
+++ b/_content/doc/go1.18.md
@@ -229,7 +229,7 @@ FreeBSD 13.0+ will require a kernel with the COMPAT\_FREEBSD12 option set (this
 Go 1.18 includes an implementation of fuzzing as described by
 [the fuzzing proposal](https://golang.org/issue/44551).
 
-See the [fuzzing landing page](https://go.dev/security/fuzz) to get
+See the [fuzzing landing page](/security/fuzz) to get
 started.
 
 Please be aware that fuzzing can consume a lot of memory and may impact your
@@ -531,7 +531,7 @@ Go now looks first for `$HOME/go1.17` or `$HOME/sdk/go1.17`
 before falling back to `$HOME/go1.4`.
 We intend for Go 1.19 to require Go 1.17 or later for bootstrap,
 and this change should make the transition smoother.
-For more details, see [go.dev/issue/44505](https://go.dev/issue/44505).
+For more details, see [go.dev/issue/44505](/issue/44505).
 
 ## Core library {#library}
 
diff --git a/_content/doc/go1.19.md b/_content/doc/go1.19.md
index 0a2cb88f..53dae468 100644
--- a/_content/doc/go1.19.md
+++ b/_content/doc/go1.19.md
@@ -167,7 +167,7 @@ a detailed guide explaining the soft memory limit in more detail, as well as
 a variety of common use-cases and scenarios. Please note that small memory
 limits, on the order of tens of megabytes or less, are less likely to be
 respected due to external latency factors, such as OS scheduling. See
-[issue 52433](https://go.dev/issue/52433) for more details. Larger
+[issue 52433](/issue/52433) for more details. Larger
 memory limits, on the order of hundreds of megabytes or more, are stable and
 production-ready.
 
diff --git a/_content/doc/go1.20.md b/_content/doc/go1.20.md
index 3d56a021..a9873af3 100644
--- a/_content/doc/go1.20.md
+++ b/_content/doc/go1.20.md
@@ -127,7 +127,7 @@ execute commands in multiple different modules.
 <!-- https://go.dev/issue/41696, CL 416094 -->
 The `go` `build` and `go` `test`
 commands no longer accept the `-i` flag,
-which has been [deprecated since Go 1.16](https://go.dev/issue/41696).
+which has been [deprecated since Go 1.16](/issue/41696).
 
 <!-- https://go.dev/issue/38687, CL 421440 -->
 The `go` `generate` command now accepts
@@ -146,7 +146,7 @@ non-`main` packages to `GOPATH/pkg`,
 and `go` `list` no longer reports a `Target`
 field for such packages. (In module mode, compiled packages are stored in the
 [build cache](https://pkg.go.dev/cmd/go#hdr-Build_and_test_caching)
-only, but [a bug](https://go.dev/issue/37015) had caused
+only, but [a bug](/issue/37015) had caused
 the `GOPATH` install targets to unexpectedly remain in effect.)
 
 <!-- https://go.dev/issue/55022 -->
@@ -228,7 +228,7 @@ To collect coverage data for a program, build it with `go`
 binary with the environment variable `GOCOVERDIR` set
 to an output directory for coverage profiles.
 See the
-['coverage for integration tests' landing page](https://go.dev/testing/coverage) for more on how to get started.
+['coverage for integration tests' landing page](/testing/coverage) for more on how to get started.
 For details on the design and implementation, see the
 [proposal](https://golang.org/issue/51430).
 
@@ -424,7 +424,7 @@ Unlike `Director` hooks, which only operate on the outbound request,
 this permits `Rewrite` hooks to avoid certain scenarios where
 a malicious inbound request may cause headers added by the hook
 to be removed before forwarding.
-See [issue #50580](https://go.dev/issue/50580).
+See [issue #50580](/issue/50580).
 
 The [`ProxyRequest.SetURL`](/pkg/net/http/httputil/#ProxyRequest.SetURL)
 method routes the outbound request to a provided destination
diff --git a/_content/doc/go1.21.md b/_content/doc/go1.21.md
index b6cd3fcc..8f7184e2 100644
--- a/_content/doc/go1.21.md
+++ b/_content/doc/go1.21.md
@@ -115,7 +115,7 @@ Together, all these changes make type inference more powerful and inference fail
 
 Go 1.21 includes a preview of a language change we are considering for a future version of Go:
 making for loop variables per-iteration instead of per-loop, to avoid accidental sharing bugs.
-For details about how to try that language change, see [the LoopvarExperiment wiki page](https://go.dev/wiki/LoopvarExperiment).
+For details about how to try that language change, see [the LoopvarExperiment wiki page](/wiki/LoopvarExperiment).
 
 <!-- https://go.dev/issue/25448 -->
 
@@ -673,7 +673,7 @@ correctly order the definition before any
 <!-- https://go.dev/issue/28089, CL 487935 -->
 The new [`IsGenerated`](/pkg/go/ast/#IsGenerated) predicate
 reports whether a file syntax tree contains the
-[special comment](https://go.dev/s/generatedcode)
+[special comment](/s/generatedcode)
 that conventionally indicates that the file was generated by a tool.
 
 <!-- https://go.dev/issue/59033, CL 476276 -->
diff --git a/_content/doc/install/source.html b/_content/doc/install/source.html
index 22469cc7..a3cc5820 100644
--- a/_content/doc/install/source.html
+++ b/_content/doc/install/source.html
@@ -728,7 +728,7 @@ default is <code>v1</code>)
 This sets the microarchitecture level for which to compile.
 Valid values are <code>v1</code> (default), <code>v2</code>, <code>v3</code>,
 <code>v4</code>.
-See <a href="https://go.dev/wiki/MinimumRequirements#amd64">the Go wiki
+See <a href="/wiki/MinimumRequirements#amd64">the Go wiki
 MinimumRequirements page</a> for more information.
 </p>
 </li>
diff --git a/_content/doc/security/best-practices.md b/_content/doc/security/best-practices.md
index fa0cac9a..0793390e 100644
--- a/_content/doc/security/best-practices.md
+++ b/_content/doc/security/best-practices.md
@@ -17,7 +17,7 @@ potential security risks early.
 You can use [govulncheck](https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck),
 backed by the [Go vulnerability database](https://pkg.go.dev),
 to scan your code for vulnerabilities and analyze which ones actually affect you.
-Get started with [the govulncheck tutorial](https://go.dev/doc/tutorial/govulncheck).
+Get started with [the govulncheck tutorial](/doc/tutorial/govulncheck).
 
 Govulncheck can also be integrated into CI/CD flows.
 The Go team provides a
@@ -27,17 +27,17 @@ Govulncheck also supports a `-json` flag to help developers integrate vulnerabil
 scanning with other CI/CD systems.
 
 You can also scan for vulnerabilities directly in your code editor by using
-the [Go extension for Visual Studio Code](https://go.dev/security/vuln/editor).
-Get started with [this tutorial](https://go.dev/doc/tutorial/govulncheck-ide).
+the [Go extension for Visual Studio Code](/security/vuln/editor).
+Get started with [this tutorial](/doc/tutorial/govulncheck-ide).
 
 ## Keep your Go version and dependencies up to date
 
-Keeping your [Go version up-to-date](https://go.dev/doc/install) offers
+Keeping your [Go version up-to-date](/doc/install) offers
 access to the latest language features,
 performance improvements and patches for known security vulnerabilities.
 An updated Go version also ensures compatibility with newer versions of dependencies,
 helping to avoid potential integration issues.
-Review the [Go release history](https://go.dev/doc/devel/release) to see
+Review the [Go release history](/doc/devel/release) to see
 what changes have been made to Go between releases.
 The Go team issues point releases throughout the release cycle to address security bugs.
 Be sure to update to the latest minor Go version to ensure you have the
@@ -55,22 +55,22 @@ each update should be carefully reviewed and tested.
 
 ## Test with fuzzing to uncover edge-case exploits
 
-[Fuzzing](https://go.dev/security/fuzz) is a type of automated testing that
+[Fuzzing](/security/fuzz) is a type of automated testing that
 uses coverage guidance to manipulate random inputs and walk through code
 to find and report potential vulnerabilities like SQL injections,
 buffer overflows, denial or service and cross-site scripting attacks.
 Fuzzing can often reach edge cases that programmers miss,
 or deem too improbable to test.
-Get started with [this tutorial](https://go.dev/doc/tutorial/fuzz).
+Get started with [this tutorial](/doc/tutorial/fuzz).
 
 ## Check for race conditions with Go’s race detector
 
-Race conditions occur when two or more [goroutines](https://go.dev/tour/concurrency/1)
+Race conditions occur when two or more [goroutines](/tour/concurrency/1)
 access the same resource concurrently,
 and at least one of those accesses is a write.
 This can lead to unpredictable, difficult-to-diagnose issues in your software.
 Identify potential race conditions in your Go code using the built-in
-[race detector](https://go.dev/doc/articles/race_detector),
+[race detector](/doc/articles/race_detector),
 which can help you ensure the safety and reliability of your concurrent programs.
 The race detector finds races that occur at runtime,
 however, so it will not find races in code paths that are not executed.
@@ -81,7 +81,7 @@ for example, `go test -race`.
 This will compile your code with the race detector enabled and report any
 race conditions it detects at runtime.
 When the race detector finds a data race in the program, it will
-[print a report](https://go.dev/doc/articles/race_detector#report-format)
+[print a report](/doc/articles/race_detector#report-format)
 containing stack traces for conflicting accesses,
 and stacks where the involved goroutines were created.
 
diff --git a/_content/doc/security/index.md b/_content/doc/security/index.md
index 7df9067c..26560f11 100644
--- a/_content/doc/security/index.md
+++ b/_content/doc/security/index.md
@@ -6,13 +6,13 @@ layout: article
 This page provides resources for Go developers to improve security for their
 projects.
 
-(See also: [Security Best Practices for Go Developers](https://go.dev/security/best-practices).)
+(See also: [Security Best Practices for Go Developers](/security/best-practices).)
 
 ## Find and fix known vulnerabilities
 
 Go’s vulnerability detection aims to provide low-noise, reliable tools for
 developers to learn about known vulnerabilities that may affect their projects.
-For an overview, start at [this summary and FAQ page](https://go.dev/security/vuln)
+For an overview, start at [this summary and FAQ page](/security/vuln)
 about Go’s vulnerability management architecture. For an applied approach,
 explore the tools below.
 
@@ -23,15 +23,15 @@ vulnerabilities affect their code and prioritize next steps based on which vulne
 functions and methods are actually called.
 
 - [View the govulncheck documentation](https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck)
-- [Tutorial: Get started with govulncheck](https://go.dev/doc/tutorial/govulncheck)
+- [Tutorial: Get started with govulncheck](/doc/tutorial/govulncheck)
 
 ### Detect vulnerabilities from your editor
 
 The VS Code Go extension checks third-party dependencies and surfaces relevant vulnerabilities.
 
-- [User documentation](https://go.dev/security/vuln/editor)
+- [User documentation](/security/vuln/editor)
 - [Download VS Code Go](https://marketplace.visualstudio.com/items?itemName=golang.go)
-- [Tutorial: Get started with VS Code Go](https://go.dev/doc/tutorial/govulncheck-ide)
+- [Tutorial: Get started with VS Code Go](/doc/tutorial/govulncheck-ide)
 
 ### Find Go modules to build upon
 
@@ -50,20 +50,20 @@ maintainers as well as from outside sources such as [MITRE](https://www.cve.org/
 are curated by the Go Security team.
 
 - [Browse reports in the Go vulnerability database](https://pkg.go.dev/vuln/)
-- [View the Go Vulnerability Database documentation](https://go.dev/security/vuln/database)
-- [Contribute a public vulnerability to the database](https://go.dev/s/vulndb-report-new)
+- [View the Go Vulnerability Database documentation](/security/vuln/database)
+- [Contribute a public vulnerability to the database](/s/vulndb-report-new)
 
 
 ## Report security bugs in the Go project
 
-### [Security Policy](https://go.dev/security/policy)
+### [Security Policy](/security/policy)
 
 Consult the Security Policy for instructions on how to
-[report a vulnerability in the Go project](https://go.dev/security/policy#reporting-a-security-bug).
+[report a vulnerability in the Go project](/security/policy#reporting-a-security-bug).
 The page also details the Go security team’s process of tracking issues and
 disclosing them to the public. See the
-[release history](https://go.dev/doc/devel/release) for details about past security
-fixes. Per the [release policy](https://go.dev/doc/devel/release#policy),
+[release history](/doc/devel/release) for details about past security
+fixes. Per the [release policy](/doc/devel/release#policy),
 we issue security fixes to the two most recent major releases of Go.
 
 ## Test unexpected inputs with fuzzing
@@ -73,8 +73,8 @@ manipulates inputs to a program to find bugs. Go supports fuzzing in its
 standard toolchain beginning in Go 1.18.  Native Go fuzz tests are
 [supported by OSS-Fuzz](https://google.github.io/oss-fuzz/getting-started/new-project-guide/go-lang/#native-go-fuzzing-support).
 
-- [Review the basics of fuzzing](https://go.dev/security/fuzz)
-- [Tutorial: Get started with fuzzing](https://go.dev/doc/tutorial/fuzz)
+- [Review the basics of fuzzing](/security/fuzz)
+- [Tutorial: Get started with fuzzing](/doc/tutorial/fuzz)
 
 ## Secure services with Go's cryptography libraries
 
diff --git a/_content/doc/security/vuln/database.md b/_content/doc/security/vuln/database.md
index 06389842..26b75e86 100644
--- a/_content/doc/security/vuln/database.md
+++ b/_content/doc/security/vuln/database.md
@@ -19,13 +19,13 @@ without warning.
 
 ## Contributing
 
-We would love for all Go package maintainers to [contribute](https://go.dev/s/vulndb-report-new)
+We would love for all Go package maintainers to [contribute](/s/vulndb-report-new)
 information about public vulnerabilities in their own projects,
-and [update](https://go.dev/s/vulndb-report-feedback) existing information about vulnerabilities
+and [update](/s/vulndb-report-feedback) existing information about vulnerabilities
 in their Go packages.
 
 We aim to make reporting a low friction process,
-so feel free to [send us your suggestions](https://go.dev/s/vuln-feedback).
+so feel free to [send us your suggestions](/s/vuln-feedback).
 
 Please **do not** use the forms above to report a vulnerability in the Go
 standard library or sub-repositories.
@@ -131,7 +131,7 @@ To work correctly with `govulncheck`, the vulnerability database specified must
 
 The canonical database contains some additional endpoints that are part of a legacy API.
 We plan to remove support for these endpoints soon. If you are relying on the legacy API
-and need additional time to migrate, [please let us know](https://go.dev/s/govulncheck-feedback).
+and need additional time to migrate, [please let us know](/s/govulncheck-feedback).
 
 ## Schema
 
@@ -241,4 +241,4 @@ At the moment, excluded reports are not served via
 [vuln.go.dev](https://vuln.go.dev) API. However, if you have
 a specific use case and it would be helpful to have access to this information
 through the API,
-[please let us know](https://go.dev/s/govulncheck-feedback).
+[please let us know](/s/govulncheck-feedback).
diff --git a/_content/doc/security/vuln/index.md b/_content/doc/security/vuln/index.md
index 080a5ab0..8de5ec00 100644
--- a/_content/doc/security/vuln/index.md
+++ b/_content/doc/security/vuln/index.md
@@ -97,7 +97,7 @@ We would love for you to contribute and help us make improvements in the
 following ways:
 
 - [Contribute new](https://golang.org/s/vulndb-report-new) and
-  [update existing](https://go.dev/s/vulndb-report-feedback) information about
+  [update existing](/s/vulndb-report-feedback) information about
   public vulnerabilities for Go packages that you maintain
 - [Take this survey](https://golang.org/s/govulncheck-feedback) to share your
   experience using govulncheck
diff --git a/_content/doc/tutorial/fuzz.md b/_content/doc/tutorial/fuzz.md
index 8957197c..95516bba 100644
--- a/_content/doc/tutorial/fuzz.md
+++ b/_content/doc/tutorial/fuzz.md
@@ -717,7 +717,7 @@ UTF-8.
    In addition to the `-fuzz` flag, several new flags have been added to `go
    test` and can be viewed in the [documentation](/security/fuzz/#custom-settings).
 
-   See [Go Fuzzing](https://go.dev/security/fuzz/#command-line-output) for more
+   See [Go Fuzzing](/security/fuzz/#command-line-output) for more
    information on terms used in fuzzing output. For example, "new interesting"
    refers to inputs that expand the code coverage of the existing fuzz test
    corpus. The number of "new interesting" inputs can be expected to increase
@@ -810,4 +810,4 @@ func FuzzReverse(f *testing.F) {
 }
 ```
 
-[Back to top](#top)
\ No newline at end of file
+[Back to top](#top)
diff --git a/_content/doc/tutorial/govulncheck-ide.md b/_content/doc/tutorial/govulncheck-ide.md
index 53e6dc40..fc36b28a 100644
--- a/_content/doc/tutorial/govulncheck-ide.md
+++ b/_content/doc/tutorial/govulncheck-ide.md
@@ -7,14 +7,14 @@
 
 You can scan your code for vulnerabilities directly out of your editor with the Go extension for Visual Studio Code.
 
-Note: for an explanation of the vulnerability fix included in the images below, see the [govulncheck tutorial](https://go.dev/doc/tutorial/govulncheck).
+Note: for an explanation of the vulnerability fix included in the images below, see the [govulncheck tutorial](/doc/tutorial/govulncheck).
 
 ## Prerequisites:
 
-- **Go 1.18 or later.** Govulncheck is designed to work with Go 1.18 onwards. For installation instructions, see [Installing Go](https://go.dev/doc/install). We recommend using the latest version of Go to follow this tutorial.
-- **VS Code**, updated to the latest version. [Download here](https://code.visualstudio.com/). You can also use Vim (see [here](https://go.dev/security/vuln/editor#editor-specific-instructions) for details), but this tutorial focuses on VS Code Go.
+- **Go 1.18 or later.** Govulncheck is designed to work with Go 1.18 onwards. For installation instructions, see [Installing Go](/doc/install). We recommend using the latest version of Go to follow this tutorial.
+- **VS Code**, updated to the latest version. [Download here](https://code.visualstudio.com/). You can also use Vim (see [here](/security/vuln/editor#editor-specific-instructions) for details), but this tutorial focuses on VS Code Go.
 - **VS Code Go extension**, which can be [downloaded here](https://marketplace.visualstudio.com/items?itemName=golang.go).
-- **Editor-specific settings changes.** You will need to modify your IDE settings according to [these specifications](https://go.dev/security/vuln/editor#editor-specific-instructions) before being able to replicate the results below.
+- **Editor-specific settings changes.** You will need to modify your IDE settings according to [these specifications](/security/vuln/editor#editor-specific-instructions) before being able to replicate the results below.
 
 
 ## How to scan for vulnerabilities using VS Code Go
@@ -110,6 +110,6 @@ Code actions can also be used to quickly upgrade to a version of your dependency
 
 ## Additional resources
 
-- See [this page](https://go.dev/security/vuln/editor) for more information about vulnerability scanning in your IDE. The [Notes and Caveats section](https://go.dev/security/vuln/editor#notes-and-caveats), in particular, discusses special cases for which vulnerability scanning may be more complex than in the example above.
+- See [this page](/security/vuln/editor) for more information about vulnerability scanning in your IDE. The [Notes and Caveats section](/security/vuln/editor#notes-and-caveats), in particular, discusses special cases for which vulnerability scanning may be more complex than in the example above.
 - The [Go Vulnerability Database](https://pkg.go.dev/vuln/) contains information from many existing sources in addition to direct reports by Go package maintainers to the Go security team.
-- See [Go Vulnerability Management](https://go.dev/security/vuln/) page provides a high-level view of Go's architecture for detecting, reporting and managing vulnerabilities.
\ No newline at end of file
+- See [Go Vulnerability Management](/security/vuln/) page provides a high-level view of Go's architecture for detecting, reporting and managing vulnerabilities.
diff --git a/_content/doc/tutorial/govulncheck.md b/_content/doc/tutorial/govulncheck.md
index c5cfabe6..e329c6ae 100644
--- a/_content/doc/tutorial/govulncheck.md
+++ b/_content/doc/tutorial/govulncheck.md
@@ -16,13 +16,13 @@ ones first.
 
 To learn more about govulncheck, see the
 [govulncheck documentation](https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck),
-and this [blog post on vulnerability management](https://go.dev/blog/vuln) for Go.
-We'd also love to [hear your feedback](https://go.dev/s/govulncheck-feedback).
+and this [blog post on vulnerability management](/blog/vuln) for Go.
+We'd also love to [hear your feedback](/s/govulncheck-feedback).
 
 ## Prerequisites
 
 - **Go 1.18 or later.** Govulncheck is designed to work with Go 1.18 onwards.
-  (For installation instructions, see [Installing Go](https://go.dev/doc/install).)
+  (For installation instructions, see [Installing Go](/doc/install).)
   We recommend using the latest version of Go to follow this tutorial.
 - **A code editor.** Any editor you have will work fine.
 - **A command terminal.** Go works well using any terminal on Linux and Mac, and on PowerShell or cmd in Windows.
diff --git a/_content/doc/tutorial/workspaces.md b/_content/doc/tutorial/workspaces.md
index 2df1cfc3..91668ef3 100644
--- a/_content/doc/tutorial/workspaces.md
+++ b/_content/doc/tutorial/workspaces.md
@@ -24,7 +24,7 @@ of those changes in a build.
     and on PowerShell or cmd in Windows.
 
 This tutorial requires go1.18 or later. Make sure you've installed Go at Go 1.18 or later using the
-links at [go.dev/dl](https://go.dev/dl).
+links at [go.dev/dl](/dl).
 
 ## Create a module for your code {#create_folder}
 
@@ -244,7 +244,7 @@ We'll then add a new function to the `reverse` package that we can use instead o
    file, and similarly resolves the `golang.org/x/example/hello/reverse` import using
    the `go.work` file.
 
-   `go.work` can be used instead of adding [`replace`](https://go.dev/ref/mod#go-mod-file-replace)
+   `go.work` can be used instead of adding [`replace`](/ref/mod#go-mod-file-replace)
    directives to work across multiple modules.
 
    Since the two modules are in the same workspace it's easy
@@ -255,7 +255,7 @@ We'll then add a new function to the `reverse` package that we can use instead o
    Now, to properly release these modules we'd need to make a release of the `golang.org/x/example/hello`
    module, for example at `v0.1.0`. This is usually done by tagging a commit on the module's version
    control repository. See the
-   [module release workflow documentation](https://go.dev/doc/modules/release-workflow)
+   [module release workflow documentation](/doc/modules/release-workflow)
    for more details. Once the release is done, we can increase the requirement on the
    `golang.org/x/example/hello` module in `hello/go.mod`:
 
@@ -277,5 +277,5 @@ We'll then add a new function to the `reverse` package that we can use instead o
    - `go work edit` edits the `go.work` file similarly to `go mod edit`
    - `go work sync` syncs dependencies from the workspace's build list into each of the workspace modules.
 
-   See [Workspaces](https://go.dev/ref/mod#workspaces) in the Go Modules Reference for more detail on
+   See [Workspaces](/ref/mod#workspaces) in the Go Modules Reference for more detail on
    workspaces and `go.work` files.