_content/doc: fix typos
This change corrects various misspelled words in the documentation and
adds a missing "to" in the Code of Conduct.
Change-Id: I64c65b1670faeb230144a29161c48c2c654871cd
Reviewed-on: https://go-review.googlesource.com/c/website/+/299130
Reviewed-by: Alberto Donizetti <alb.donizetti@gmail.com>
Reviewed-by: Emmanuel Odeke <emmanuel@orijtech.com>
Trust: Alberto Donizetti <alb.donizetti@gmail.com>
Run-TryBot: Alberto Donizetti <alb.donizetti@gmail.com>
TryBot-Result: Go Bot <gobot@golang.org>
diff --git a/_content/doc/conduct.html b/_content/doc/conduct.html
index 3e95db9..d959943 100644
--- a/_content/doc/conduct.html
+++ b/_content/doc/conduct.html
@@ -182,7 +182,7 @@
receive and address reported violations of the code of conduct. They will then
work with a committee consisting of representatives from the Open Source
Programs Office and the Google Open Source Strategy team. If for any reason you
-are uncomfortable reaching out the Project Stewards, please email
+are uncomfortable reaching out to the Project Stewards, please email
the Google Open Source Programs Office at <i>opensource@google.com</i>.</p>
<p>We will investigate every complaint, but you may not receive a direct response.
diff --git a/_content/doc/contribute.html b/_content/doc/contribute.html
index 66a47eb..94f2233 100644
--- a/_content/doc/contribute.html
+++ b/_content/doc/contribute.html
@@ -268,7 +268,7 @@
<p>
The Go project consists of the main
<a href="https://go.googlesource.com/go">go</a> repository, which contains the
-source code for the Go language, as well as many golang.org/x/... repostories.
+source code for the Go language, as well as many golang.org/x/... repositories.
These contain the various tools and infrastructure that support Go. For
example, <a href="https://go.googlesource.com/pkgsite">golang.org/x/pkgsite</a>
is for <a href="https://pkg.go.dev">pkg.go.dev</a>,
diff --git a/_content/doc/mod.md b/_content/doc/mod.md
index b1c0f4e..83c147e 100644
--- a/_content/doc/mod.md
+++ b/_content/doc/mod.md
@@ -446,7 +446,7 @@
### Grammar {#go-mod-file-grammar}
`go.mod` syntax is specified below using Extended Backus-Naur Form (EBNF).
-See the [Notation section in the Go Language Specificiation](/ref/spec#Notation)
+See the [Notation section in the Go Language Specification](/ref/spec#Notation)
for details on EBNF syntax.
```
@@ -1557,9 +1557,9 @@
version is dropped.
* The `-retract=version` and `-dropretract=version` flags add and drop a
retraction for the given version, which may be a single version (like
- `v1.2.3`) or an internval (like `[v1.1.0,v1.2.0]`). Note that the `-retract`
+ `v1.2.3`) or an interval (like `[v1.1.0,v1.2.0]`). Note that the `-retract`
flag cannot add a rationale comment for the `retract` directive. Rationale
- comments are recommeneded and may be shown by `go list -m -u` and other
+ comments are recommended and may be shown by `go list -m -u` and other
commands.
The editing flags may be repeated. The changes are applied in the order given.
@@ -3215,7 +3215,7 @@
changed since it was first downloaded. The `go` command reports a security error
if a downloaded file does not have the correct hash.
-For `go.mod` files, the `go` commmand computes the hash from the file
+For `go.mod` files, the `go` command computes the hash from the file
content. For module zip files, the `go` command computes the hash from the names
and contents of files within the archive in a deterministic order. The hash is
not affected by file order, compression, alignment, and other metadata. See
@@ -3316,7 +3316,7 @@
`example.com/m` to both be stored on disk, since the former is encoded as
`example.com/!m`.
-Parts of the path surrounded by square brakets, like `[.p/$W]` denote optional
+Parts of the path surrounded by square brackets, like `[.p/$W]` denote optional
values.
<table class="ModTable">
@@ -3593,7 +3593,7 @@
<p>
<code>GOPROXY</code> URLs may have the schemes <code>https</code>,
<code>http</code>, or <code>file</code>. If a URL has no scheme,
- <code>https</code> is assumed. A module cache may be used direclty as
+ <code>https</code> is assumed. A module cache may be used directly as
a file proxy:
</p>
<pre>GOPROXY=file://$(go env GOMODCACHE)/cache/download</pre>
diff --git a/_content/doc/modules/gomod-ref.md b/_content/doc/modules/gomod-ref.md
index 7a7c2b7..ba75ca3 100644
--- a/_content/doc/modules/gomod-ref.md
+++ b/_content/doc/modules/gomod-ref.md
@@ -354,7 +354,7 @@
These directives are ignored in modules that depend on the current module.
You can use the [`go mod edit`](/ref/mod#go-mod-edit) command
-to exclude a module, as in the followng example.
+to exclude a module, as in the following example.
```
go mod edit -exclude=example.com/theirmodule@v1.3.0
