Small comment updates to atomic-counters

examples/atomic-counters/atomic-counters.go

@@ -42,8 +42,8 @@ func main() {
 	// Wait until all the goroutines are done.
 	wg.Wait()
 
-	// Reading atomics safely while they are being updated is
-	// possible using functions like `Load`, although here it's
-	// safe anyway, because no goroutines are writing to 'ops'.
+	// Here no goroutines are writing to 'ops', but using
+	// `Load` it's safe to atomically read a value even while
+	// other goroutines are (atomically) updating it.
 	fmt.Println("ops:", ops.Load())
 }

examples/atomic-counters/atomic-counters.hash

@@ -1,2 +1,2 @@
-806f385f4485c3e9d10fe319744dd58ab77adaaf
-LfAMxMppwL-
+3435537238237eb363f652dddb405788fec98c8b
+HWE6h4-y-Fw

examples/atomic-counters/atomic-counters.sh

@@ -1,9 +1,10 @@
 # We expect to get exactly 50,000 operations. Had we
-# used the non-atomic `ops++` to increment the counter,
-# we'd likely get a different number, changing between
-# runs, because the goroutines would interfere with
-# each other. Moreover, we'd get data race failures
-# when running with the `-race` flag.
+# used a non-atomic integer and incremented it with
+# `ops++`, we'd likely get a different number,
+# changing between runs, because the goroutines
+# would interfere with each other. Moreover, we'd
+# get data race failures when running with the
+# `-race` flag.
 $ go run atomic-counters.go
 ops: 50000