aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2022-07-11 19:10:50 +0200
committerTobias Klauser <tobias.klauser@gmail.com>2022-07-11 19:54:22 +0000
commitb75ad09cae8918343000e304c66c5df27101829b (patch)
tree235316ffd968024d33ea2d9131d69815434e5db1
parent7510e597def68cee77e8ba280fc0f04d3cfd2a22 (diff)
downloadgo-b75ad09cae8918343000e304c66c5df27101829b.tar.gz
go-b75ad09cae8918343000e304c66c5df27101829b.zip
cmd/trace: fix typo in web documentation
Change-Id: I950224c3f698fbdf2bcab6f847f4afddaa6e9c2d Reviewed-on: https://go-review.googlesource.com/c/go/+/416974 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com> Run-TryBot: Alan Donovan <adonovan@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com> Reviewed-by: Alan Donovan <adonovan@google.com>
-rw-r--r--src/cmd/trace/main.go4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/cmd/trace/main.go b/src/cmd/trace/main.go
index 11804d0b90..0e4d882c97 100644
--- a/src/cmd/trace/main.go
+++ b/src/cmd/trace/main.go
@@ -247,7 +247,7 @@ p { color: grey85; font-size:85%; }
because it made a system call or tried to acquire a mutex.
Directly underneath each bar, a smaller bar or more commonly a fine
- vertical line indicates an event occuring during its execution.
+ vertical line indicates an event occurring during its execution.
Some of these are related to garbage collection; most indicate that
a goroutine yielded its logical processor but then immediately resumed execution
on the same logical processor. Clicking on the event displays the stack trace
@@ -274,7 +274,7 @@ p { color: grey85; font-size:85%; }
function written in C.
</p>
<p>
- Above the event trace for the first logical processor are
+ Above the event trace for the first logical processor are
traces for various runtime-internal events.
The "GC" bar shows when the garbage collector is running, and in which stage.