From b75ad09cae8918343000e304c66c5df27101829b Mon Sep 17 00:00:00 2001 From: Tobias Klauser Date: Mon, 11 Jul 2022 19:10:50 +0200 Subject: [PATCH] cmd/trace: fix typo in web documentation Change-Id: I950224c3f698fbdf2bcab6f847f4afddaa6e9c2d Reviewed-on: https://go-review.googlesource.com/c/go/+/416974 TryBot-Result: Gopher Robot Run-TryBot: Tobias Klauser Run-TryBot: Alan Donovan Reviewed-by: Ian Lance Taylor Reviewed-by: Alan Donovan --- src/cmd/trace/main.go | 4 ++-- 1 file 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.

- 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. -- 2.50.0