commit 927473651d7f0cd255c97d6775a299e03dd7e930
author Jeremy Chase <jeremy.chase@gmail.com> Tue Feb 22 19:35:30 2022 +0000
committer Dmitri Shuralyov <dmitshur@google.com> Sun Mar 20 16:45:45 2022 +0000
tree 5a7e7ec55dfb0fc704cd4add0c79893f6ab4c67d
parent 13fd0169c532e13fbcc57b3abf0f03ee49c2fa8b

_content/doc/fuzz: correct typos

Change-Id: I62e808f434b2ce0701da4d77f3b03e1d3cee00fc
GitHub-Last-Rev: 1b44a82e96150811393d062e6980315695e05526
GitHub-Pull-Request: golang/website#133
Reviewed-on: https://go-review.googlesource.com/c/website/+/387314
Reviewed-by: Ian Lance Taylor <iant@google.com>
Reviewed-by: Daniel Martí <mvdan@mvdan.cc>
Run-TryBot: Daniel Martí <mvdan@mvdan.cc>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Trust: Dmitri Shuralyov <dmitshur@google.com>

_content/doc/fuzz/index.md

diff --git a/_content/doc/fuzz/index.md b/_content/doc/fuzz/index.md
index 09f1b32..6394a9c 100644
--- a/_content/doc/fuzz/index.md
+++ b/_content/doc/fuzz/index.md
@@ -49,7 +49,7 @@
   arguments. There is no return value.
 - There must be exactly one fuzz target per fuzz test.
 - All [seed corpus](#glos-seed-corpus) entries must have types which are
-  identical to the [fuzzing arguments](#fuzzing-arguments), in the same order.
+  identical to the [fuzzing arguments](#glos-fuzzing-arguments), in the same order.
   This is true for calls to
   <code>[(\*testing.F).Add](https://pkg.go.dev/testing#F.Add)</code> and any
   corpus files in the testdata/fuzz directory of the fuzz test.
@@ -119,7 +119,7 @@
 fuzzing begins.
 
 To gather baseline coverage, the fuzzing engine executes both the [seed
-corpus](#glos-seed-corpus) and the [generated corpus](#generated-corpus), to
+corpus](#glos-seed-corpus) and the [generated corpus](#glos-generated-corpus), to
 ensure that no errors occurred and to understand the code coverage the existing
 corpus already provides.
 
@@ -137,7 +137,7 @@
 interesting inputs to grow quickly at the start and eventually slow down, with
 occasional bursts as new branches are discovered.
 
-You should expect to see the "new intesting" number taper off over time as the
+You should expect to see the "new interesting" number taper off over time as the
 inputs in the corpus begin to cover more lines of the code, with occasional
 bursts if the fuzzing engine finds a new code path.
 
@@ -148,7 +148,7 @@
   - A panic occurred in the code or the test.
   - The fuzz target called `t.Fail`, either directly or through methods such as
   `t.Error` or `t.Fatal`.
-  - A non-recoverable error occured, such as an `os.Exit` or stack overflow.
+  - A non-recoverable error occurred, such as an `os.Exit` or stack overflow.
   - The fuzz target took too long to complete. Currently, the timeout for an
   execution of a fuzz target is 1 second. This may fail due to a deadlock or
   infinite loop, or from intended behavior in the code. This is one reason why