Update rubrics

assignments/a3.md

@@ -103,7 +103,7 @@ Release bodies must include:
 | Section | Description | Worth |
 | --- | --- | --- |
 | Use Cases  | {::nomarkdown}<ul><li>Describes 3-6 use cases that provide adequate complexity to showcase the teams skills</li><li>Use cases are well defined and recorded on the Github team repo</li><li>Illustrates UI with low fidelity sketches where applicable</li><li>Teaching Staff will approve use cases after submission. Use case approval will not affect grade, but students may be required to re-write some use cases if not approved.</li></ul>{:/} | 25.0 |
-| Stack Decisions  | Team describes the main technologies the team intends to use in the team repo. For every technology, there is also a decision record.<br>Each decision provides thoughtful rhetoric on why this is a good decision for the team, leveraging ideas and concepts presented in lectures. | 20.0 |
+| Stack Decisions  | Team describes the main technologies the team intends to use in the Github team repo. For every technology, there is also a decision record.<br>Each decision provides thoughtful rhetoric on why this is a good decision for the team, leveraging ideas and concepts presented in lectures. | 20.0 |
 | Architecture Diagram  | Incorparting all parts of the technologies in your Stack Decisions and adding adequate detail inside of those technologies (e.g. don't just list React server when there's major components to list), design an architecture diagram in the software of your choice.<br>Include it in the team repo as an image or a PDF.<br>Diagram is clean and easily followed. Text can be sparingly leveraged. | 20.0 |
 | Roadmap  | Roadmap clearly captures in-depth details of the short term future (next week weeks), some light details about the medium term (towards the end of the term), and high level goals for the future (past the end of the term).<br>Roadmap is defined in _GitHub Issues_ and labelled using labels, milestones, or projects.<br>Includes plans for user research. | 20.0 |
 | Participation & Teamwork (Individual Grade) | Effectively worked as a team member and shared equitable work load during this assignment.<br>Communication was regular and effective & acted in accordance with team principles. | 15.0 |

assignments/participation_teamwork.md

@@ -43,7 +43,7 @@ In assignment 1 you will create a principles document outlining how often your t
 
 | Section | Description | Worth |
 | --- | --- | --- |
-| General  | **Participation on GitHub**<br>{::nomarkdown}<ul><li>Participated in GitHub Issues & Submitted GitHub PRs.</li><li>Paragraph is provided in Quercus (-100% on this section if not provided).</li><li>Due as you pass in your software.</li></ul><strong>Participation in lectures/courses</strong><ul><li>Participated in and viewed online lectures/course, attended and engaged in class presentations, demos, etc.</li><li>Online Lessons have engaging, value adding comments to add to the discussion.</li><li>Joined and set up profile on Slack on time.</li><li>Team formation started/finished on time.</li><li>Due on the last day of classes.</li></ul><strong>Teamwork & Communication</strong><ul><li>Participated in all team work</li><li>Answered at least 8 weeks of standups thoughtfully</li><li>Adhered to team principles, communicated regularly/effectively, etc.</li><li>Provided substantial feature development / software to the course</li><li>Paragraph is provided in Quercus (-100% on this section if not provided).</li><li>Due as you pass in your software.</li></ul>{:/} | 100.0 |
+| General  | **Participation on GitHub**<br>{::nomarkdown}<ul><li>Participated in GitHub Issues & Submitted GitHub PRs.</li><li>Paragraph is provided in Quercus (-100% on this section if not provided).</li><li>Due as you pass in your software.</li></ul><strong>Participation in lectures/courses</strong><ul><li>Participated in and viewed lectures, attended and engaged in-class presentations from guest speakers, demos, etc.</li><li>Online discussions in Slack (#discussions) have engaging, value adding comments to add to the discussion.</li><li>Team formation started/finished on time.</li><li>Due on the last day of classes.</li></ul><strong>Teamwork & Communication</strong><ul><li>Participated in all team work</li><li>Answered at least 8 weeks of standups thoughtfully</li><li>Adhered to team principles, communicated regularly/effectively, etc.</li><li>Provided substantial feature development / software to the course</li><li>Paragraph is provided in Quercus (-100% on this section if not provided).</li><li>Due as you pass in your software.</li></ul>{:/} | 100.0 |
 | | **Total:** | 100 |
 
  <!-- RUBRIC END -->