diff --git a/rules/triaging-do-you-correctly-triage-additional-item-requests/rule.md b/rules/triaging-do-you-correctly-triage-additional-item-requests/rule.md
index 9418f9bcd49..2ef5a637d0f 100644
--- a/rules/triaging-do-you-correctly-triage-additional-item-requests/rule.md
+++ b/rules/triaging-do-you-correctly-triage-additional-item-requests/rule.md
@@ -11,7 +11,7 @@ authors:
     url: https://ssw.com.au/people/cameron-shaw
   - title: Justin King
     url: https://ssw.com.au/people/justin-king
-related: 
+related:
   - turn-emails-into-pbis
 redirects: []
 created: 2009-08-18T04:45:08.000Z
@@ -29,40 +29,40 @@ Managing additional work requests can reduce the adverse impact on estimates and
 
 The first step is to analyse the priority of the additional item. Let's look at the rules to how to prioritize:
 
-### By Default, move Tasks into the next Sprint
+### By default, move new work into the next Sprint
 
-Priority is dependent upon the severity of the request. Only if it is a 'critical bug', then it will be done "in this Sprint", most tasks however go "in a later Sprint". They can include new feature requests, non-critical bug fixes, modifications and undiscovered work (i.e. work you didn't initially anticipate).   
+Priority is dependent upon the severity of the request. Only if it is a 'critical bug', then it will be done "in this Sprint", most tasks however go "into the Backlog". They can include new feature requests, non-critical bug fixes, modifications and undiscovered work (i.e. work you didn't initially anticipate).   
 
 ::: info 
-**Note:** On a fixed price contract the rules change. Bugs should be fixed in the current Sprint if time allows, otherwise first thing in the next Sprint as they are stopping you from being paid.  
+**Note:** On a fixed price contract, the rules change. Bugs should be fixed in the current Sprint if time allows, otherwise first thing in the next Sprint as they are stopping you from being paid.  
 :::
 
-### Exception #1 - Critical Bugs go into current Sprint 
+### Exception #1 - Critical Bugs go into the current Sprint 
 
 If you have a crash-to-code bug, most of the time it will go into the current Sprint. If it prevents one or more users accessing the system, it will also go into the current Sprint. High-priority bugs are fixed "in this Sprint".
 
-On the other hand, a bug that was in the prior Sprint and not marked as a task in the current Sprint, generally will be moved into the next Sprint. Everything in between is grey :-(
+Bugs are usually prioritised, so even non-critical bugs will likely end up in the next Sprint (via the Backlog).
 
 ### Exception #2 - A client can override
 
 A request for a new screen with a new look-up table that doesn't prevent users from operating the system, should be allocated to "a later Sprint". 
-If the client really \*needs\* it done now, they must specify "must be in this Sprint". This will become an 'additional item' in the current Sprint. 
+If the client really *needs* it done now, they must specify "must be in this Sprint". This will become an 'additional item' in the current Sprint. 
 
 If this request from the client will have a material impact on inflexible time and budget restraints, you need to speak and inform the client. 
 
 For example: *"Hi Bill, this task you specified 'must be in this Sprint' will take an extra 4 days. Our critical deadline will be missed. Is that OK?"*
 
-### **Exception #3 - A Developer can override**  
+### Exception #3 - A Developer can override
 
-A client may request a small feature (e.g. changing the sort order of a combo-box). This work can go in the current Sprint as long as the task is small (less than 1/2 hour) and the Sprint is under budget.  
+A client may request a small feature (e.g. changing the sort order of a combo-box). This work can go in the current Sprint as long as the task is small (less than 1/2 hour) and the Sprint is not already slipping.  
   
-If the work is over budget then you need to obtain approval for any 'additional item', from both the project manager and the client, before adding the request into the Release Plan. See more about how to [obtain approval for additional items that exceed estimates](/do-you-email-clients-as-soon-as-you-realise-you-will-overrun-your-original-estimate).
+If the work is over budget, then you need to obtain approval for any 'additional item', from both the project manager and the client, before adding the request into the Release Plan. See more about how to [obtain approval for additional items that exceed estimates](/do-you-email-clients-as-soon-as-you-realise-you-will-overrun-your-original-estimate).
 
 ::: email-template  
 |          |     |
 | -------- | --- |
 | To:      | Dave |
-| Subject: | Client List for Administrators  |  
+| Subject: | Northwind - Client List for Administrators  |  
 ::: email-content  
 
 ### Hi Dave,