Update platform-user-story.md (#16862)

.github/ISSUE_TEMPLATE/platform-user-story.md

@@ -21,34 +21,30 @@ so that _[Outcome - what is the value add to the user]_."
 
 ### Description/Use Case
 <!--
-_Use this section to describe the 'Why', and/or provide an example scenario in which this feature/functionality would be valueable._
+Use this section to describe the 'Why', and/or provide an example scenario in which this feature/functionality would be valueable.
 -->
 
 ### Risks/Impacts/Considerations
 <!--
-_Use this section to briefly list out any risks/impacts that may come about, as a result of the proposed solution._
-- _System performance may be slowed_
-- _Only a single search parameter can be used_
+Use this section to briefly list out any risks/impacts that may come about, as a result of the proposed solution.
+- _[System performance may be slowed]_
+- _[Only a single search parameter can be used]_
 -->
 
 ### Dev Notes
 <!--
-_Use this section to describe any useful technical information to duplicate an issue or explain requirements related to this ticket without providing implementation details._
-- _Provided is the data that was used to replicate the issue..._
-- _To test, use SimpleReport upload CSV page to ..._
+Use this section to describe any useful technical information to duplicate an issue or explain requirements related to this ticket without providing implementation details.
+- _[Provided is the data that was used to replicate the issue...]_
+- _[To test, use SimpleReport upload CSV page to ...]_
 -->
 
 ### Acceptance Criteria
 <!--
 What is Acceptance Criteria?
 A set of conditions or business rules, as defined by the Product Owner, which the functionality or feature should satisfy, in order to be accepted by the Product Owner.
 
-Use the following template when creating new Acceptance Criteria:
+Write the acceptance criteria as a list that can be checked off as work progresses. For example:
 
-"Given _[describe the precondition]_, when I _[describe the action performed]_, then I expect _[describe the expected outcome]_."
-
-_OR... it may be written as a bulleted list._
-
-- _Time must be displayed as HH:MM:SS_
-- _Delivery rate must be shown as a percentage_
+- [ ] _[Time must be displayed as HH:MM:SS]_
+- [ ] _[Delivery rate must be shown as a percentage]_
 -->