rebuild

mmcgrana · eefab15c724310192e5dcf392ae446d4ed090613 · mmcgrana committed Oct 7, 2013 · Oct 7, 2013 · eefab15
1 parent 46fbbfd
commit eefab15c724310192e5dcf392ae446d4ed090613
Unified Split

Showing with 4 additions and 4 deletions.

+2 −2 examples/atomic-counters/atomic-counters.hash

+2 −2 public/atomic-counters
@@ -1,2 +1,2 @@
-97f1f28e352163cb841fb26dc05dced9fa8efde5
-sKIaNsJquU
+ddfef8425eef64cfcb82799c9bddca4bfa9bbd29
+2h8nvrnaHP
@@ -27,7 +27,7 @@
           <td class="docs">
             <p>The primary mechanism for managing state in Go is
 communication over channels. We saw this for example
-with <a href="worker-pool">worker pools</a>. There are a few other
+with <a href="worker-pools">worker pools</a>. There are a few other
 options for managing state though. Here we&rsquo;ll
 look at using the <code>sync/atomic</code> package for <em>atomic
 counters</em> accessed by multiple goroutines.</p>
@@ -44,7 +44,7 @@ counters</em> accessed by multiple goroutines.</p>
             
           </td>
           <td class="code leading">
-	        <a href="http://play.golang.org/p/sKIaNsJquU"><img title="Run code" src="play.png" class="run" /></a>
+	        <a href="http://play.golang.org/p/2h8nvrnaHP"><img title="Run code" src="play.png" class="run" /></a>
             <div class="highlight"><pre><span class="kn">package</span> <span class="nx">main</span>
 </pre></div>