_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>

4 files changed, 15 insertions, 15 deletions

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.