From 46fbbfda0f836643e8ceef3dd1145d48ac17dc5f Mon Sep 17 00:00:00 2001 From: Mark McGranaghan Date: Mon, 7 Oct 2013 06:00:26 -0700 Subject: [PATCH] fix worker pools link --- examples/atomic-counters/atomic-counters.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/atomic-counters/atomic-counters.go b/examples/atomic-counters/atomic-counters.go index 842dfee..682e524 100644 --- a/examples/atomic-counters/atomic-counters.go +++ b/examples/atomic-counters/atomic-counters.go @@ -1,6 +1,6 @@ // The primary mechanism for managing state in Go is // communication over channels. We saw this for example -// with [worker pools](worker-pool). There are a few other +// with [worker pools](worker-pools). There are a few other // options for managing state though. Here we'll // look at using the `sync/atomic` package for _atomic // counters_ accessed by multiple goroutines.