diff --git a/rules/sprint-forecast/rule.md b/rules/sprint-forecast/rule.md
index 06a538008a..5abd8917b0 100644
--- a/rules/sprint-forecast/rule.md
+++ b/rules/sprint-forecast/rule.md
@@ -1,7 +1,7 @@
 ---
-seoDescription: Do you create a Sprint Forecast? (aka The functionality that will be developed during the Sprint) - Confirming the relationship between the Product Owner and Development Team in Agile Project Management.
 type: rule
-title: Do you create a Sprint Forecast? (aka The functionality that will be developed during the Sprint)
+title: Do you create a Sprint Forecast? (aka The functionality to be developed in the Sprint)
+seoDescription: The functionality that will be developed during the Sprint confirms the relationship between the Product Owner and Development Team in Agile Project Management.
 uri: sprint-forecast
 authors:
   - title: Adam Cogan
@@ -30,13 +30,13 @@ Each Sprint in a Scrum project can be considered a mini-project that has **time*
 
 ::: email-template
 
-| | |
-| -------- | --- |
-| To: | {{Product Owner}} |
-| Subject: | {{Client Name}}: Sprint XXX Forecast |
+|          |                                        |
+| -------- | -------------------------------------- |
+| To:      | {{ PRODUCT OWNER }}                    |
+| Subject: | {{ CLIENT NAME }}: Sprint XXX Forecast |
 ::: email-content
 
-### Hi {{Product Owner}}
+### Hi {{ PRODUCT OWNER }}
 
 Sprint Goals (in priority order):