From: John Bampton <jbampton@gmail.com>
Date: Tue, 17 May 2022 19:29:03 +0000 (+0000)
Subject: runtime: fix code span element
X-Git-Tag: go1.19beta1~204
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=13147f744c4ed7900ef9b1c1ffb8bf674f06b052;p=gostls13.git

runtime: fix code span element

Change-Id: I99c593573b3bec560ab3af49ac2f486ee442ee1c
GitHub-Last-Rev: e399ec50f9dde9229e05f801fd752694cc661822
GitHub-Pull-Request: golang/go#52946
Reviewed-on: https://go-review.googlesource.com/c/go/+/406837
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Michael Knyszek <mknyszek@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Run-TryBot: Ian Lance Taylor <iant@google.com>
Auto-Submit: Michael Knyszek <mknyszek@google.com>
---

diff --git a/src/runtime/HACKING.md b/src/runtime/HACKING.md
index 0ab6bcaee5..af9fe288aa 100644
--- a/src/runtime/HACKING.md
+++ b/src/runtime/HACKING.md
@@ -97,7 +97,7 @@ For runtime error debugging, it may be useful to run with `GOTRACEBACK=system`
 or `GOTRACEBACK=crash`. The output of `panic` and `fatal` is as described by
 `GOTRACEBACK`. The output of `throw` always includes runtime frames, metadata
 and all goroutines regardless of `GOTRACEBACK` (i.e., equivalent to
-`GOTRACEBACK=system). Whether `throw` crashes or not is still controlled by
+`GOTRACEBACK=system`). Whether `throw` crashes or not is still controlled by
 `GOTRACEBACK`.
 
 Synchronization