internal/trace: fix typo in goroutines.go

assosciated -> associated

Change-Id: Id1cbbdea12f0239a9e173ece934c18cc9ffcf0f4
GitHub-Last-Rev: 7fea9de6c27b95f91591db4b5bd9023eb80dc522
GitHub-Pull-Request: golang/go#54739
Reviewed-on: https://go-review.googlesource.com/c/go/+/425596
Reviewed-by: Michael Pratt <mpratt@google.com>
Reviewed-by: Michael Knyszek <mknyszek@google.com>
Auto-Submit: Michael Knyszek <mknyszek@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Run-TryBot: Michael Knyszek <mknyszek@google.com>

diff --git a/src/internal/trace/goroutines.go b/src/internal/trace/goroutines.go
index 5da90e0b6d83487c0d2bed337e80bd8855df345e..796bc8b03c8f5b72ea6461aabca3515f1d86441d 100644 (file)
--- a/src/internal/trace/goroutines.go
+++ b/src/internal/trace/goroutines.go
@@ -172,7 +172,7 @@ func GoroutineStats(events []*Event) map[uint64]*GDesc {
                        // of the active region. For ease handling of this
                        // case, we create a fake region description with the
                        // task id. This isn't strictly necessary as this
-                       // goroutine may not be assosciated with the task, but
+                       // goroutine may not be associated with the task, but
                        // it can be convenient to see all children created
                        // during a region.
                        if creatorG := gs[ev.G]; creatorG != nil && len(creatorG.gdesc.activeRegions) > 0 {