SSWConsulting · tiagov8 · May 9, 2024 · May 9, 2024 · May 9, 2024
diff --git a/rules/8-steps-to-scrum/rule.md b/rules/8-steps-to-scrum/rule.md
@@ -47,7 +47,7 @@ A quick note, there are only 3 roles in a Scrum Team, The Product Owner (the bos
 
 ### 3. [Sprint Planning](/what-happens-at-a-sprint-planning-meeting)
 
-The Sprint Planning session is for the Developers to focus on the subset of the Product Backlog that they think they can complete in the next Sprint, (which is most commonly a 2-week time-box).
+The Sprint Planning session is for the Developers to focus on the subset of the Product Backlog that they think they can complete in the next Sprint, (which is most commonly a 2-week timebox).
 
 The Product Owner puts the PBIs into priority order and makes sure the top ones have enough detail to be worked on. The Developers then pulls PBIs from the top of the Backlog and commits to delivering as much as they forecast they can, in the coming Sprint.
 

diff --git a/rules/do-you-know-what-happens-at-a-sprint-review-meeting/rule.md b/rules/do-you-know-what-happens-at-a-sprint-review-meeting/rule.md
@@ -39,9 +39,9 @@ If a Story is rejected and returned to the Product Backlog but the Sprint itself
 
 The Scrum Master keeps the meeting on track and to the Timebox by disallowing discussions not relevant to the acceptance or rejection of the story; this is often done by making a note to bring the subject up again in the [Retrospective](/do-you-know-what-happens-at-a-sprint-retrospective-meeting) Meeting.
 
-This meeting is normally time-boxed to as many hours as there are weeks in the Sprint.
+This meeting is normally timeboxed to as many hours as there are weeks in the Sprint.
 
-It's important that stakeholders stay in the loop of the projects progress, but they are often too busy to join the Sprint Reviews. Before the summary, you should try [loop them in](/loop-someone-in) and if they cannot join, record the summmary and send a link.
+It's important that stakeholders stay in the loop of the projects progress, but they are often too busy to join the Sprint Reviews. Before the summary, you should try [loop them in](/loop-someone-in) and if they cannot join, record the summary and send a link.
 
 ::: greybox
 In Scrum, there are 4 meetings in total that you need to know about:

diff --git a/rules/meetings-are-you-prepared-for-the-initial-meeting/rule.md b/rules/meetings-are-you-prepared-for-the-initial-meeting/rule.md
@@ -22,12 +22,12 @@ Be prepared for the initial meeting because first impressions are the most impor
 Preparing for the meeting includes:
 
 * Ensuring the sales staff attending the meeting are familiar with the relevant technologies
-* Reviewing the clients' website or other available information, taking special note of the nature of the client's business. It's also useful to remember the office locations (e.g. one office, nationwide or international) and the year of commencement of business
-* Reviewing any specification documents the client may have provided.
-* Having a wireless card to access the Internet if you cannot connect to the clients network. In fact, it is preferred you do not connect to the clients network due to time and security issues
-* Having the [Standard Sales Presentation](https://github.com/SSWConsulting/SSW.Rules.Content/raw/main/rules/meetings-are-you-prepared-for-the-initial-meeting/SSW-SalesMarketing.pptx). Remember, while clients don't want to think this is your first job, they rarely like to listen to how many CommBanks, NRMAs or Pfizers you've done work for. Clients generally prefer the focus of the meeting to be their business. You will however consider any previous projects which bear similarities to the project on offer, you do need to prove our competency
+* Reviewing the client's website or other available information, taking special note of the nature of the client's business. It's also useful to remember the office locations (e.g. one office, nationwide or international) and the year of commencement of business
+* Reviewing any specification documents the client may have provided
+* Having a wireless card to access the Internet if you cannot connect to the client's network. In fact, it is preferred you do not connect to the client's network due to time and security issues
+* Having the [Standard Sales Presentation](https://github.com/SSWConsulting/SSW.Rules.Content/raw/main/rules/meetings-are-you-prepared-for-the-initial-meeting/SSW-SalesMarketing.pptx). Remember, while clients don't want to think this is your first job, they rarely like to listen to how many CommBanks, NRMAs or Pfizers you've done work for. Clients generally prefer the focus of the meeting to be their business. You will, however, consider any previous projects which bear similarities to the project on offer. You do need to prove our competency
 * Have all the information that was recorded during the [initial call](/be-prepared-for-inbound-calls)
 * A hard copy of the [Consulting Order Terms and Conditions](https://www.ssw.com.au/SSW/Standards/Forms/ConsultingOrderTermsConditions.aspx) may be useful for them to review when the meeting is concluded
 * Plenty of business cards (that haven't been sitting in your wallet for three months!)
-* Use ChatGPT or a similar AI service to help you think of questions that are relevant to your project's technology. Try our new GPT, SIMP (SSW Initial Meeting Pro) for an easy and efficient way to prepare: https://chat.openai.com/g/g-PlDXigpe3-simp-ssw-initial-meeting-pro
+* Use ChatGPT or a similar AI service to help you think of questions that are relevant to your project's technology. Try our new GPT, SIMP (SSW Initial Meeting Pro) for an easy and efficient way to prepare: <https://chat.openai.com/g/g-PlDXigpe3-simp-ssw-initial-meeting-pro>
 * Turning up early!
diff --git a/rules/what-happens-at-a-sprint-planning-meeting/rule.md b/rules/what-happens-at-a-sprint-planning-meeting/rule.md
@@ -36,11 +36,11 @@ What can be delivered in the Increment resulting from the upcoming Sprint?
 
 [Technical Debt](/technical-debt) should be considered prior to the Sprint Planning, as it is imperative to address it. [Just Enough Refactoring](/just-enough-refactoring) should be used to solve the debt that directly surrounds or is impacted by the features included into the Sprint.
 
-The Product Backlog is examined and the Product Owner makes changes so that it is prioritized with bugs prioritized amongst Product Backlog Items (PBIs).
+The Product Backlog is examined, and the Product Owner makes changes so that it is prioritized, with bugs prioritized among the Product Backlog Items (PBIs).
 
-The Product Owner is then asked to group the top ranking Bugs into PBIs for inclusion in the Sprint. See this [rule](/bugs-do-you-know-how-to-handle-bugs-on-the-product-backlog).
+The Product Owner is then asked to group the top-ranking bugs into PBIs for inclusion in the Sprint. See this [rule](/bugs-do-you-know-how-to-handle-bugs-on-the-product-backlog).
 
-The Team are then advised of their resourcing for the Sprint as there may be additions, subtractions, leave or public holidays which are different to the previous Sprint. Considering their previous record and their current resources, The team decide on the number of story points that they will deliver in the forthcoming Sprint. When the team are not currently co-located this is often done by voting, and discussed until consensus is reached.
+The team are then advised of their resourcing for the Sprint as there may be additions, subtractions, leave or public holidays which are different to the previous Sprint. Considering their previous record and their current resources, The team decide on the number of story points that they will deliver in the forthcoming Sprint. When the team are not currently co-located this is often done by voting, and discussed until consensus is reached.
 
 The team then size (assign Story points to) PBIs starting at the top until there are more than enough PBIs to fill the Sprint.
 
@@ -73,7 +73,7 @@ No actual work on the Sprint should start until this planning is complete. It is
 
 The team should also ensure that the burndown chart is working and will be automatically sent to all members of the Scrum team overnight.
 
-The meeting concludes when The Team reports to the Scrum Master that their planning is complete and they are able to display the burndown chart.
+The meeting concludes when the team reports to the Scrum Master that their planning is complete and they are able to display the burndown chart.
 
 Ideally this meeting is timeboxed to as many hours as there will be weeks in the Sprint. However, the Sprint Planning is so essential that it must continue to completion outside the meeting if necessary.