# HG changeset patch # User Steve Losh # Date 1278471482 14400 # Node ID 8308374acdb24a2f4a9310d0d92abe5e31b102f0 # Parent 544c6c7b7603d55ee1fe8f6ce7da9ae2b555b109 docs: typos, wording diff -r 544c6c7b7603 -r 8308374acdb2 docs/concepts.rst --- a/docs/concepts.rst Tue Jul 06 00:00:49 2010 -0400 +++ b/docs/concepts.rst Tue Jul 06 22:58:02 2010 -0400 @@ -5,11 +5,11 @@ Your code is not perfect. -If you're the only person that's reading your code, it's wrong. Period. +If you're the only person that's reading your code, it's wrong. As developers we need to review each other's code. This helps us catch errors before they find our users. It also makes us take greater care when writing -code because we know someone will most definitely be looking at it. +code because we know someone will be looking at it. Code Review Basics ------------------ @@ -60,7 +60,7 @@ them. In the past half-decade or so there has been a move toward *decentralized* or -*distrubuted* version control systems. With these systems you commit to your +*distributed* version control systems. With these systems you commit to your local machine and then *push* and *pull* your commits to other people. Code review tools, however, seem to have remained rooted in the "centralized