Merge pull request digibyte#59 from mctrivia/patch-3

small wording changes

CONTRIBUTING.md

@@ -134,10 +134,10 @@ Patches that change DigiByte consensus rules are considerably more involved than
 
 ### Peer Review
 
-Anyone may participate in peer review which is expressed by comments in the pull request. Typically reviewers will review the code for obvious errors, as well as test out the patch set and opine on the technical merits of the patch. Project maintainers take into account the peer review when determining if there is consensus to merge a pull request (remember that discussions may have been spread out over GitHub, Gitter, Telegram, and mailing lists). The following language is used within pull-request comments:
+Anyone may participate in peer review which is expressed by comments in the pull request. Typically reviewers will review the code for obvious errors, as well as test out the patch set and opine on the technical merits of the patch. Project maintainers take into account the peer review when determining if there is consensus to merge a pull request (remember that discussions may have been spread out over GitHub, and Gitter). The following language is used within pull-request comments:
 
 - ACK means "I have tested the code and I agree it should be merged";
-- NACK means "I disagree this should be merged", and must be accompanied by sound technical justification (or in certain cases of copyright/patent/licensing issues, legal justification). NACKs without accompanying reasoning may be disregarded;
+- NACK means "I disagree.  This should not be merged", and must be accompanied by sound technical justification (or in certain cases of copyright/patent/licensing issues, legal justification). NACKs without accompanying reasoning may be disregarded;
 - utACK means "I have not tested the code, but I have reviewed it and it looks OK, I agree it can be merged";
 - Concept ACK means "I agree in the general principle of this pull request";
 - Nit refers to trivial, often non-blocking issues.