diff --git a/rules/3-steps-to-a-pbi/rule.md b/rules/3-steps-to-a-pbi/rule.md
index 9c21fe9d603..77923e46977 100644
--- a/rules/3-steps-to-a-pbi/rule.md
+++ b/rules/3-steps-to-a-pbi/rule.md
@@ -22,6 +22,7 @@ related:
   - record-a-quick-and-dirty-done-video
   - definition-of-done
   - done-do-you-know-when-to-send-a-done-email-in-scrum
+  - close-pbis-with-context
 redirects:
   - do-you-know-the-3-steps-to-completing-a-pbi
   - do-you-know-the-3-steps-to-a-pbi
@@ -29,7 +30,7 @@ created: 2013-08-30T06:33:21.000Z
 archivedreason: null
 guid: 1de9df77-9b69-4242-b648-e08e5980e9a6
 ---
-A PBI (Product Backlog Item) is a term commonly used in Agile project management and software development to represent a unit of work or an item in the Product Backlog, which is a prioritized list of features, enhancements, or fixes to be addressed in a project.
+A PBI (Product Backlog Item) is a term commonly used in Agile project management and software development to represent a unit of work. It refers to an item in the Product Backlog, which is a prioritized list of features, enhancements, or fixes to be addressed in a project.
 
 From a developer's viewpoint, the lifecycle of a PBI can be broken down into 3 steps:
 
@@ -43,12 +44,12 @@ Next, check the PBI against the [Definition of Ready](/have-a-definition-of-read
 
 ### 1. PBI is Ready
 
-You have a backlog of PBIs (tasks, features, and fixes) which are already prioritized and approved by the [Product Owner](/rules-to-better-product-owners)
+You have a Sprint Backlog of PBIs (tasks, features, and fixes) which are already prioritized and approved by the [Product Owner](/rules-to-better-product-owners)
 
 1. Take the next PBI in the list by assigning it to yourself
 2. Break down that PBI into clear and actionable tasks
 
-![Figure: "Testing Task" added to a PBI. This is the board the team will use for 90% of the Sprint, so that testing is visible to everyone](Testing-task.png)
+![Figure: "Testing Task" added to a PBI. This is the board the team will use for 90% of the Sprint so that testing is visible to everyone](Testing-task.png)
 
 ### 2. Time to Code
 
@@ -63,14 +64,14 @@ This step depends on the complexity and nature of the task, especially if the PB
 
 ### 3. Done
 
-This should be easiest part!
+This should be the easiest part!
 
 1. Make sure your code is deployed 🚀
 2. Reply 'Done' inside the PBI and also in the email thread, as per [when to send a 'done' email in Scrum](/done-do-you-know-when-to-send-a-done-email-in-scrum)
    Note: Remember to [close PBIs, tasks and goals with context?](/close-pbis-with-context)
 3. Close the PBI
 
-Congrats, your PBI is now ready to be demonstrated during your Sprint Review!
+Congrats, your PBI is ready to be demonstrated during your Sprint Review!
 
 ::: good
 ![Figure: The important steps in a PBI lifecycle. Print this "SSW 3 Steps to a PBI pdf" and put it on your 'War Room' wall](3StepsToAPBI.jpg)