diff --git a/public/uploads/rules/tofu/rule.mdx b/public/uploads/rules/tofu/rule.mdx
index 870bb8168b..fc8e8d66c7 100644
--- a/public/uploads/rules/tofu/rule.mdx
+++ b/public/uploads/rules/tofu/rule.mdx
@@ -20,9 +20,12 @@ seoDescription: >-
 created: 2024-02-06T13:42:55.753Z
 createdBy: Tiago Araujo
 createdByEmail: TiagoAraujo@ssw.com.au
+lastUpdated: 2026-01-08T11:42:46.689Z
+lastUpdatedBy: 'Adam Cogan [SSW]'
+lastUpdatedByEmail: AdamCogan@ssw.com.au
 ---
 
-When working on a task, you may need to wait on others before you can move forward. In those situations, it’s easy to delegate and forget, causing the task to stall.
+Tasks often stall when responsibility isn’t actively managed. When working on a task, you may need to wait on others before you can move forward. In those situations, it’s easy to delegate and forget, causing the task to stall.
 
 No one is more invested in unblocking a task than the person responsible for it. That's why it's important to follow the **Take Ownership and Follow Up (TOFU)** principle.
 
@@ -38,7 +41,7 @@ That means being accountable for the task and following up with the people you
 There are 2 main aspects to TOFU:
 
 * **Taking Ownership** - Giving timely honest updates to stakeholders about progress
-* **Following up** - Proactively communicating with blockers (ideally chase them at least one a day)
+* **Following up** - Proactively communicating with blockers (ideally chase them at least once a day)
 
 ## Why it's important
 
@@ -48,8 +51,8 @@ There are 2 main aspects to TOFU:
 
 ## How to do it effectively
 
-1. **Acknowledge and accept** - When a task is assigned to you, acknowledge it promptly and ensure you understand the requirements. If anything is unclear, seek clarification immediately
-2. **Communicate oroactively** - Don't wait for someone to ask for an update. Regularly communicate your progress, especially if you encounter any roadblocks or delays
+1. **Acknowledge and accept** - When a task is assigned to you, acknowledge it promptly, and ensure you understand the requirements. If anything is unclear, seek clarification immediately
+2. **Communicate proactively** - Don't wait for someone to ask for an update. Regularly communicate your progress, especially if you encounter any roadblocks or delays
 3. **Set clear deadlines** - Establish realistic deadlines for your tasks and communicate these with your team and stakeholders. If a deadline needs to be adjusted, communicate this change as early as possible
 4. **Use tools to your advantage** - Understand the best ways for [following up effectively](/follow-up-effectively) and leverage Scrum tools (e.g., Azure DevOps, GitHub, Trello) to track tasks, deadlines, and progress
 5. **Close the loop** - Once a task is completed, ensure all relevant parties are informed and that any necessary documentation is updated. Closing the loop is a critical part of the follow-up process, as it signifies that no further action is required. The way to do this for a task you received via email is to [send a Done email](/reply-done-and-delete-the-email/). For tasks (e.g. a PBI) outside an email it is usually to [add a comment](/close-pbis-with-context/)