typo

Author: pixelzoom

checklists/code_review_checklist.md

@@ -480,7 +480,7 @@ addListener: function( listener ) { /*...*/ }
 - [ ] Are any significant chunks of code duplicated? This will be checked manually as well as with https://github.com/danielstjules/jsinspect or `grunt find-duplicates`
 - [ ] Is there anything that should be generalized and migrated to common code?
 - [ ] Are there any `TODO` or `FIXME` comments in the code?  They should be addressed or promoted to GitHub issues.
-- [ ] Are there any [magic numbers](https://en.wikipedia.org/wiki/Magic_number_(programming) that should be factored out as constants and documented?
+- [ ] Are there any [magic numbers](https://en.wikipedia.org/wiki/Magic_number_(programming)) that should be factored out as constants and documented?
 - [ ] Are there any constants that are duplicated in multiple files that should be factored out into a {{REPO}}Constants.js file?
 - [ ] Is [PhetColorScheme](https://github.com/phetsims/scenery-phet/blob/master/js/PhetColorScheme.js) used where appropriate? Verify that the sim is not inventing/creating its own colors for things that have been standardized in `PhetColorScheme`.  Identify any colors that might be worth adding to `PhetColorScheme`.
 - [ ] Does the implementation rely on any specific constant values that are likely to change in the future? Identify constants that might be changed in the future. (Use your judgement about which constants are likely candidates.) Does changing the values of these constants break the sim? For example, see https://github.com/phetsims/plinko-probability/issues/84.