diff --git a/content/blogs/YakShaver/how-much-time-does-yakshaver-save.mdx b/content/blogs/YakShaver/how-much-time-does-yakshaver-save.mdx
index eb46e9d2b..4c88c6b9d 100644
--- a/content/blogs/YakShaver/how-much-time-does-yakshaver-save.mdx
+++ b/content/blogs/YakShaver/how-much-time-does-yakshaver-save.mdx
@@ -1,9 +1,7 @@
 ---
 seo:
   title: How Much Time Does YakShaver Save?
-  description: >-
-    Discover how YakShaver optimizes your workflow and saves you valuable time
-    in your daily tasks.
+  description: Discover how YakShaver optimizes your workflow and saves you valuable time in your daily tasks.
 category: Getting Started
 title: How Much Time Does YakShaver Save?
 date: '2025-03-18T13:00:00.000Z'
@@ -13,51 +11,31 @@ sswPeopleLink: 'https://www.ssw.com.au/people/steven-qiang/'
 bannerImage: /YakShaver/Blogs/getting_started.png
 readLength: 2 min
 summaryCard: true
-summary: >
+summary: |
   ## Getting Started with YakShaver
 
-
-  Creating high-quality Scrum Work Items, PBIs, or bug reports takes
-  time—typically 30 minutes per item on average, sometimes over 6 hours for
-  complex ones involving deep discussions or dependencies.
-
+  Creating high-quality Scrum Work Items, PBIs, or bug reports takes time—typically 30 minutes per item on average, sometimes over 6 hours for complex ones involving deep discussions or dependencies.
 
   ## Time Breakdown: Where the Effort Goes
 
-
   * 30–50% of time is spent in refinement meetings and collaborative effort.
-
-  * Tasks need clear descriptions, acceptance criteria, and full context to meet
-  the [Definition of
-  Ready](https://www.ssw.com.au/rules/have-a-definition-of-ready/).
-
+  * Tasks need clear descriptions, acceptance criteria, and full context to meet the [Definition of Ready](https://www.ssw.com.au/rules/have-a-definition-of-ready/).
 
   ***
 
-
   ## How YakShaver Helps
 
-
-  YakShaver uses AI to automate and accelerate Work Item creation, handling the
-  labor-intensive setup.
-
+  YakShaver use AI to automate and accelerate Work Item creation, handling the labor-intensive setup.
 
   * Saves \~30 minutes per Work Item
-
-  * Ensures faster alignment with the [Definition of
-  Ready](https://www.ssw.com.au/rules/have-a-definition-of-ready/)
-
+  * Ensures faster alignment with the [Definition of Ready](https://www.ssw.com.au/rules/have-a-definition-of-ready/)
   * Improves efficiency for both simple and complex tasks
 
-
   ***
 
-
   ## See Your Potential ROI
 
-
-  Want to know what this looks like for your team? Use the built-in [ROI
-  Calculator](https://yakshaver.ai/) to estimate time and cost savings.
+  Want to know what this looks like for your team? Use the built-in [ROI Calculator](https://yakshaver.ai/) to estimate time and cost savings.
 ---
 
 Creating a high-quality work item, bug report, or PBI that meets the Definition of Ready in a Scrum project takes ***30 minutes on average***\*. This includes writing clear descriptions, acceptance criteria, and relevant details, along with refinement meetings and collaboration time, which typically account for 30–50% of the total effort. Complex items may take **6+ hours**, especially if they require deep technical discussions or dependencies on other teams.