Update and rename CodeReview-Exercise1.md to PeerReview-Exercise1.md

PeerReview/CodeReview-Exercise1.md → PeerReview/PeerReview-Exercise1.md

@@ -1,9 +1,23 @@
 # Code Review for Programming Exercise 1 #
 ## Description ##
 
-For this assignment, you will be giving feedback on the completeness of assignment one. In order to to do so, we will be giving you a rubric to give feedback on. For the feedback, please give positive criticism and suggestions on how to fix segments of code.
+For this assignment, you will be giving feedback on the completeness of assignment three: Pikmini. In order to to do so, we will be giving you a rubric to give feedback on. For the feedback, please give positive criticism and suggestions on how to fix segments of code.
 
-If there are any questions at any point, please email the TA.   
+You only need to review code modified or created by the student you are reviewing. You do not have to review the code and project files that were given out by the instructor.
+
+Abusive or hateful language or comments will not be tolerated and will result in a grade penalty or be considered a breach of the UC Davis Code of Academic Conduct.
+
+If there are any questions at any point, please email the TA.
+
+Email: asisandhu at ucdavis dot edu
+
+## Due Date and Submission Information ##
+This code review is due on:
+Tuesday, October 15th by 11:59 PM
+
+A successful submission should consist of a copy of this markdown document template that is modified with your peer-review. The file name should be the same as it is in the template: PeerReview-Exercise1.md. You also need to include your name and email address in the Peer-reviewer Information section below. This review document should be placed into the base folder of the repo you are reviewing in a branch called review. This branch should be on the origin of the repository you are reviewing.
+
+If you are in the rare situation where there are two peer-reviewers on a single repository, append your UC Davis user name before the extension of your review file. An example: PeerReview-Exercise1-username.md. Both reviewers should submit their reviews in the review branch.  
 
 ## Solution Assessment ##
 
@@ -92,9 +106,11 @@ Here is another example as well.
 
 * [I go to Github and look at the ICommand script in the ECS189L repo!](https://github.com/dr-jam/ECS189L/blob/1618376092e85ffd63d3af9d9dcc1f2078df2170/Projects/CommandPatternExample/Assets/Scripts/ICommand.cs#L5)
 
-### Code Style Infractures ###
+### Code Style Review ###
+
+#### Style Guide Infractions ####
 
-#### Put style guide infractures ####
+#### Style Guide Exemplars ####
 
 ## Best Practices ##
 
@@ -104,11 +120,12 @@ If the student has followed best practices (Unity coding conventions from the St
 
 If the student has breached the best practices and has done something that should be noted, please add the infracture.
 
-
 This should be similar to the Code Style justification.
 
 * [description of infraction](https://github.com/dr-jam/ECS189L) - this is the justification.
 
-### Best Practice observations ###
+### Best Practices Refiew ###
+
+#### Best Practices Infractions ####
 
-#### Put best practice observations here ####
+#### Best Practices Exemplars ####