Some minor details.
https://codereview.appspot.com/6948043/diff/4/doc/articles/race_detector.html
File doc/articles/race_detector.html (right):
https://codereview.appspot.com/6948043/diff/4/doc/articles/race_detector.html#newcode9
doc/articles/race_detector.html:9: Data races are one of the most common
and hardest to debug types of bugs in concurrent systems. A data race
occurs when two goroutines access the same variable w/o proper
synchronization and at least one of the accesses is write. See the <a
href="/ref/mem">The Go Memory Model</a> for details.
Isn't "without" better than "w/o"?
https://codereview.appspot.com/6948043/diff/4/doc/articles/race_detector.html#newcode35
doc/articles/race_detector.html:35: Fortunately, Go includes built-in
data race detector. The usage is very simple -- you just need to add
-race flag to go command:
s/includes built-in/includes a built-in/
s/flag to go command/flag to the go command/
https://codereview.appspot.com/6948043/diff/4/doc/articles/race_detector.html#newcode121
doc/articles/race_detector.html:121: Here are some example of typical
data races. All of them can be automatically detected with the race
detector.
s/example/examples/
https://codereview.appspot.com/6948043/
