Change of name in review.md

Author: iw-ezequiel

insights/review.md

@@ -229,7 +229,7 @@ Good facilitation can help teams get the most out of the review and it is recomm
 
 * Recommended group size is 3–8 team members for each session.
 * Recommended duration is 3–4 hours, either in one block with breaks or in multiple sessions (but aim to avoid long gaps between sessions).
-* Ask a member of the Software Engineering Quality Assessments team (currently Andrew Blundell, Daniel Stefanuik, David Lavender, Sean Craig, Nick Sparks, Adam Strickland) to create a blank spreadsheet for the review from the [template](review-template.xlsx). This will be stored centrally and shared with the team.
+* Ask a member of the Software Engineering Quality Assessments team (currently Andrew Blundell, Daniel Stefanuik, David Lavender, Sean Craig, Nick Sparks, Ezequiel Gomez) to create a blank spreadsheet for the review from the [template](review-template.xlsx). This will be stored centrally and shared with the team.
 * Work with a member of the team to fill in the _Project_ and _What's it do_ fields before the session. This is typically uncontroversial and saves time in the session.
 * To save time, fill in the list of participants before the session, but verify and update as necessary at the start of the session.
 * Be ready for the session with the review spreadsheet and this document open such that both can easily be seen by participants by sharing your screen (assuming the review is not being held in person).