updates from our backlog session

.github/ISSUE_TEMPLATE/engineering-task.md

@@ -10,7 +10,7 @@ Use the Bug Report issue template to request help when Vagrant is not working as
 -->
 
 ## Description 
-Should be 2 - 3 sentences that define the solution or changes. 
+2 - 3 sentences that define the solution or changes. 
 
 ## Use case (optional) 
 How will this affect the end user? 
@@ -26,15 +26,15 @@ Add links to related issues or supporting documentation.
 If a task takes longer than 3 weeks, either consider if you can break it down into smaller pieces of work or update the issue with a new estimated time-frame with a summary checklist of tasks. 
 
 ### Estimated user impact
-Critical: fixes a bug, relieves a common pain point
-Major: addresses a frequent request
-Minor: trivial inconveniences that have robust workarounds 
+Most issues should categorized as minor or major. 
+- [ ] Critical: fixes a bug that impacts production deployments
+- [ ] Major: addresses a frequent request, relieves a common pain point
+- [ ] Minor: trivial inconveniences that have robust workarounds 
 
 <!--
 To complete this issue: 
 
 * add labels
-* add a reviewer 
 * select a milestone 
 
 Your milestone selection will be considered a suggestion for the team to review during backlog grooming.
@@ -43,5 +43,5 @@ Additional labels to consider:
 
 Select a task size label based on the estimated completion time and description (task-small, task-medium, task-large).
 
-If the estimated user impact is marked as critical, also add a critical label (list labels here).
+If the estimated user impact is marked as critical, also add a critical label.
 -->