diff --git a/source/team/ways-of-working.html.md.erb b/source/team/ways-of-working.html.md.erb
index 12e0b1ab4..a0738df0b 100644
--- a/source/team/ways-of-working.html.md.erb
+++ b/source/team/ways-of-working.html.md.erb
@@ -1,7 +1,7 @@
 ---
 owner_slack: "#modernisation-platform"
 title: Our ways of working
-last_reviewed_on: 2024-08-01
+last_reviewed_on: 2024-08-13
 review_in: 6 months
 ---
 
@@ -39,10 +39,10 @@ review_in: 6 months
 - Longer term objectives tracked in team [roadmap](https://app.productplan.com/pr/rY8sb6v1YYLZl4_dSKNSrUbasx2Ivzob).
 - Ensure tasks meet Definition of Ready (DoR) before sprint planning
 - Backlog issues are adequately refined by the team
-- Issues in sprint can be: `To Do`, `In Progress`, `Blocked`, `Done`
-    - `To Do`: issues here should be adequately refined. If not, they should be removed from the sprint and placed onto the backlog. Tickets marked as prioritised should be done first, assuming you are confident that you have the technical knowlede to do so.
-    - `In Progress`: issues here have an assigned team member. Updates are added as milestones are reach. Links to PRs and other useful information should be included.
-    - `Blocked`: issues here have external dependencies preventing their progress. Issues we expect to be blocked for the duration of a sprint should be place onto the backlog.
+- Issues in sprint can be: `To Do`, `In Progress`, `Blocked`, `For Review`, `Done`
+    - `To Do`: issues here should be adequately refined. If not, they should be removed from the sprint and placed onto the backlog. Tickets marked as prioritised should be done first, assuming you are confident that you have the technical knowledge to do so.
+    - `In Progress`: issues here have an assigned team member. Updates are added as milestones are reached. Links to PRs and other useful information should be included.
+    - `Blocked`: issues here have external dependencies preventing their progress. Issues we expect to be blocked for the duration of a sprint should be placed onto the backlog.
     - `For Review`: after the technical work has been done, this is a check that the ticket has been appropriately updated and the definition of done has been met. This is not to be carried out by the github reviewer.
     - `Done`: issues here have been implemented, tested, and reviewed.
 - When an issues is `Done` it should be closed